![]() | |||||||||||||
Messages in this thread |
Mike Bell wrote: > On Tue, Feb 10, 2004 at 02:20:19PM +0100, Helge Hafting wrote: > >>Non-devfs setups (with or without udev) support a similiar trigger >>mechanism for module loading, that is simpler to set up and understand. >>And that is a persistend device node. Plain, simple, and ls sees it too. >>Open it and the device is loaded as needed. And at open time, not >>at lookup time. Load at lookup time might not be necessary, after all. > > > This doesn't work anymore if you move to dynamic device numbers, nor Sure. Completely random device numbers will make this demand loading of device drivers impossible. Either it won't happen (all numbers won't be completely random, although they may get more dynamic than today) or module loading based on device node opening will be deprecated. This won't mean the end of dynamic loading, you will merely need to load modules explicit before you get a device node. > does it work cleanly if /dev is on tmpfs or something else that doesn't > persist between reboots (that's one of the things I like about devfs, > being able to use it with a RO root.) Still possible. Boot script (possibly the udev startup script) copies a handful of device nodes from the RO root into the tmpfs /dev. Helge Hafting - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-03-22 14:00 [from the cache] ©2003-2008 | |||||||||||||