I'm only going to reply once to this thread
In message <[EMAIL PROTECTED]> Robert
Watson writes:
: And in a sense, we already have two kerneld's -- pccardd and usbd, which
: maintain mappings between named devices and drivers, etc. Combining them,
: and adding another source of requests (and LPC channel over a UNIX domain
: socket) would not be that hard.
I personally think that a devd would be great to have. One that could
do things when devices arrive and leave as well as when the removable
hardware/software detects a new hunk of hardware that doesn't attach
to any resident driver. It would be extremely useful if only the
specific driver that was for that hardware wound up in the kernel. It
would also be useful if that module were unloaded when that removable
device went away. No need to keep it in memory, so long as there was
a way to bring it back later.
Sure, there's a monster bug in the kldload/unload right now where that
eats wired memory. That bug should be fixed.
Finally, all of this would be less of an issue if one could page the
kernel, or at least parts of it...
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
