Date: Mon, 20 Sep 1999 17:50:41 -0700 (PDT) From: Julian Elischer <julian@whistle.com> To: Matthew Jacob <mjacob@feral.com> Cc: Mark Newton <newton@internode.com.au>, gurney_j@resnet.uoregon.edu, winter@jurai.net, chuckr@mat.net, wayne@crb-web.com, freebsd-hackers@FreeBSD.ORG Subject: Re: what is devfs? Message-ID: <Pine.BSF.3.95.990920174745.6478F-100000@current1.whistle.com> In-Reply-To: <Pine.BSF.4.05.9909201723300.44736-100000@semuta.feral.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.990920174745.6478F-100000>