[lkml]   [2003]   [Dec]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: udev sysfs docs Re: State of devfs in 2.6?
Måns Rullgård wrote:
> Miles Bader <> writes:
>>>>> 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's something I don't understand: I thought that with a well
>>>>configured hotplug+udev system, you'll never have to worry about loading
>>>>drivers on device-node open() because all drivers should be auto-loaded
>>>>and all device-nodes should be auto-created.
>>>No, you are correct. That's why I'm not really worried about this, and
>>>I don't think anyone else should be either.
>>Is there a specific case for which people want this feature?
>>Offhand it seems like a slightly odd thing to ask for...
> I believe the original motivation for module autoloading was to save
> memory by unloading modules when their devices were unused. Loading
> them automatically on demand made for less trouble for users, who
> didn't have to run modprobe manually to use the sound card, or
> whatever. This could still be a good thing in embedded systems.


And if you want to run this way with udev, set it up so device nodes
don't get deleted when the device unloads. That way you keep
device nodes for your driverless devices, and when you try to open
them the kernel runs modprobe for you. Devfs isn't needed for that
afaik, it is only needed for modprobing devices that doesn't have
a /dev entry yet.

Your /dev will contain nodes both for driven and non-driven
devices, but not for devices you don't have at all.

Helge Hafting

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:59    [W:0.121 / U:0.324 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site