Changeset bf3dcb3f

Timestamp:

Feb 21, 2006, 2:17:51 AM (19 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:

f15e0d6

Parents:

a605458

Message:

r1112@server (orig r1110): chris | 2006-01-30 11:07:11 -0800
Moved note in boot section about running the rest of the book as root to populating LFS/dev since the devices must be created as root.

Location:

BOOK/boot/common

Files:

• changingowner.xml (modified) (2 diffs)
• devices.xml (modified) (1 diff)

BOOK/boot/common/changingowner.xml

@@ -11 +11 @@
   <title>Changing Ownership</title>
 
-  <note os="a">
-    <para>From now on, all commands in the rest of the book will be run as the <systemitem class="username">root</systemitem> user.</para>
-  </note>
-
-  <para os="b">Currently, the <filename class="directory">/tools</filename>
+  <para os="a">Currently, the <filename class="directory">/tools</filename>
   directory, <filename class="directory">/cross-tools</filename> directory, and
   <filename class="directory">$LFS</filename> directory are owned
   by the user <systemitem class="username">lfs</systemitem>,
-  a user that exists only on the host system. For security reasons, the $LFS root directory and all of it subdirectories should be owned by <systemitem class="username">root</systemitem>. Change the ownership for $LFS and its subdirectories by running these commands:</para>
+  a user that exists only on the host system. For security reasons, the
+  $LFS root directory and all of it subdirectories should be owned by
+  <systemitem class="username">root</systemitem>. Change the ownership for $LFS and its subdirectories by running these commands:</para>
 
 <screen><userinput>chown root:root ${LFS}
 chown -R root:root $LFS/{bin,boot,dev,etc,home,lib,media,mnt,opt,proc,root,sbin,srv,sys,tmp,usr,var}</userinput></screen>
 
-  <para os="c">The same issue also exists with <filename class="directory">/tools</filename> and <filename class="directory">/cross-tools</filename>. Although these directories can be deleted once the
+  <para os="b">The same issue also exists with <filename class="directory">/tools</filename> and <filename class="directory">/cross-tools</filename>. Although these directories can be deleted once the
   LFS system has been finished, they can be retained to build additional
   LFS systems. If the <filename class="directory">/tools</filename> and <filename class="directory">/cross-tools</filename>
@@ -33 +31 @@
   thus exposing these files to possible malicious manipulation.</para>
 
-  <para os="d">To avoid this issue, add the <systemitem
+  <para os="c">To avoid this issue, add the <systemitem
   class="username">lfs</systemitem> user to the new LFS system later when
   creating the <filename>/etc/passwd</filename> file, taking care to assign

BOOK/boot/common/devices.xml

@@ -18 +18 @@
     <title>Creating Initial Device Nodes</title>
 
-    <para os="a">When the kernel boots the system, it requires the presence
+    <note os="a">
+      <para>The commands in the remainder of the book should be run as
+      the<systemitem class="username">root</systemitem> user. Also,
+      double-check that $LFS is set as root.</para>
+    </note>
+
+    <para os="b">When the kernel boots the system, it requires the presence
     of a few device nodes, in particular the <filename
     class="devicefile">console</filename> and <filename