rule verification

Archaic archaic at
Tue May 2 21:37:31 PDT 2006

On Wed, May 03, 2006 at 10:02:48AM +0600, Alexander E. Patrakov wrote:
> KERNEL=="capi", NAME="capi20",  SYMLINK="isdn/capi20"
> KERNEL=="capi*", NAME="capi/%n", GROUP="dialout"
> Won't the second rule match the bare "capi" device and thus hide the result 
> of the first one?

At one time it was (or at least was believed) that the 1st rule to match
won. In that is still true, then the above construct makes sense. If it
isn't true, then what order are the rules processed in?

> KERNEL=="s[grt][0-9]*",                 GROUP="disk"


> KERNEL=="scd[0-9]*",                    GROUP="cdrom"


> Also, just for cleanness, I suggest to move all rules from 25-lfs.rules 
> with the "RUN" in them to a separate file, 25-run.rules.

Modular is good. :) I moved the modprobe rules to 26-modprobe.rules and
the firmware one to 27-firmware.rules. Of course, this is still POC
stuff and the layout is still forming.

> The SuSE-specific rules about "timeout" are dubious and are better
> commented out.

That's messy looking. I removed them altogether. Re-adding them would be
trivial. Jim?

> Raw USB long rule has to be added to LFS (to 25-lfs.rules) because it deals 
> with naming (you may want to change SYMLINK+= to NAME=).

I take it you are referring to:
SUBSYSTEM=="usb_device", PROGRAM="/bin/sh -c 'X=%k X=$${X#usbdev} B=$${X%%%%.*} D=$${X#*.}; echo bus/usb/$$B/$$D'", NAME="%c"

I put it at the beginning of the USB section.

The new tarball is here:


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

More information about the lfs-dev mailing list