Changeset 040521bc for BOOK/chroot/common

Timestamp:

Sep 22, 2006, 8:30:38 PM (18 years ago)

Author:

Jim Gifford <clfs@…>

Branches:

clfs-1.2, clfs-2.1, clfs-3.0.0-systemd, clfs-3.0.0-sysvinit, master, systemd, sysvinit

Children:

8953f24

Parents:

5921622

Message:

Sync up with 1.0 Book

Location:

BOOK/chroot/common

Files:

• chroot.xml (modified) (3 diffs)
• kernfs.xml (modified) (4 diffs)

BOOK/chroot/common/chroot.xml

@@ -17 +17 @@
   temporary tools:</para>
 
-<screen><userinput>chroot "$CLFS" /tools/bin/env -i \
-    HOME=/root TERM="$TERM" PS1='\u:\w\$ ' \
+<screen><userinput>chroot "${CLFS}" /tools/bin/env -i \
+    HOME=/root TERM="${TERM}" PS1='\u:\w\$ ' \
     PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \
     /tools/bin/bash --login +h</userinput></screen>
@@ -27 +27 @@
   <envar>TERM</envar>, <envar>PS1</envar>, and
   <envar>PATH</envar> variables are set again. The
-  <parameter>TERM=$TERM</parameter> construct will set the
+  <parameter>TERM=${TERM}</parameter> construct will set the
   <envar>TERM</envar> variable inside chroot to the same value as
   outside chroot. This variable is needed for programs like
@@ -38 +38 @@
   <envar>CLFS</envar> variable anymore, because all work will be
   restricted to the CLFS file system.  This is because the Bash shell is
-  told that <filename class="directory">$CLFS</filename> is now the root
+  told that <filename class="directory">${CLFS}</filename> is now the root
   (<filename class="directory">/</filename>) directory.</para>
 

BOOK/chroot/common/kernfs.xml

@@ -23 +23 @@
   be mounted:</para>
 
-<screen><userinput>mkdir -pv $CLFS/{dev,proc,sys}</userinput></screen>
+<screen><userinput>mkdir -pv ${CLFS}/{dev,proc,sys}</userinput></screen>
 
   <para>Now mount the file systems:</para>
 
-<screen><userinput>mount -vt proc proc $CLFS/proc
-mount -vt sysfs sysfs $CLFS/sys</userinput></screen>
+<screen><userinput>mount -vt proc proc ${CLFS}/proc
+mount -vt sysfs sysfs ${CLFS}/sys</userinput></screen>
 
   <para>Remember that if for any reason you stop working on the CLFS system
@@ -38 +38 @@
   starting Udev early in the boot process, so we create them here:</para>
 
-<screen><userinput>mknod -m 600 $CLFS/dev/console c 5 1
-mknod -m 666 $CLFS/dev/null c 1 3</userinput></screen>
+<screen><userinput>mknod -m 600 ${CLFS}/dev/console c 5 1
+mknod -m 666 ${CLFS}/dev/null c 1 3</userinput></screen>
 
   <para>Once the system is complete and booting, the rest of our device
@@ -48 +48 @@
   appear in the new CLFS filesystem:</para>
 
-<screen><userinput>mount -v -o bind /dev $CLFS/dev</userinput></screen>
+<screen><userinput>mount -v -o bind /dev ${CLFS}/dev</userinput></screen>
 
   <para>Additional file systems will soon be mounted from within the chroot 
@@ -54 +54 @@
   for each of these now:</para>
 
-<screen><userinput>mount -f -vt tmpfs tmpfs $CLFS/dev/shm
-mount -f -vt devpts -o gid=4,mode=620 devpts $CLFS/dev/pts</userinput></screen>
+<screen><userinput>mount -f -vt tmpfs tmpfs ${CLFS}/dev/shm
+mount -f -vt devpts -o gid=4,mode=620 devpts ${CLFS}/dev/pts</userinput></screen>
 
 </sect1>