From owner-cvs-all Mon Dec 28 17:23:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26076 for cvs-all-outgoing; Mon, 28 Dec 1998 17:23:16 -0800 (PST) (envelope-from owner-cvs-all@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA26067; Mon, 28 Dec 1998 17:23:05 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA01112; Tue, 29 Dec 1998 11:52:05 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id LAA32484; Tue, 29 Dec 1998 11:51:44 +1030 (CST) Message-ID: <19981229115143.X12346@freebie.lemis.com> Date: Tue, 29 Dec 1998 11:51:43 +1030 From: Greg Lehey To: Bernd Walter , Peter Wemm , cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sbin/vinum Makefile commands.c list.c v.c References: <199812281632.IAA06166@freefall.freebsd.org> <19981229021500.49965@cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19981229021500.49965@cicely.de>; from Bernd Walter on Tue, Dec 29, 1998 at 02:15:00AM +0100 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk On Tuesday, 29 December 1998 at 2:15:00 +0100, Bernd Walter wrote: > On Mon, Dec 28, 1998 at 08:32:39AM -0800, Peter Wemm wrote: >> peter 1998/12/28 08:32:39 PST >> >> Modified files: >> sbin/vinum Makefile commands.c list.c v.c >> Log: >> Tweaks as a result of having vinum statically buildable in a kernel. >> > The last I know is that the vinum module had to be loaded after / was mountet rw, > because it creates nodes and directorys und /dev. > Was there an exchange in this behavour? No. I don't really think this is going to work properly until we have DEVFS. > Are there any plans to implement devfs at this time? If theres > nobody working on devfs support and if there's no good reason to do > later I would try to do it - devfs seems not to be to hard to > implement with my current knowledge. There are two big problems with DEVFS: 1. There are two very different opinions out there about how to do it. 2. The technical one is how to handle deletions of devices. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message