Changeset f3317d4 for chapter07/udev.xml
- Timestamp:
- 02/15/2013 09:14:37 PM (11 years ago)
- Branches:
- 7.5-systemd, 7.6-systemd, 7.7-systemd, 7.8-systemd, 7.9-systemd
- Children:
- b588d62
- Parents:
- 4a4e017
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter07/udev.xml
r4a4e017 rf3317d4 120 120 whatever <systemitem class="filesystem">devtmpfs</systemitem> used 121 121 initially.</para> </sect3> 122 123 <sect3>124 <title>Udev Bootscripts</title>125 126 <para>The first LFS bootscript,127 <filename>/etc/init.d/mountvirtfs</filename> will copy any devices128 located in <filename class="directory">/lib/udev/devices</filename> to129 <filename class="directory">/dev</filename>. This is necessary because130 some devices, directories, and symlinks are needed before the dynamic131 device handling processes are available during the early stages of132 booting a system, or are required by <command>udevd</command> itself.133 Creating static device nodes in <filename134 class="directory">/lib/udev/devices</filename> also provides an easy135 workaround for devices that are not supported by the dynamic device136 handling infrastructure.</para>137 138 <para>The <filename>/etc/rc.d/init.d/udev</filename> initscript starts139 <command>udevd</command>, triggers any "coldplug" devices that have140 already been created by the kernel and waits for any rules to complete.141 The script also unsets the uevent handler from the default of142 <filename>/sbin/hotplug </filename>. This is done because the kernel no143 longer needs to call out to an external binary. Instead144 <command>udevd</command> will listen on a netlink socket for uevents that145 the kernel raises.</para>146 147 <para>The <command>/etc/rc.d/init.d/udev_retry</command> initscript takes148 care of re-triggering events for subsystems whose rules may rely on149 filesystems that are not mounted until the <command>mountfs</command>150 script is run (in particular, <filename class="directory">/usr</filename>151 and <filename class="directory">/var</filename> may cause this). This152 script runs after the <command>mountfs</command> script, so those rules153 (if re-triggered) should succeed the second time around. It is154 configured from the <filename>/etc/sysconfig/udev_retry</filename> file;155 any words in this file other than comments are considered subsystem names156 to trigger at retry time. To find the subsystem of a device, use157 <command>udevadm info --attribute-walk <device></command> where158 <device> is a an absolure path in /dev or /sys such as /dev/sr0 or159 /sys/class/rtc.</para>160 161 </sect3>162 122 163 123 <sect3>
Note:
See TracChangeset
for help on using the changeset viewer.