Messages in this thread | | | Date | Wed, 10 Dec 2003 09:13:20 +0100 | From | Jakob Oestergaard <> | Subject | Re: udev sysfs docs Re: State of devfs in 2.6? |
| |
On Mon, Dec 08, 2003 at 11:56:20PM -0800, Greg KH wrote: > On Tue, Dec 09, 2003 at 06:17:28AM +0100, Witukind wrote: > > From the udev FAQ: > > > > Q: But udev will not automatically load a driver if a /dev node is opened > > when it is not present like devfs will do. > > A: If you really require this functionality, then use devfs. It is still > > present in the kernel. > > > > Will it have this 'equivalent functionality' some day? > > Heh, no. I really don't believe all of the people who keep asking me > this. I think I need to reword this answer to something like: > A: That is correct. If you really require this functionality, then > use devfs. There is no way that udev can support this, and it > never will. > > That better? :)
No Greg. People keep asking, because you continue to give an answer that is 'correct' but does not answer the question people 'meant' to ask.
Andreas Jellinghaus <aj@dungeon.inka.de> gave an excellent answer - which I shall blatantly quote:
------------------------- Q: devfs did load drivers when someone tried to open() a non existing device. will sysfs/hotplug/udev do this?
A: there is no need to. hotplug/sysfs/udev will create devices for all hardware supported by the kernel and the available modules. it will do that during boot up, and whenever new hardware is added. so you can expect all devices be already present, no need for a devfs like mechanism. -------------------------
And there you have it :)
/ jakob
- 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/
| |