From owner-freebsd-current Tue Nov 3 01:06:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11973 for freebsd-current-outgoing; Tue, 3 Nov 1998 01:06:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11966 for ; Tue, 3 Nov 1998 01:06:40 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id BAA15199; Tue, 3 Nov 1998 01:00:12 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdo15193; Tue Nov 3 09:00:09 1998 Date: Tue, 3 Nov 1998 00:59:44 -0800 (PST) From: Julian Elischer To: Alfred Perlstein cc: current@FreeBSD.ORG Subject: Re: wondering about DEVFS & MFS? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG you can't use an MFS root and DEVFS together due to the fact that MFS synthesizes a device node which needless to say, devfs doesn't know anything about. If you've got an ffs root and just put devfs over the top of your existing /dev/you'll be ok but with and MFS ROOT you're screwed.. I still have devfs fixes to put in but am busy on other things. It works in the situation I mentionned. On Mon, 2 Nov 1998, Alfred Perlstein wrote: > > mfs is working fine for me as my /tmp, i used to be a big fan of DEVFS, > how is it coming along? usable again? any caveats? > > i know LINT says DEVFS+MFS is a no-no, is this still true? in some particular cases ... yes. > > thanks, > Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com > -- There are operating systems, and then there's FreeBSD. > -- http://www.freebsd.org/ 3.0-current > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message