> > If a process tries to open() an entry in /dev which does not exist,
> > devfs passes the name of the entry to kerneld. It is up to kerneld to
> > convert filenames to modules (i.e. "ttyS{0,1,2,3}" to "serial").
>
> Sorry, no.
>
> I refuse to use a kernel that depends on kerneld. That's final.
>
> This is a design issue. I don't like a crippled kernel - I want the kernel
> to be stand-alone, and be able to function on its own. It shouldn't do
> policy decisions, but is should also not just flail wildly around when
> something strange happens. That way lies madness (Windows NT to be exact).
As far as I have understood the proposal, kerneld would be called _only_ when
someone tries to open a (-1,-1) entry in /dev, _not_ for normal entries created
automatically for all built-in drivers during kernel startup.
Have a nice fortnight
-- Martin `MJ' Mares <mj@gts.cz> http://atrey.karlin.mff.cuni.cz/~mj/ Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth "In accord to UNIX philosophy, PERL gives you enough rope to hang yourself." -- Larry Wall