Ignore:
Timestamp:
06/16/2005 04:47:40 PM (19 years ago)
Author:
Archaic <archaic@…>
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:
2a88671
Parents:
9c80e02
Message:

Several minor grammatical fixes. Thanks to Randy and Steve.

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

File:
1 edited

Legend:

Unmodified
Added
Removed

  • chapter06/devices.xml

    r9c80e02 rbc2136e  
    2525<title>Mounting ramfs and Populating /dev</title>
    2626
    27 <para>The ideal way to populate <filename
    28 class="directory">/dev</filename> is to mount a <systemitem
    29 class="filesystem">ramfs</systemitem> onto <filename
    30 class="directory">/dev</filename>, like <systemitem
    31 class="filesystem">tmpfs</systemitem>, and create the devices on there
    32 during each bootup. Since the system has not been booted, it is
    33 necessary to do what the bootscripts would otherwise do and populate
    34 <filename class="directory">/dev</filename>. Begin by mounting
    35 <filename class="directory">/dev</filename>:</para>
     27<para>The recommended method of populating the <filename
     28class="directory">/dev</filename> directory with devices is to mount a virtual
     29filesystem (such as <systemitem class="filesystem">ramfs</systemitem> or
     30<systemitem class="filesystem">tmpfs</systemitem>) on the <filename
     31class="directory">/dev</filename> directory, and allow the devices to be created
     32dynamically on that virtual filesystem as they are detected or accessed. This is
     33generally done during the boot process. Since this new system has not been
     34booted, it is necessary to do what the bootscripts would otherwise do by
     35mounting <filename class="directory">/dev</filename>:</para>
    3636
    3737<screen><userinput>mount -n -t ramfs none /dev</userinput></screen>
    3838
    39 <!-- Edit Me -->
    40 <para>Since the Udev package will not be installed until later on in the
    41 process, create a minimal set of device nodes used for building:</para>
     39<para>The Udev package is what actually creates the devices in the <filename
     40class="directory">/dev</filename> directory. Since it will not be installed
     41until later on in the process, manually create the minimal set of device nodes
     42needed to complete the building of this system:</para>
    4243
    4344<screen><userinput>mknod -m 622 /dev/console c 5 1
Note: See TracChangeset for help on using the changeset viewer.