Messages in this thread | | | Subject | Re: [ANNOUNCE] udev 011 release | From | Rob Love <> | Date | Sat, 27 Dec 2003 21:19:14 -0500 |
| |
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
- 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/
| |