Changeset 8446a0b for chapter06


Ignore:
Timestamp:
06/27/2005 11:17:32 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:
06d3024
Parents:
4bcbf29
Message:

Switched from mounting /dev on a ramfs to a tmpfs.

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

Location:
chapter06
Files:
2 edited

Legend:

Unmodified
Added
Removed

  • chapter06/devices.xml

    r4bcbf29 r8446a0b  
    2323
    2424<sect2>
    25 <title>Mounting ramfs and Populating /dev</title>
     25<title>Mounting tmpfs and Populating /dev</title>
    2626
    2727<para>The recommended method of populating the <filename
    2828class="directory">/dev</filename> directory with devices is to mount a virtual
    29 filesystem (such as <systemitem class="filesystem">ramfs</systemitem> or
    30 <systemitem class="filesystem">tmpfs</systemitem>) on the <filename
    31 class="directory">/dev</filename> directory, and allow the devices to be created
    32 dynamically on that virtual filesystem as they are detected or accessed. This is
    33 generally done during the boot process. Since this new system has not been
    34 booted, it is necessary to do what the bootscripts would otherwise do by
    35 mounting <filename class="directory">/dev</filename>:</para>
     29filesystem (such as <systemitem class="filesystem">tmpfs</systemitem>) on the
     30<filename class="directory">/dev</filename> directory, and allow the devices to
     31be created dynamically on that virtual filesystem as they are detected or
     32accessed. This is generally done during the boot process. Since this new system
     33has not been booted, it is necessary to do what the bootscripts would otherwise
     34do by mounting <filename class="directory">/dev</filename>:</para>
    3635
    37 <screen><userinput>mount -n -t ramfs none /dev</userinput></screen>
     36<screen><userinput>mount -n -t tmpfs none /dev</userinput></screen>
    3837
    3938<para>The Udev package is what actually creates the devices in the <filename
    … …  
    5251<!-- -->
    5352
    54 <para>There are some symlinks and directories required by LFS that are
    55 not created by Udev, so create those here:</para>
     53<para>There are some symlinks and directories required by LFS that are created
     54during boot by the bootscripts. Since this is a chroot environment and not a
     55booted environment, those symlinks and directories need to be created
     56here:</para>
    5657
    5758<screen><userinput>ln -s /proc/self/fd /dev/fd

  • chapter06/kernfs.xml

    r4bcbf29 r8446a0b  
    3030mount</quote> for each of these now:</para>
    3131
    32 <screen><userinput>mount -f -t ramfs ramfs $LFS/dev
     32<screen><userinput>mount -f -t tmpfs tmpfs $LFS/dev
    3333mount -f -t tmpfs tmpfs $LFS/dev/shm
    3434mount -f -t devpts -o gid=4,mode=620 devpts $LFS/dev/pts</userinput></screen>
Note: See TracChangeset for help on using the changeset viewer.