Changeset aabd480 for chapter07/udev.xml


Ignore:
Timestamp:
07/01/2005 11:16:14 PM (19 years ago)
Author:
Archaic <archaic@…>
Branches:
6.1, 6.1.1
Children:
808f5af
Parents:
90b56f5
Message:

Brought all occurences of LFS-Bootscripts into conformity. (merged from trunk r6288)

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/branches/6.1/BOOK@6308 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:
1 edited

Legend:

Unmodified
Added
Removed

  • chapter07/udev.xml

    r90b56f5 raabd480  
    8383processes and to <command>udev</command> for device node creation.</para>
    8484
    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
     86device 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
     91class="filesystem">/sys</systemitem> filesystem and creates devices under
     92<filename class="directory">/dev</filename> that match the descriptions.  For
     93example, <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
     97the <filename class="directory">/dev</filename> directory are configured
     98according to the rules specified in the files within the <filename
     99class="directory">/etc/udev/rules.d/</filename> directory. These are numbered in
     100a similar fashion to the LFS-Bootscripts package. If <command>udev</command>
     101can'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>
    106103
    107104<para>Once the above stage is complete, all devices that were already
Note: See TracChangeset for help on using the changeset viewer.