From owner-freebsd-current Sun Sep 27 14:10:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16555 for freebsd-current-outgoing; Sun, 27 Sep 1998 14:10:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16510 for ; Sun, 27 Sep 1998 14:10:15 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id OAA28641; Sun, 27 Sep 1998 14:10:05 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp04.primenet.com, id smtpd028630; Sun Sep 27 14:10:02 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id OAA29425; Sun, 27 Sep 1998 14:09:58 -0700 (MST) From: Terry Lambert Message-Id: <199809272109.OAA29425@usr05.primenet.com> Subject: Re: DEVFS & SLICE? To: dholland@cs.toronto.edu (David Holland) Date: Sun, 27 Sep 1998 21:09:58 +0000 (GMT) Cc: rotel@indigo.ie, tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: <98Sep26.231232edt.37814-5346@qew.cs.toronto.edu> from "David Holland" at Sep 26, 98 11:12:28 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Major and minor device numbers are a projection of internal kernel > guts into user space. As such, they are a problem, not a feature. Here here. > The DEVFS approach, when taken to its conclusion, ultimately leads to > abolishing the concept entirely. You'd still need dev_t for stat, but > you don't need or want to interpret the contents. For what it's worth, on Solaris, the dev_t returned by stat is the address of the device descriptor in kernel space, and not an index. > > These two issues seem more or less the same, using DEVFS simply > > moves the checking from mknod code to DEVFS code. Any general > > framework implemented in DEVFS for controlling device visibility > > in chroot environments could just as easily be provided for mknod. > > Huh? How do you tell mknod(2) that it can only create nodes in (say) > /dev, /home/ftp/dev, and /usr/test/chroot/dev? Or better yet: # mknod wd0 c 21 1 mknod: Command not found. # (Yes, I know you will still need "mknod" to build an NFS "/dev" for primitive OS's like DEC UNIX and Linux; don't take everything so seriously!). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message