Date: Thu, 26 Aug 2004 09:15:48 +0100 From: Tim Bishop <tim-lists@bishnet.net> To: Greg 'groggy' Lehey <grog@FreeBSD.org> Cc: current@FreeBSD.ORG Subject: Re: What's the status of vinum? Message-ID: <1093508148.72818.2.camel@inferno.sixth.bishnet.net> In-Reply-To: <20040825234618.GV9754@wantadilla.lemis.com> References: <001d01c48372$a4b5e130$142a15ac@spud> <1092649820.821.2.camel@inferno.sixth.bishnet.net> <20040816122357.GT30875@wantadilla.lemis.com> <1093463672.41794.4.camel@inferno.sixth.bishnet.net> <20040825234618.GV9754@wantadilla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2004-08-26 at 00:46, Greg 'groggy' Lehey wrote: > On Wednesday, 25 August 2004 at 20:54:33 +0100, Tim Bishop wrote: > > 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. > > Very early 5.x, sure. That goes back a long way. I still have this > machine running: > > FreeBSD brewer.lemis.com 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Tue Dec 12 18:45:30 CST 2000 grog@monorchid.lemis.com:/src/FreeBSD/5.0-CURRENT/src/sys/compile/MONORCHID i386 I'm talking releases of 5.x - I've not tracked -CURRENT really. Specifically, 5.1. > > 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? > > I suppose now is a good time to remind you that -CURRENT is constantly > changing. If you want stability, you shouldn't be using it. I'd > suggest that you stay where you are until gvinum is finished. When 5.3 is released we're in the process of heading towards -STABLE, which I'd hoped would have a working gvinum (or vinum) implementation. It looks like this won't happen. I drew the balance between stability and trying out new stuff. I didn't track -CURRENT, I used the releases along that line to familiarise myself with 5.x. Cheers, Tim. -- Tim Bishop http://www.bishnet.net/tim PGP Key: 0x5AE7D984
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1093508148.72818.2.camel>