RFC: new/changed udev rules - Part 1

Archaic archaic at linuxfromscratch.org
Sun May 14 20:44:41 PDT 2006

On Sun, May 14, 2006 at 08:09:49PM -0700, Jim Gifford wrote:
> So far my system that has 4 ide cd drives and 4 scsi devices, hasn't 
> seen any problems. From what I can see there has to be some way in sysfs 
> that we can use instead of using the Debian method, which something 
> about that script bugs me(a script that writes rules for itself doesn't 
> seem right to me)

If the order of uevents isn't predictable (which it isn't) then the
symlink cannot be predictable, either. Therefore, there is no
persistance. It make take you 50 reboots for the order to be different,
but the fact remains.

Persistance is, as best as I can tell, accessing a device via a known
symlink. The physical location of the drives is irrelevant to me, the
end user, because I'm using the symlink, so I don't want to worry about
whether it is /dev/hda, /dev/hdb, or whatever. So now, what happens if I
add/remove/move hardware which cause driveX to change from /dev/hda to
/dev/hdb. The symlink I had been using previously is now broken insofar
that it isn't the device I expect it to be. This is why the current LFS
method exists. A rule file will be generated for these devices only
once. This generated file is completely customizable, and those device
symlinks will never change. Plus, and new devices added will
automatically be added to the generated file (again, each device is
added only one time). It seems like a win-win.


Want control, education, and security from your operating system?
Hardened Linux From Scratch

More information about the lfs-dev mailing list