Date: Tue, 21 Sep 1999 10:24:52 +0930 (CST) From: Mark Newton <newton@internode.com.au> To: mjacob@feral.com Cc: newton@internode.com.au, julian@whistle.com, 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: <199909210054.KAA35335@gizmo.internode.com.au> In-Reply-To: <Pine.BSF.4.05.9909201723300.44736-100000@semuta.feral.com> from "Matthew Jacob" at Sep 20, 99 05:23:40 pm
next in thread | previous in thread | raw e-mail | index | archive | help
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"? Not needed - The devfs registration stubs are called during driver initialization which happens at boot time anyway; When the devfsd starts up and reads messages from its socket, it'd get a queue of device instances. I'm envisaging something like /dev/log here; When syslog opens it at boot time, it gets all the log messages that have appeared during initialization. - mark ---- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 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?199909210054.KAA35335>