Re: udev and devfs - The final word

Helge Hafting
2004-01-09T08:39:48Z

Andrey Borzenkov wrote:
>>So, how does devfs stack up to the above problems and constraints:
>> Problems:
>> 1) devfs only shows the dev entries for the devices in the system.
>
>
> Is this a problem? Where exactly this problem lies?
>

Some people like to unload their (modular) devices so they don't use
memory when not in use. This saves them a few kB.
It is then useful to have the device node sitting there anyway, functioning
as a trigger. The kernel will autoload the module when the device is opened,
but that won't happen if there's no device node to open.

This approach can be made to work with devfs too - by splitting the device
into two pieces. One that manages the device node, and autoloads the rest
when needed.

>
>> 2) devfs does not handle the need for dynamic major/minor numbers
>
>
> Neither does udev. Both take whatever driver gives them.
>
>
>> 3) devfs does not provide a way to name devices in a persistent
>> fashion.
>
>
> I am not sure what exactly you mean here.
>
Probably something like
mv /dev/hda /dev/mydisk
and have it remembered upon the next reboot. devfsd can do that though.

>
>> 4) devfs does provide a deamon that userspace programs can hook > into
>> to listen to see what devices are being created or removed.
>> Constraints:
>> 1) devfs forces the devfs naming policy into the kernel. If you
>> don't like this naming scheme, tough.
>
>
> kernel imposes naming scheme for exporting devices in sysfs. It is
> possible to get rid of devfs_name in kernel and use those names
> that must exist anyway to support udev as well. devfs has
> devfsd that can call whatever naming agent you like.
>
>
>> 2) devfs does not follow the LSB device naming standard.
>
>
> it is user-space (devfsd) issue, not kernel space (devfs)
>
>
>> 3) devfs is small, and embedded devices use it. However it is
>> implemented in non-pagable memory.
>
>
> Same for sysfs. Other Unices have pageable kernel memory. If Linux
> had it any memory based filesystem could benefit from it. I did not
> look at backing store for sysfs patches but it is likely that same
> idea could be used for devfs.
>
>
>>Oh yeah, and there are the insolvable race conditions with the devfs
>>implementation in the kernel, but I'm not going to talk about them > right
>
>
> I do not argue that current devfs implementation is ugly and racy. I
> just beg you to point at what makes those races "unsolvable".
>
They are of course not unsolvable. Those understanding them seems
to believe that a complete rewrite will be easier than the rather
invasive changes necessary to fix the races. This is why the
_current implementation_ is marked obsolete. Nobody is volunteering
to fix devfs or rewrite it though.

Helge Hafting