Date: Wed, 26 Apr 2000 13:02:05 +0930 From: Greg Lehey <grog@lemis.com> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: Brad Knowles <blk@skynet.be>, Mathew Kanner <mat@cs.mcgill.ca>, current@FreeBSD.ORG Subject: Re: Vinum breakage Message-ID: <20000426130205.E40207@freebie.lemis.com> In-Reply-To: <200004051843.LAA79634@apollo.backplane.com> References: <200004051344.JAA15337@dean.pc.sas.com> <200004051606.JAA78646@apollo.backplane.com> <20000405123724.A24249@cs.mcgill.ca> <200004051649.JAA78992@apollo.backplane.com> <v0422081db51122bb4520@[195.238.1.121]> <200004051843.LAA79634@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, 5 April 2000 at 11:43:52 -0700, Matthew Dillon wrote: > >> >>> Also, as a general note to everyone, make sure you are building vinum >>> into the kernel directly and not using it as a kld, just to ensure that >>> it stays in sync with the kernel. >> >> Isn't this in direct conflict with the instructions given for >> normally using vinum? Is this a temporary change, until we get over >> some of the current problems, or is this a more permanent change? >> >> Out of curiosity, is this your recommendation, or does Greg agree with it? > > This is my personal recommendation - if you are messing around with > something that is under development or test, it is best to build it > into the kernel to avoid getting out of sync without knowing it. Hmm. I seem to have mislaid this thread. I recommend using modules rather than to put vinum in the kernel. Since I test this way, I also prefer you to do it that way, so that I can't be sure there's some problem in the build process. On the other hand, Matt is right: it's currently a pain to be sure your kernel and the vinum module are in sync. Given the problems we're having, understand the issues and do whichever you prefer. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000426130205.E40207>