From owner-freebsd-hackers Mon Sep 20 17:51: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 7B90C14D0B for ; Mon, 20 Sep 1999 17:50:59 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id RAA93125; Mon, 20 Sep 1999 17:50:42 -0700 (PDT) Date: Mon, 20 Sep 1999 17:50:41 -0700 (PDT) From: Julian Elischer To: Matthew Jacob Cc: Mark Newton , gurney_j@resnet.uoregon.edu, winter@jurai.net, chuckr@mat.net, wayne@crb-web.com, freebsd-hackers@FreeBSD.ORG Subject: Re: what is devfs? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 20 Sep 1999, Matthew Jacob wrote: > > > > > Hmm - rip out the whole devfs infrastructure and replace it with something > > which writes tuples of (operation, devname, major, minor) to a socket > > somewhere, where "operation" is "create", "delete", "online", "offline", > > etc. Why worry about the complexities of a vfs to handle /dev in the > > kernel when almost all of it can be done in userland? > > > > [ Heh. *now* there'll be some wailing and gnashing of teeth... :-) ] > > > "booting"? you can make /dev on a small mfs that is automatically mounted, or you can rpepopulate /dev with know boot devices. You don't need /dev to mount root anyhow. In fact you don't need /dev to mount others either as the mount request passes in the device name which could be looked up directly assuming that poul's dev_t cache has the entries already. (result of make_dev()). > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message