Author: archaic Date: 2006-05-12 17:49:00 -0600 (Fri, 12 May 2006) New Revision: 7602
Modified: trunk/udev-config/25-lfs.rules Log: Added explanatory comments to 25-lfs.rules. Modified: trunk/udev-config/25-lfs.rules =================================================================== --- trunk/udev-config/25-lfs.rules 2006-05-12 23:29:17 UTC (rev 7601) +++ trunk/udev-config/25-lfs.rules 2006-05-12 23:49:00 UTC (rev 7602) @@ -1,4 +1,26 @@ -# /etc/udev/rules.d/25-lfs.rules: Rule definitions for LFS. +# In the following example, each comma-separated section will be explained. +# +# KERNEL=="mice", MODE="0644", GROUP="some group", NAME="input/%k", SYMLINK="mouse" +# +# In the first section, a uevent generated by the kernel with the name "mice" +# will cause a device node named "mice" to be created in the default location of +# /dev with a default ownership of root:root and default permissions of 0660. In +# the next 2 sections we change the default permissions and group ownership +# depending on needs. In the 4th section, we change where the device node will +# be created (in this example we want /dev/input/mice instead of /dev/mice). The +# last section says to create a symlink in /dev/mouse. +# +# Keep in mind that /dev is the default location for nodes and symlinks. If you +# want a node or symlink in a subdirectory, you have to specify it (for example: +# SYMLINK="input/mouse" would create a /dev/input/mouse symlink) +# +# If for some reason you do not want a device node created for hardware that is +# present, give it a blank NAME. An example would be DRI devices. X Windows will +# handle those itself. +# +# A final word of caution: Any particular rule must be written on one line and a +# comma must separate each section of the rule. You can have either spaces or +# tabs between each section. # Core kernel devices -- http://linuxfromscratch.org/mailman/listinfo/lfs-book FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
