Ignore:
Timestamp:
08/08/2004 02:11:09 AM (20 years ago)
Author:
Gerard Beekmans <gerard@…>
Branches:
6.0
Children:
5ba3d1d
Parents:
6e41459
Message:

Completed global edits for upcoming 6.0 release

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

File:
1 edited

Legend:

Unmodified
Added
Removed

  • chapter06/devices.xml

    r6e41459 ref13657  
    1111
    1212<sect2>
    13 <title>Creating initial device nodes</title>
     13<title>Creating Initial Device Nodes</title>
    1414
    1515<para>When the kernel boots the system, it requires the presence of a few device
    1616nodes, in particular the <filename class="devicefile">console</filename> and
    17 <filename class="devicefile">null</filename> devices:</para>
     17<filename class="devicefile">null</filename> devices. Create these by
     18running the following commands:</para>
    1819
    1920<screen><userinput>mknod -m 600 /dev/console c 5 1
    … …  
    2425<title>Mounting ramfs and populating /dev</title>
    2526
    26 <para>The ideal way to populate <filename class="directory">/dev</filename> is
    27 to mount a <systemitem class="filesystem">ramfs</systemitem> onto <filename class="directory">/dev </filename>
    28 like <systemitem class="filesystem">tmpfs</systemitem>, but it
    29 cannot be swapped) and create the devices on there during each bootup.  Since we haven't
    30 booted the system, we have to do what the bootscripts would otherwise do for us, and
    31 populate <filename class="directory">/dev</filename> ourselves.  Begin by mounting <filename class="directory">/dev</filename>:</para>
     27<para>The ideal way to populate <filename
     28class="directory">/dev</filename> is to mount a ramfs onto <filename
     29class="directory">/dev</filename> like <systemitem
     30class="filesystem">tmpfs</systemitem>, and create the devices on there
     31during each bootup. Since the system has not been booted, it is
     32necessary to do what the bootscripts would otherwise do and populate
     33<filename class="directory">/dev</filename>. Begin by mounting
     34<filename class="directory">/dev</filename>:</para>
    3235
    3336<screen><userinput>mount -n -t ramfs none /dev</userinput></screen>
    3437
    35 <para>Now use the provided udevstart utility to create the initial devices based on
    36 all the information in <filename class="directory">/sys</filename>:</para>
     38<para>Now run the installed <command>udevstart</command> program to
     39create the initial devices based on all the information in <filename
     40class="directory">/sys</filename>:</para>
    3741
    3842<screen><userinput>/tools/sbin/udevstart</userinput></screen>
    3943
    40 <para>There are some symlinks and directories required by LFS that are not created by
    41 Udev, so we create those ourselves here:</para>
     44<para>There are some symlinks and directories required by LFS that are
     45not created by Udev, so create those here:</para>
    4246
    4347<screen><userinput>ln -s /proc/self/fd /dev/fd
    … …  
    4953mkdir /dev/shm</userinput></screen>
    5054
    51 <para>Finally, mount the proper virtual (kernel) file systems on the directories we just
    52 created:</para>
     55<para>Finally, mount the proper virtual (kernel) file systems on the
     56newly-created directories:</para>
    5357
    5458<screen><userinput>mount -t devpts -o gid=4,mode=620 none /dev/pts
    … …  
    5660</sect2>
    5761
     62</sect1>
    5863
    59 </sect1>
Note: See TracChangeset for help on using the changeset viewer.