Messages in this thread |  | | | Subject | Re: My $0.02 on devd and devfs | | Date | Tue, 12 Oct 1999 17:56:51 -0300 | | From | Horst von Brand <> |
| |
danielt@digi.com said: > On Tue, 12 Oct 1999, Horst von Brand wrote:
[...]
> > Nope. devd is notified when the device shows up. It can then go and create > > /dev/printer/0 and do some other magic, if needed. When you try to open the > > file, it is there. That in turn might trigger loading modules and > > initializing the device.
> And _how_exactly_ is the device "showing up" if it is a module?
Ever taken a look at lspci(8)? It is quite able to detect devices that haven't been initialized, and for which no driver is extant. Any decent PnP mechanism _will_ have to be able to tell the OS "a such-and-such showed up at this place, please take care of it".
> This scenario has some serious black magic in it or devd is > "less useful than the male nipple".
Just a bit of logic.
> > Note that if devd is missing, but the device files are extant, everything > > is peachy.
> And exactly like it is now, which has everyone who deals with dynamic > devices twisting themselves into pretzels to try to work around it > without _looking_ like they are trying to bypass it completely.
Sorry, I don't understand this. -- Horst von Brand vonbrand@sleipnir.valparaiso.cl Casilla 9G, Viña del Mar, Chile +56 32 672616
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
|  |