Changeset fde4f7d for chapter07/udev.xml
- Timestamp:
- 07/01/2005 08:39:25 PM (19 years ago)
- Branches:
- 10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- d001e2b
- Parents:
- 4d938ef
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter07/udev.xml
r4d938ef rfde4f7d 83 83 processes and to <command>udev</command> for device node creation.</para> 84 84 85 <para>The <command>S10udev</command> initscript takes care of creating 86 these device nodes when Linux is booted. This script starts with 87 registering <command>/sbin/udevsend</command> as a hotplug event handler. 88 Hotplug events (discussed below) should not be generated during this 89 stage, but <command>udev</command> is registered just in case they do 90 occur. The <command>udevstart</command> program then walks through 91 the <systemitem class="filesystem">/sys</systemitem> filesystem and 92 creates devices under <filename class="directory">/dev</filename> that 93 match the descriptions. For example, 94 <filename>/sys/class/tty/vcs/dev</filename> contains the string 95 <quote>7:0</quote> This string is used by <command>udevstart</command> 96 to create <filename>/dev/vcs</filename> with major number 97 <emphasis>7</emphasis> and minor <emphasis>0</emphasis>. The names and 98 permissions of the nodes created under the 99 <filename class="directory">/dev</filename> directory are configured according 100 to the rules specified in the files within the 101 <filename class="directory">/etc/udev/rules.d/</filename> directory. These are 102 numbered in a similar fashion to the LFS bootscripts. If 103 <command>udev</command> can't find a rule for the device it is creating, it will 104 default permissions to <emphasis>660</emphasis> and ownership to 105 <emphasis>root:root</emphasis>.</para> 85 <para>The <command>S10udev</command> initscript takes care of creating these 86 device nodes when Linux is booted. This script starts with registering 87 <command>/sbin/udevsend</command> as a hotplug event handler. Hotplug events 88 (discussed below) should not be generated during this stage, but 89 <command>udev</command> is registered just in case they do occur. The 90 <command>udevstart</command> program then walks through the <systemitem 91 class="filesystem">/sys</systemitem> filesystem and creates devices under 92 <filename class="directory">/dev</filename> that match the descriptions. For 93 example, <filename>/sys/class/tty/vcs/dev</filename> contains the string 94 <quote>7:0</quote> This string is used by <command>udevstart</command> to create 95 <filename>/dev/vcs</filename> with major number <emphasis>7</emphasis> and minor 96 <emphasis>0</emphasis>. The names and permissions of the nodes created under 97 the <filename class="directory">/dev</filename> directory are configured 98 according to the rules specified in the files within the <filename 99 class="directory">/etc/udev/rules.d/</filename> directory. These are numbered in 100 a similar fashion to the LFS-Bootscripts package. If <command>udev</command> 101 can't find a rule for the device it is creating, it will default permissions to 102 <emphasis>660</emphasis> and ownership to <emphasis>root:root</emphasis>.</para> 106 103 107 104 <para>Once the above stage is complete, all devices that were already
Note:
See TracChangeset
for help on using the changeset viewer.