Changeset 8446a0b
- Timestamp:
- 06/27/2005 11:17:32 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:
- 06d3024
- Parents:
- 4bcbf29
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter01/changelog.xml
r4bcbf29 r8446a0b 92 92 </listitem> 93 93 94 <listitem><para>June 27th, 2005 [archaic]: Switched from mounting /dev on a 95 ramfs to a tmpfs.</para></listitem> 96 94 97 <listitem><para>June 27th, 2005 [archaic]: Filled in text for errata page. 95 98 Thanks for the text, Steve!</para></listitem> -
chapter06/devices.xml
r4bcbf29 r8446a0b 23 23 24 24 <sect2> 25 <title>Mounting ramfs and Populating /dev</title>25 <title>Mounting tmpfs and Populating /dev</title> 26 26 27 27 <para>The recommended method of populating the <filename 28 28 class="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> 29 filesystem (such as <systemitem class="filesystem">tmpfs</systemitem>) on the 30 <filename class="directory">/dev</filename> directory, and allow the devices to 31 be created dynamically on that virtual filesystem as they are detected or 32 accessed. This is generally done during the boot process. Since this new system 33 has not been booted, it is necessary to do what the bootscripts would otherwise 34 do by mounting <filename class="directory">/dev</filename>:</para> 36 35 37 <screen><userinput>mount -n -t ramfs none /dev</userinput></screen>36 <screen><userinput>mount -n -t tmpfs none /dev</userinput></screen> 38 37 39 38 <para>The Udev package is what actually creates the devices in the <filename … … 52 51 <!-- --> 53 52 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 54 during boot by the bootscripts. Since this is a chroot environment and not a 55 booted environment, those symlinks and directories need to be created 56 here:</para> 56 57 57 58 <screen><userinput>ln -s /proc/self/fd /dev/fd -
chapter06/kernfs.xml
r4bcbf29 r8446a0b 30 30 mount</quote> for each of these now:</para> 31 31 32 <screen><userinput>mount -f -t ramfs ramfs $LFS/dev32 <screen><userinput>mount -f -t tmpfs tmpfs $LFS/dev 33 33 mount -f -t tmpfs tmpfs $LFS/dev/shm 34 34 mount -f -t devpts -o gid=4,mode=620 devpts $LFS/dev/pts</userinput></screen> -
chapter07/udev.xml
r4bcbf29 r8446a0b 28 28 get device nodes created for them. Because these device nodes will be 29 29 created each time the system boots, they will be stored on a 30 <systemitem class="filesystem"> ramfs</systemitem> (a file system that30 <systemitem class="filesystem">tmpfs</systemitem> (a file system that 31 31 resides entirely in memory and does not take up any disk space). 32 32 Device nodes do not require much disk space, so the memory that is
Note:
See TracChangeset
for help on using the changeset viewer.