From owner-freebsd-current Sat Sep 26 20:21:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA01406 for freebsd-current-outgoing; Sat, 26 Sep 1998 20:21:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from yonge.cs.toronto.edu (yonge.cs.toronto.edu [128.100.2.11]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA01387 for ; Sat, 26 Sep 1998 20:21:03 -0700 (PDT) (envelope-from dholland@cs.toronto.edu) Received: from qew.cs.toronto.edu ([128.100.1.13]) by yonge.cs.toronto.edu with SMTP id <86567-25411>; Sat, 26 Sep 1998 23:20:44 -0400 Received: by qew.cs.toronto.edu id <37814-5346>; Sat, 26 Sep 1998 23:12:32 -0400 Subject: Re: DEVFS & SLICE? From: David Holland To: rotel@indigo.ie Date: Sat, 26 Sep 1998 23:12:28 -0400 Cc: tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: <199809261328.OAA00354@indigo.ie> from "Niall Smart" at Sep 26, 98 10:28:27 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <98Sep26.231232edt.37814-5346@qew.cs.toronto.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > MAKEDEV should probably be built from a file which describes kernel > devices, maintanence of this would be so easy as to be a non-issue > and would have the side effect of a database of device major and > minor numbers which the DEVFS approach doesn't seem to afford. Major and minor device numbers are a projection of internal kernel guts into user space. As such, they are a problem, not a feature. 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. > 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? -- - David A. Holland | (please continue to send non-list mail to dholland@cs.utoronto.ca | dholland@hcs.harvard.edu. yes, I moved.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message