Date: Fri, 4 Oct 2002 17:59:15 -0400 From: Garance A Drosihn <drosih@rpi.edu> To: Poul-Henning Kamp <phk@critter.freebsd.dk>, Lars Eggert <larse@ISI.EDU> Cc: n0go013 <ttz@blahdeblah.demon.co.uk>, current <freebsd-current@FreeBSD.ORG>, not on list - please copy <hackers@FreeBSD.ORG> Subject: Re: [ GEOM tests ] vinum drives lost Message-ID: <p0511171db9c3bcbb728d@[128.113.24.47]> In-Reply-To: <62515.1033758160@critter.freebsd.dk> References: <62515.1033758160@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
At 9:02 PM +0200 10/4/02, Poul-Henning Kamp wrote: >There are numerous architectural issues which have never been >fixed in vinum, and one or more of these bits now. > >Whoever loves vinum will have to chase it/them down and fix it. > >If I receive patches or requests for changes to GEOM as result >of this, they will be evaluated in good faith. > >Worst case you will have the option to use: > > options NOGEOM > options vinum I know nothing about vinum and only a little about GEOM, so I have no opinion on which should be fixed to work with the other, and I'm reluctant to get drawn into that battle anyway. However, I do think that if it isn't easy to get the two of them to work together nicely, then we should enforce the above options in the source code. Ie, if someone tries to compile a kernel with both GEOM and vinum turned on, then the compile should fail with some suitable error message. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p0511171db9c3bcbb728d>