Re: [ANNOUNCE] udev 011 release

[Rob Love <rml@ximian.com>]

On Sat, 2003-12-27 at 21:04, J.A. Magallon wrote:

> This means that it will try to run, for example, gpm before the device for
> the mouse is created (as I said, if you booted with an empty /dev you want
> to populate with device nodes).

Yah, I guess it ought to go lower, so long as sysfs is sufficiently
mounted before it runs.

The reason I put it at 20 was that it really does not matter.  udev is
not a functional replacement for a static /dev while we do not have
initramfs.  Once we have udev working during early boot, we won't need
the initscripts.

> And a couple questions.
> a) Should not ordering be reversed here:
> 
>   start)
>     if [ ! -d $udev_dir ]; then
>         mkdir $udev_dir
>     fi
>     if [ ! -d $sysfs_dir ]; then
>         exit 1
>     fi
>   If we have not /sys, there's no sense on creating /udev, so I would check first
>   for /sys.

Makes sense.

> b) What is the sense of removing devices when udev is stopped ? As I understand
>   it, udev is not 'running', it is just a command to create device nodes, called 
>   by hotplug.

Because if you have your udev on a persistent storage media (e.g., ext3,
like most of us) then it is nice to clear it out across reboots.

	Rob Love




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel