From owner-freebsd-current Mon Jun 1 12:20:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09272 for freebsd-current-outgoing; Mon, 1 Jun 1998 12:20:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09222 for ; Mon, 1 Jun 1998 12:20:23 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id TAA05276; Mon, 1 Jun 1998 19:19:49 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id VAA05003; Mon, 1 Jun 1998 21:19:32 +0200 (MET DST) Message-ID: <19980601211931.09973@follo.net> Date: Mon, 1 Jun 1998 21:19:31 +0200 From: Eivind Eklund To: Julian Elischer , "Alex G. Bulushev" Cc: sepotvin@videotron.ca, current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... References: <199806010816.MAA12889@sinbin.demos.su> <3572FBD0.33590565@whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <3572FBD0.33590565@whistle.com>; from Julian Elischer on Mon, Jun 01, 1998 at 12:06:56PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jun 01, 1998 at 12:06:56PM -0700, Julian Elischer wrote: > THis is the single best argument I've heard for allowing > devfs type nodes on a normal fs. :-) > > certainly DEVFS makes the case of providing devices to chroot > environments a lot more 'heavyweight' > > A number of things to note about this: > 1/ There is a suggestion that there be a mount option that simply > mounts an EMPTY devfs, which would then be populatable using some > form of mknod (which uses the name to create the device and not the > major/minor) Can't this easily be done by mounting a DEVFS, wiping it, mounting one more, and ln'ing in the nodes? No changes required to do that... Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message