Re: udev in initrd

[Alan Cox <alan redhat com>]

On Tue, Jul 06, 2004 at 06:17:07PM +0200, Owen Taylor wrote:
> Clearly there has to be a policy about how devices are named; it's
> just one of the things that has to be there for a stable usable
> system. Having a simple C program that can read a policy 
> description file and name devices would certainly be vastly more
> efficient way of doing things than all the shell scripts that 
> udev runs.
> 
> But udev exists now, and that's a big advantage for it.

Rewriting udev in C is practical, that implies the concept is right but
the implementation can be optimised. That puts it in the same class as
openoffice, gnome and most of our config tools so I don't see it as a 
barrier. What has to be right is the interface