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: [EMAIL PROTECTED] (W)
Network Engineer Email: [EMAIL PROTECTED] (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 [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
