From owner-freebsd-stable@FreeBSD.ORG Fri Oct 29 20:20:11 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4B3F916A4CE; Fri, 29 Oct 2004 20:20:11 +0000 (GMT) Received: from mta13.adelphia.net (mta13.adelphia.net [68.168.78.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DE9543D1D; Fri, 29 Oct 2004 20:20:10 +0000 (GMT) (envelope-from security@jim-liesl.org) Received: from smtp.jim-liesl.org ([68.71.52.28]) by mta13.adelphia.net (InterMail vM.6.01.03.02 201-2131-111-104-20040324) with ESMTP id <20041029202007.VSTQ15118.mta13.adelphia.net@smtp.jim-liesl.org>; Fri, 29 Oct 2004 16:20:07 -0400 Received: from [127.0.0.1] (localhost.jim-liesl.org [127.0.0.1]) by smtp.jim-liesl.org (Postfix) with ESMTP id 03F8A152B3; Fri, 29 Oct 2004 14:20:05 -0600 (MDT) Message-ID: <4182A618.5090406@jim-liesl.org> Date: Fri, 29 Oct 2004 14:20:40 -0600 From: secmgr User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Greg 'groggy' Lehey References: <02f201c4ba91$f9f95db0$33017f80@psique> <1098725440.5103.4.camel@sp4.cs.ucdavis.edu> <417D604D.4090800@jim-liesl.org> <20041028153756.GB1195@eucla.lemis.com> In-Reply-To: <20041028153756.GB1195@eucla.lemis.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org cc: FreeBSD Release Engineering Team Subject: Re: freebsd 5.3 have any problem with vinum ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Oct 2004 20:20:11 -0000 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