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

chapter01/changelog.xml

@@ -91,6 +91,9 @@ First a summary, then a detailed log.</para>
 </itemizedlist>
 </listitem>
 
+<listitem><para>June 27th, 2005 [archaic]: Switched from mounting /dev on a
+ramfs to a tmpfs.</para></listitem>
+
 <listitem><para>June 27th, 2005 [archaic]: Filled in text for errata page.
 Thanks for the text, Steve!</para></listitem>
 

chapter06/devices.xml

@@ -22,19 +22,18 @@ mknod -m 666 /dev/null c 1 3</userinput></screen>
 </sect2>
 
 <sect2>
-<title>Mounting ramfs and Populating /dev</title>
+<title>Mounting tmpfs and Populating /dev</title>
 
 <para>The recommended method of populating the <filename
 class="directory">/dev</filename> directory with devices is to mount a virtual
-filesystem (such as <systemitem class="filesystem">ramfs</systemitem> or
-<systemitem class="filesystem">tmpfs</systemitem>) on the <filename
-class="directory">/dev</filename> directory, and allow the devices to be created
-dynamically on that virtual filesystem as they are detected or accessed. This is
-generally done during the boot process. Since this new system has not been
-booted, it is necessary to do what the bootscripts would otherwise do by
-mounting <filename class="directory">/dev</filename>:</para>
+filesystem (such as <systemitem class="filesystem">tmpfs</systemitem>) on the
+<filename class="directory">/dev</filename> directory, and allow the devices to
+be created dynamically on that virtual filesystem as they are detected or
+accessed. This is generally done during the boot process. Since this new system
+has not been booted, it is necessary to do what the bootscripts would otherwise
+do by mounting <filename class="directory">/dev</filename>:</para>
 
-<screen><userinput>mount -n -t ramfs none /dev</userinput></screen>
+<screen><userinput>mount -n -t tmpfs none /dev</userinput></screen>
 
 <para>The Udev package is what actually creates the devices in the <filename
 class="directory">/dev</filename> directory. Since it will not be installed
@@ -51,8 +50,10 @@ mknod -m 444 /dev/urandom c 1 9
 chown root:tty /dev/{console,ptmx,tty}</userinput></screen>
 <!-- -->
 
-<para>There are some symlinks and directories required by LFS that are
-not created by Udev, so create those here:</para>
+<para>There are some symlinks and directories required by LFS that are created
+during boot by the bootscripts. Since this is a chroot environment and not a
+booted environment, those symlinks and directories need to be created
+here:</para>
 
 <screen><userinput>ln -s /proc/self/fd /dev/fd
 ln -s /proc/self/fd/0 /dev/stdin

chapter06/kernfs.xml

@@ -29,7 +29,7 @@ environment.</para>
 chroot environment. To keep the host up to date, perform a <quote>fake
 mount</quote> for each of these now:</para>
 
-<screen><userinput>mount -f -t ramfs ramfs $LFS/dev
+<screen><userinput>mount -f -t tmpfs tmpfs $LFS/dev
 mount -f -t tmpfs tmpfs $LFS/dev/shm
 mount -f -t devpts -o gid=4,mode=620 devpts $LFS/dev/pts</userinput></screen>
 

chapter07/udev.xml

@@ -27,7 +27,7 @@ numbers for every possible device that might exist in the world. Using
 the udev method, only those devices which are detected by the kernel
 get device nodes created for them. Because these device nodes will be
 created each time the system boots, they will be stored on a
-<systemitem class="filesystem">ramfs</systemitem> (a file system that
+<systemitem class="filesystem">tmpfs</systemitem> (a file system that
 resides entirely in memory and does not take up any disk space).
 Device nodes do not require much disk space, so the memory that is
 used is negligible.</para>