From owner-freebsd-current@FreeBSD.ORG Wed Aug 25 19:54:39 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F177216A4CF; Wed, 25 Aug 2004 19:54:38 +0000 (GMT) Received: from carrick.bishnet.net (carrick.bishnet.net [217.204.9.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8AF8643D66; Wed, 25 Aug 2004 19:54:38 +0000 (GMT) (envelope-from tim-lists@bishnet.net) Received: from 82-68-45-195.dsl.in-addr.zen.co.uk ([82.68.45.195]) by carrick.bishnet.net with asmtp (TLSv1:AES256-SHA:256) (Exim 4.40 (FreeBSD)) id 1C03qr-0009gz-UZ; Wed, 25 Aug 2004 20:54:34 +0100 From: Tim Bishop To: Greg 'groggy' Lehey In-Reply-To: <20040816122357.GT30875@wantadilla.lemis.com> References: <001d01c48372$a4b5e130$142a15ac@spud> <1092649820.821.2.camel@inferno.sixth.bishnet.net> <20040816122357.GT30875@wantadilla.lemis.com> Content-Type: text/plain Message-Id: <1093463672.41794.4.camel@inferno.sixth.bishnet.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 25 Aug 2004 20:54:33 +0100 Content-Transfer-Encoding: 7bit X-Bishnet-MailScanner-Information: Contact postmaster@bishnet.net X-Bishnet-MailScanner-VirusCheck: Found to be clean X-Bishnet-MailScanner-SpamCheck: not spam, SpamAssassin (score=-4.9, required 5, autolearn=not spam, BAYES_00 -4.90) X-Bishnet-MailScanner-From: tim-lists@bishnet.net cc: Darren Pilgrim cc: current@FreeBSD.ORG Subject: Re: What's the status of vinum? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Aug 2004 19:54:39 -0000 On Mon, 2004-08-16 at 13:23, Greg 'groggy' Lehey wrote: > On Monday, 16 August 2004 at 10:50:20 +0100, Tim Bishop wrote: > > I'm currently using RELENG_5_2 with vinum (not gvinum). It's > > mirroring everything except swap, which I vaguely recall might not > > have worked. > > Correct. Swap on Vinum does not work on 5.x: the swap code insists on > GEOM. It worked on earlier 5.x, though. > > I believe with -CURRENT that vinum might not work right, and gvinum > > might be the only option. Then again I could be wrong :-) > > Yes, you're (still) wrong. They're both currently in the tree, and > different parts of each work. > > > When 5.2 is released gvinum should be the default, and should > > hopefully be in a finished state. > > For very large values of 2. 5.3 won't have a complete gvinum; > hopefully 5.4 will only have gvinum, which will then be renamed vinum. Yes, I meant 5.3 :-) So what's state is (g)vinum likely to be in for 5.3? I'm hesitant to upgrade because it appears that the system is moving from under vinum's feet, and gvinum isn't there yet. What are people who are currently using vinum on earlier 5.x's going to do until gvinum is finished? Cheers, Tim. -- Tim Bishop http://www.bishnet.net/tim PGP Key: 0x5AE7D984