Date: Fri, 29 Oct 2004 14:20:40 -0600 From: secmgr <security@jim-liesl.org> To: Greg 'groggy' Lehey <grog@FreeBSD.org> Cc: FreeBSD Release Engineering Team <re@FreeBSD.org> Subject: Re: freebsd 5.3 have any problem with vinum ? Message-ID: <4182A618.5090406@jim-liesl.org> In-Reply-To: <20041028153756.GB1195@eucla.lemis.com> References: <02f201c4ba91$f9f95db0$33017f80@psique> <1098725440.5103.4.camel@sp4.cs.ucdavis.edu> <417D604D.4090800@jim-liesl.org> <20041028153756.GB1195@eucla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Greg 'groggy' Lehey wrote: >A bit of background: we know that 'gvinum' will replace Vinum; the >original intention had been to do it seamlessly, but for various >reasons that did happen. Then we decided that we should leave them >both in the tree until gvinum had the full functionality of Vinum. >It's beginning to look like that's a bad idea. Lukas is >(understandably) working only on gvinum, and since I know it's nearly >there, I'm not going to do any further work on Vinum in FreeBSD 5. >Given the problems, I'd suggest that we yank it. I'm copying the >release engineering team. Re, what do you think? > >Greg > > Not that I've got a lot of say in the matter, but I would vote for this too. (along with migration info in the release notes). There are also some minor changes needed to the docs on vinumvm.org for gvinum/newfs (5.3) to correct new paths and switches. thanks jim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4182A618.5090406>