From d2c332bc21267f5e01cb545d3f01cae1dcacdae3 Mon Sep 17 00:00:00 2001 From: Archaic Date: Thu, 13 Apr 2006 18:45:33 +0000 Subject: Merged the udev_update branch to trunk. git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@7509 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter06/changingowner.xml | 40 -------- chapter06/chapter06.xml | 6 +- chapter06/chroot.xml | 18 ++-- chapter06/createfiles.xml | 116 +++++++++++++++++++++- chapter06/creatingdirs.xml | 2 +- chapter06/devices.xml | 93 ------------------ chapter06/hotplug.xml | 223 ------------------------------------------ chapter06/introduction.xml | 7 -- chapter06/iproute2.xml | 4 +- chapter06/kernfs.xml | 79 +++++++++++---- chapter06/pkgmgt.xml | 8 -- chapter06/udev.xml | 233 ++++++++++++++++++++++++++++++++------------ 12 files changed, 356 insertions(+), 473 deletions(-) delete mode 100644 chapter06/changingowner.xml delete mode 100644 chapter06/devices.xml delete mode 100644 chapter06/hotplug.xml (limited to 'chapter06') diff --git a/chapter06/changingowner.xml b/chapter06/changingowner.xml deleted file mode 100644 index 83deca414..000000000 --- a/chapter06/changingowner.xml +++ /dev/null @@ -1,40 +0,0 @@ - - - %general-entities; -]> - - - - - Changing Ownership - - Currently, the /tools directory - is owned by the user lfs, a user - that exists only on the host system. Although the /tools directory can be deleted once the LFS - system has been finished, it can be retained to build additional LFS systems. - If the /tools directory is kept as is, - the files are owned by a user ID without a corresponding account. This is - dangerous because a user account created later could get this same user ID - and would own the /tools directory - and all the files therein, thus exposing these files to possible malicious - manipulation. - - To avoid this issue, add the lfs - user to the new LFS system later when creating the - /etc/passwd file, taking care to assign it the same user - and group IDs as on the host system. Alternatively, assign the contents of - the /tools directory to user - root by running the following - command: - -chown -R 0:0 /tools - - The command uses 0:0 instead of - root:root, because chown - is unable to resolve the name root until the - passwd file has been created. - - diff --git a/chapter06/chapter06.xml b/chapter06/chapter06.xml index 4186fd7bb..5715d6be9 100644 --- a/chapter06/chapter06.xml +++ b/chapter06/chapter06.xml @@ -12,14 +12,11 @@ Installing Basic System Software - + - - - @@ -53,7 +50,6 @@ - diff --git a/chapter06/chroot.xml b/chapter06/chroot.xml index ca3e86a92..ea213033e 100644 --- a/chapter06/chroot.xml +++ b/chapter06/chroot.xml @@ -44,16 +44,18 @@ reason, hashing is switched off by passing the +h option to bash. - It is important that all the commands throughout the remainder of this - chapter and the following chapters are run from within the chroot environment. - If you leave this environment for any reason (rebooting for example), remember - to first mount the proc and - devpts file systems (discussed - in the previous section) and enter chroot again before continuing with the - installations. - Note that the bash prompt will say I have no name! This is normal because the /etc/passwd file has not been created yet. + + It is important that all the commands throughout the remainder of this + chapter and the following chapters are run from within the chroot + environment. If you leave this environment for any reason (rebooting for + example), ensure that the virtual kernel filesystems are mounted as + explained in and and enter chroot again before continuing + with the installation. + + diff --git a/chapter06/createfiles.xml b/chapter06/createfiles.xml index ae22a241d..0cfc7596f 100644 --- a/chapter06/createfiles.xml +++ b/chapter06/createfiles.xml @@ -8,7 +8,31 @@ - Creating Essential Symlinks + Creating Essential Files and Symlinks + + + /etc/passwd + + + + /etc/group + + + + /var/run/utmp + + + + /var/log/btmp + + + + /var/log/lastlog + + + + /var/log/wtmp + Some programs use hard-wired paths to programs which do not exist yet. In order to satisfy these programs, create a number of symbolic links which will be @@ -20,4 +44,94 @@ ln -sv /tools/bin/perl /usr/bin ln -sv /tools/lib/libgcc_s.so{,.1} /usr/lib ln -sv bash /bin/sh + A proper Linux system maintains a list of the mounted file systems in + the file /etc/mtab. Normally, this file would be + created when we mount a new file system. Since we will not be mounting any + file systems inside our chroot environment, create an empty file for + utilities that expect the presence of /etc/mtab: + +touch /etc/mtab + + In order for user root to be + able to login and for the name root to be recognized, there + must be relevant entries in the /etc/passwd and + /etc/group files. + + Create the /etc/passwd file by running the following + command: + +cat > /etc/passwd << "EOF" +root:x:0:0:root:/root:/bin/bash +EOF + + The actual password for root + (the x used here is just a placeholder) will be set later. + + Create the /etc/group file by running the following + command: + +cat > /etc/group << "EOF" +root:x:0: +bin:x:1: +sys:x:2: +kmem:x:3: +tty:x:4: +tape:x:5: +daemon:x:6: +floppy:x:7: +disk:x:8: +lp:x:9: +dialout:x:10: +audio:x:11: +video:x:12: +utmp:x:13: +usb:x:14: +cdrom:x:15: +EOF + + The created groups are not part of any standard—they are groups + decided on in part by the requirements of the Udev configuration in this + chapter, and in part by common convention employed by a number of existing + Linux distributions. The Linux Standard Base (LSB, available at ) recommends only that, besides the group + root with a Group ID (GID) of 0, + a group bin with a GID of 1 be + present. All other group names and GIDs can be chosen freely by the system + administrator since well-written programs do not depend on GID numbers, but + rather use the group's name. + + To remove the I have no name! prompt, start a new + shell. Since a full Glibc was installed in and the + /etc/passwd and /etc/group + files have been created, user name and group name resolution will now + work. + +exec /tools/bin/bash --login +h + + Note the use of the +h directive. This tells + bash not to use its internal path hashing. Without this + directive, bash would remember the paths to binaries it has + executed. To ensure the use of the newly compiled binaries as soon as they are + installed, the +h directive will be used for the duration + of this chapter. + + The login, agetty, and + init programs (and others) use a number of log + files to record information such as who was logged into the system and + when. However, these programs will not write to the log files if they + do not already exist. Initialize the log files and give them + proper permissions: + +touch /var/run/utmp /var/log/{btmp,lastlog,wtmp} +chgrp -v utmp /var/run/utmp /var/log/lastlog +chmod -v 664 /var/run/utmp /var/log/lastlog + + The /var/run/utmp file records the users + that are currently logged in. The /var/log/wtmp + file records all logins and logouts. The + /var/log/lastlog file records when + each user last logged in. The /var/log/btmp file + records the bad login attempts. + diff --git a/chapter06/creatingdirs.xml b/chapter06/creatingdirs.xml index b9a269ebc..4e602b356 100644 --- a/chapter06/creatingdirs.xml +++ b/chapter06/creatingdirs.xml @@ -13,7 +13,7 @@ It is time to create some structure in the LFS file system. Create a standard directory tree by issuing the following commands: -install -dv /{bin,boot,dev,etc/opt,home,lib,mnt} +install -dv /{bin,boot,etc/opt,home,lib,mnt} install -dv /{sbin,srv,usr/local,var,opt} install -dv /root -m 0750 install -dv /tmp /var/tmp -m 1777 diff --git a/chapter06/devices.xml b/chapter06/devices.xml deleted file mode 100644 index 51821fe84..000000000 --- a/chapter06/devices.xml +++ /dev/null @@ -1,93 +0,0 @@ - - - %general-entities; -]> - - - - - Populating /dev - - - /dev/* - - - - Creating Initial Device Nodes - - When the kernel boots the system, it requires the presence of a few - device nodes, in particular the console - and null devices. The device nodes - will be created on the hard disk so that they are available before - udev has been started, and additionally when Linux is - started in single user mode (hence the restrictive permissions on - console). Create the devices by - running the following commands: - -mknod -m 600 /dev/console c 5 1 -mknod -m 666 /dev/null c 1 3 - - - - - Mounting tmpfs and Populating /dev - - The recommended method of populating the /dev directory with devices is to mount a - virtual filesystem (such as tmpfs) - on the /dev directory, and allow the - devices to be created dynamically on that virtual filesystem as they are - detected or accessed. This is generally done during the boot process. Since - this new system has not been booted, it is necessary to do what the - LFS-Bootscripts package would otherwise do by mounting /dev: - -mount -nvt tmpfs none /dev - - The Udev package is what actually creates the devices in the /dev directory. Since it will not be installed - until later on in the process, manually create the minimal set of device nodes - needed to complete the building of this system: - -mknod -m 622 /dev/console c 5 1 -mknod -m 666 /dev/null c 1 3 -mknod -m 666 /dev/zero c 1 5 -mknod -m 666 /dev/ptmx c 5 2 -mknod -m 666 /dev/tty c 5 0 -mknod -m 444 /dev/random c 1 8 -mknod -m 444 /dev/urandom c 1 9 -chown -v root:tty /dev/{console,ptmx,tty} - - There are some symlinks and directories required by LFS that are - created during system startup by the LFS-Bootscripts package. Since this - is a chroot environment and not a booted environment, those symlinks and - directories need to be created here: - -ln -sv /proc/self/fd /dev/fd -ln -sv /proc/self/fd/0 /dev/stdin -ln -sv /proc/self/fd/1 /dev/stdout -ln -sv /proc/self/fd/2 /dev/stderr -ln -sv /proc/kcore /dev/core -mkdir -v /dev/pts -mkdir -v /dev/shm - - Finally, mount the proper virtual (kernel) file systems on the - newly-created directories: - -mount -vt devpts -o gid=4,mode=620 none /dev/pts -mount -vt tmpfs none /dev/shm - - The mount commands executed above may result - in the following warning message: - -can't open /etc/fstab: No such file or directory. - - This file—/etc/fstab—has not - been created yet but is also not required for the file systems to be - properly mounted. As such, the warning can be safely ignored. - - - - diff --git a/chapter06/hotplug.xml b/chapter06/hotplug.xml deleted file mode 100644 index d66e0c7e7..000000000 --- a/chapter06/hotplug.xml +++ /dev/null @@ -1,223 +0,0 @@ - - - %general-entities; -]> - - - - - Hotplug-&hotplug-version; - - - Hotplug - - - - - - <para>The Hotplug package contains scripts that react upon hotplug events - generated by the kernel. Such events correspond to every change in the kernel - state visible in the <systemitem class="filesystem">sysfs</systemitem> - filesystem, e.g., the addition and removal of hardware. This package also - detects existing hardware during boot and inserts the relevant modules into the - running kernel.</para> - - <segmentedlist> - <segtitle>&buildtime;</segtitle> - <segtitle>&diskspace;</segtitle> - - <seglistitem> - <seg>0.01 SBU</seg> - <seg>460 KB</seg> - </seglistitem> - </segmentedlist> - - <segmentedlist> - <segtitle>&dependencies;</segtitle> - - <seglistitem> - <seg>Bash, Coreutils, Findutils, Gawk, and Make</seg> - </seglistitem> - </segmentedlist> - - </sect2> - - <sect2 role="installation"> - <title>Installation of Hotplug - - This package does not come with a test suite. - - Install the Hotplug package: - -make install - - Copy a file that the install target omits. - -cp -v etc/hotplug/pnp.distmap /etc/hotplug - - Remove the init script that Hotplug installs since we are going to be - using the script included in the LFS-Bootscripts package: - -rm -rfv /etc/init.d - - Network device hotplugging is not yet supported by the LFS-Bootscripts - package. For that reason, remove the network hotplug agent: - -rm -fv /etc/hotplug/net.agent - - Create a directory for storing firmware that can be loaded by - hotplug: - -mkdir -v /lib/firmware - - - - - - Contents of Hotplug - - - Installed program - Installed scripts - Installed files - - - hotplug - /etc/hotplug/*.rc, /etc/hotplug/*.agent - /etc/hotplug/hotplug.functions, /etc/hotplug/blacklist, - /etc/hotplug/{pci,usb}, /etc/hotplug/usb.usermap, /etc/hotplug.d, - and /var/log/hotplug/events - - - - - Short Descriptions - - - - - hotplug - - This script is called by default by the Linux kernel when - something changes in its internal state (e.g., a new device is - added or an existing device is removed) - - hotplug - - - - - - /etc/hotplug/*.rc - - These scripts are used for cold plugging, i.e., detecting and - acting upon hardware already present during system startup. They are - called by the hotplug initscript included in - the LFS-Bootscripts package. The *.rc scripts try - to recover hotplug events that were lost during system boot because, - for example, the root filesystem was not mounted by the kernel - - /etc/hotplug/*.rc - - - - - - /etc/hotplug/*.agent - - These scripts are called by hotplug in response - to different types of hotplug events generated by the kernel. Their - action is to insert corresponding kernel modules and call any - user-provided scripts - - /etc/hotplug/*.agent - - - - - - /etc/hotplug/blacklist - - This file contains the list of modules that should never be - inserted into the kernel by the Hotplug scripts - - /etc/hotplug/blacklist - - - - - - /etc/hotplug/hotplug.functions - - This file contains common functions used by other scripts in the - Hotplug package - - /etc/hotplug/hotplug.functions - - - - - - /etc/hotplug/{pci,usb} - - These directories contain user-written handlers for hotplug - events - - /etc/hotplug/{pci,usb} - - - - - - /etc/hotplug/usb.usermap - - This file contains rules that determine which user-defined handlers to - call for each USB device, based on its vendor ID and other - attributes - - /etc/hotplug/usb.usermap - - - - - - /etc/hotplug.d - - This directory contains programs (or symlinks to them) that are - interested in receiving hotplug events. For example, Udev puts its - symlink here during installation - - /etc/hotplug.d - - - - - - /lib/firmware - - This directory contains the firmware for devices that need to - have their firmware loaded before use - - /lib/firmware - - - - - - /var/log/hotplug/events - - This file contains all the events that hotplug - has called since bootup - - /var/log/hotplug/events - - - - - - - - - diff --git a/chapter06/introduction.xml b/chapter06/introduction.xml index 5e9cfd5c3..588d84780 100644 --- a/chapter06/introduction.xml +++ b/chapter06/introduction.xml @@ -55,11 +55,4 @@ there is a list of programs and libraries (along with brief descriptions of these) that the package installs. - - At this point, you may wish to keep your finished temporary - tools for use in future LFS builds by creating a tarball of the - /tools directory and - storing it in a safe location. - - diff --git a/chapter06/iproute2.xml b/chapter06/iproute2.xml index 84e4244e0..fdf93aa08 100644 --- a/chapter06/iproute2.xml +++ b/chapter06/iproute2.xml @@ -25,8 +25,8 @@ &diskspace; - 0.1 SBU - 4.3 MB + 0.2 SBU + 4.8 MB diff --git a/chapter06/kernfs.xml b/chapter06/kernfs.xml index 2bdf9f9c3..3c9e68c0b 100644 --- a/chapter06/kernfs.xml +++ b/chapter06/kernfs.xml @@ -8,33 +8,72 @@ - Mounting Virtual Kernel File Systems + Preparing Virtual Kernel File Systems - Various file systems exported by the kernel are used to communicate to and - from the kernel itself. These file systems are virtual in that no disk space is - used for them. The content of the file systems resides in memory. + + /dev/* + - Begin by creating directories onto which the file systems will be - mounted: + Various file systems exported by the kernel are used to communicate to + and from the kernel itself. These file systems are virtual in that no disk + space is used for them. The content of the file systems resides in + memory. -mkdir -pv $LFS/{proc,sys} + Begin by creating directories onto which the file systems will be + mounted: - Now mount the file systems: +mkdir -pv $LFS/{dev,proc,sys} -mount -vt proc proc $LFS/proc -mount -vt sysfs sysfs $LFS/sys + + Creating Initial Device Nodes + + When the kernel boots the system, it requires the presence of a few + device nodes, in particular the console and null devices. The device nodes will be created + on the hard disk so that they are available before udev + has been started, and additionally when Linux is started in single user mode + (hence the restrictive permissions on console). Create the devices by running the + following commands: + +mknod -m 600 $LFS/dev/console c 5 1 +mknod -m 666 $LFS/dev/null c 1 3 + + + + + Mounting and Populating /dev - Remember that if for any reason you stop working on the LFS - system and start again later, it is important to check that these file - systems are mounted again before entering the chroot - environment. + The recommended method of populating the /dev directory with devices is to mount a + virtual filesystem (such as tmpfs) on the /dev directory, and allow the devices to be + created dynamically on that virtual filesystem as they are detected or + accessed. This is generally done during the boot process by Udev. Since + this new system does not yet have Udev and has not yet been booted, it is + necessary to mount and populate /dev manually. This is accomplished by bind + mounting the host system's /dev + directory. A bind mount is a special type of mount that allows you to + create a mirror of a directory or mount point to some other location. Use + the following command to achieve this: - Additional file systems will soon be mounted from within the - chroot environment. To keep the host up to date, perform a fake - mount for each of these now: +mount --bind /dev $LFS/dev + + + + + Mounting Virtual Kernel File Systems + + Now mount the remaining virtual kernel filesystems: + +mount -vt devpts devpts $LFS/dev/pts +mount -vt tmpfs shm $LFS/dev/shm +mount -vt proc proc $LFS/proc +mount -vt sysfs sysfs $LFS/sys -mount -vft tmpfs tmpfs $LFS/dev -mount -vft tmpfs tmpfs $LFS/dev/shm -mount -vft devpts -o gid=4,mode=620 devpts $LFS/dev/pts + diff --git a/chapter06/pkgmgt.xml b/chapter06/pkgmgt.xml index 76ea123e2..4ce94106d 100644 --- a/chapter06/pkgmgt.xml +++ b/chapter06/pkgmgt.xml @@ -39,14 +39,6 @@ the Hints subproject and see if one of them fits your need. - - As no particular package management technique is mentioned in LFS, - the commands in the remainder of this book must be performed while logged in - as user root and no longer as user - lfs. Also, double check that - $LFS is set. - - Upgrade Issues diff --git a/chapter06/udev.xml b/chapter06/udev.xml index 96d2ec579..f78ab1cec 100644 --- a/chapter06/udev.xml +++ b/chapter06/udev.xml @@ -26,7 +26,7 @@ 0.1 SBU - 3.8 MB + 4.8 MB @@ -43,19 +43,31 @@ Installation of Udev + Create some devices and directories that Udev cannot handle due to + them being required very early in the boot process: + +install -dv /lib/{firmware,udev/devices/{pts,shm}} +mknod -m0666 /lib/udev/devices/null c 1 3 +ln -sv /proc/self/fd /lib/udev/devices/fd +ln -sv /proc/self/fd/0 /lib/udev/devices/stdin +ln -sv /proc/self/fd/1 /lib/udev/devices/stdout +ln -sv /proc/self/fd/2 /lib/udev/devices/stderr +ln -sv /proc/kcore /lib/udev/devices/core + Compile the package: -make EXTRAS=extras/run_directory +make EXTRAS="extras/ata_id extras/cdrom_id extras/edd_id \ + extras/firmware extras/floppy extras/scsi_id \ + extras/usb_id extras/volume_id" The meaning of the make option: - EXTRAS=extras/run_directory + EXTRAS=... - This builds the udev_run_devd and - udev_run_hotplugd binaries, which are required - for correct handling of hotpluggable devices. + This builds several helper binaries that can aid in writing custom + Udev rules. @@ -66,7 +78,10 @@ Install the package: -make DESTDIR=/ EXTRAS=extras/run_directory install +make DESTDIR=/ \ + EXTRAS="extras/ata_id extras/cdrom_id extras/edd_id \ + extras/firmware extras/floppy extras/scsi_id \ + extras/usb_id extras/volume_id" install The meaning of the make parameter: @@ -87,16 +102,78 @@ cp -v ../&udev-config-file; /etc/udev/rules.d/25-lfs.rules + Create some rules that work around broken sysfs attribute creation + timing in linux-2.6.15: + +cat >> /etc/udev/rules.d/10-wait_for_sysfs.rules << "EOF" +ACTION=="add", DEVPATH=="/devices/*", ENV{PHYSDEVBUS}=="?*", WAIT_FOR_SYSFS="bus" +ACTION=="add", SUBSYSTEM=="net", WAIT_FOR_SYSFS="address" +EOF + Install the documentation that explains how to create Udev rules: install -m644 -D -v docs/writing_udev_rules/index.html /usr/share/doc/udev-&udev-version;/index.html - - - Run the udevstart program to create our full - complement of device nodes. - -/sbin/udevstart + + + When Udev is started by the LFS-Bootscripts, a replay of all kernel + device events happens. These events tell Udev what devices exist. + Sometimes the Udev bootscript doesn't wait long enough for + udevd to process all of the replayed events and + consequently the devices for those missed events are not created before the + script exits. Since udevd is still running in the + background, the devices will be created a few milliseconds later, but the + next bootscript to run may require a device to exist before it has been + created. To avoid such missed events, and to avoid hardcoding an overly + long wait time, It is recommended that you run the following commands to + aid the LFS development team in debugging these missed events and finding + an acceptable solution more quickly. + + First, create a simple C file: + +cat > bug.c << EOF +/* Simple event recorder */ +#define _GNU_SOURCE +#include <sys/types.h> +#include <sys/stat.h> +#include <fcntl.h> +#include <unistd.h> +#include <stdlib.h> +#include <argz.h> +int main(int argc, char * argv[]) +{ + char * envz; + size_t len; + int bug; + bug = open("/dev/bug", O_WRONLY | O_APPEND); + if (bug == -1) + return 0; + setenv("_SEPARATOR", "--------------------------------------", 1); + argz_create(environ, &envz, &len); + argz_stringify(envz, len, '\n'); + envz[len-1]='\n'; + write(bug, envz, len); + close(bug); + free(envz); + return 0; +} +EOF + + Now compile it: + +gcc -o /lib/udev/bug bug.c + + The next step adds a simple logging rule to run this program. + +cat > /etc/udev/rules.d/90-bug.rules << "EOF" +ACTION=="add", RUN+="bug" +EOF + + When booting the new LFS system, if any events are missed, a warning + message will appear and a /dev/bugreport file will be + created. The warning message will tell you where to send feedback. + + @@ -108,8 +185,9 @@ Installed directory - udev, udev_run_devd, udev_run_hotplugd, udevcontrol, udevd, - udevinfo, udevmonitor, udevsend, udevstart, and udevtest + ata_id, cdrom_id, create_floppy_devices, edd_id, firmware_helper, + scsi_id, udevcontrol, udevd, udevinfo, udevmonitor, udevtest, usb_id + and vol_id /etc/udev @@ -119,38 +197,66 @@ - - udev + + ata_id + + Provides Udev with a unique string and + additional information (uuid, label) for an ATA drive + + ata_id + + + + + + cdrom_id + + Provides Udev with the capabilities of a + CD-ROM or DVD-ROM drive + + cdrom_id + + + + + + create_floppy_devices - Creates device nodes in /dev - or renames network interfaces (not in LFS) in response to hotplug - events - - udev + Creates all possible floppy devices based on the CMOS type + + create_floppy_devices - - udev_run_devd + + edd_id - Executes programs and scripts in the /etc/dev.d/ directory in response to - hotplug events - - udev_run_devd + Provides Udev with the EDD ID for a BIOS disk drive + + edd_id - - udev_run_hotplugd + + firmware_helper - Executes programs and scripts in the /etc/hotplug.d/ directory in response - to hotplug events - - udev_run_hotplugd + Uploads firmware to devices + + firmware_helper + + + + + + scsi_id + + Provides Udev with a unique SCSI identifier + based on the data returned from sending a SCSI INQUIRY command to + the specified device + + scsi_id @@ -169,8 +275,9 @@ udevd - A daemon that reorders hotplug events before submitting them to - udev, thus avoiding various race conditions + A daemon that listens for uevents on the netlink socket, + creates devices and runs the configured external programs in + response to these uevents udevd @@ -180,7 +287,7 @@ udevinfo - Allows users to query the udev database for + Allows users to query the Udev database for information on any device currently present on the system; it also provides a way to query any device in the sysfs tree to help create udev @@ -194,48 +301,44 @@ udevmonitor - Prints the event received from the kernel and the event which - udev sends out after rule processing + Prints the event received from the kernel and the environment + which Udev sends out after rule processing udevmonitor - - udevsend + + udevtest - Delivers hotplug events to udevd - - udevsend + Simulates a uevent for the given device, and prints out the + name of the node the real udevd would have created, + or the name of the renamed network interface + + udevtest - - udevstart + + usb_id - Creates device nodes in /dev - that correspond to drivers compiled directly into the kernel; it - performs that task by simulating hotplug events presumably dropped by - the kernel before invocation of this program (e.g., because the root - filesystem has not been mounted) and submitting such synthetic hotplug - events to udev - - udevstart + Provides Udev with information about USB + devices + + usb_id - - udevtest + + vol_id - Simulates a udev run for the given device, - and prints out the name of the node the real udev - would have created or (not in LFS) the name of the renamed network - interface - - udevtest + Provides Udev with the label and uuid of a + filesystem + + vol_id @@ -243,7 +346,7 @@ /etc/udev - Contains udev configuation files, + Contains Udev configuation files, device permissions, and rules for device naming /etc/udev -- cgit v1.2.3-54-g00ecf