Changeset 148bb04 for chapter06/changingowner.xml

Timestamp:

09/02/2003 10:03:51 PM (21 years ago)

Author:

Alex Gronenwoud <alex@…>

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.0, 6.1, 6.1.1, 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, v5_0, v5_1, v5_1_1, 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:

cd8e54e

Parents:

40add94

Message:

Renaming /stage1 to /tools.

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

File:

• chapter06/changingowner.xml (modified) (2 diffs)

chapter06/changingowner.xml

@@ -3 +3 @@
 <?dbhtml filename="changingowner.html" dir="chapter06"?>
 
-<para>Right now the <filename class="directory">/stage1</filename> directory
+<para>Right now the <filename class="directory">/tools</filename> directory
 is owned by the user <emphasis>lfs</emphasis>, a user that exists only on your
 host system. Although you will probably want to delete the
-<filename class="directory">/stage1</filename> directory once you have
+<filename class="directory">/tools</filename> directory once you have
 finished your LFS system, you may want to keep it around, for example to
 build more LFS systems. But if you keep the
-<filename class="directory">/stage1</filename> directory as it is, you end up
+<filename class="directory">/tools</filename> directory as it is, you end up
 with files owned by a user ID without a corresponding account. This is
 dangerous because a user account created later on could get this same user ID
-and would suddenly own the <filename class="directory">/stage1</filename>
+and would suddenly own the <filename class="directory">/tools</filename>
 directory and all the files therein, thus exposing these files to possible
 malicious manipulation.</para>
@@ -20 +20 @@
 file, taking care to assign it the same user and group IDs as on your host
 system. Alternatively, you can (and the book assumes you do) assign the
-contents of the <filename class="directory">/stage1</filename> directory to
+contents of the <filename class="directory">/tools</filename> directory to
 user <emphasis>root</emphasis> by running the following command:</para>
 
-<para><screen><userinput>chown -R 0:0 /stage1</userinput></screen></para>
+<para><screen><userinput>chown -R 0:0 /tools</userinput></screen></para>
 
 <para>The command uses "0:0" instead of "root:root", because chown is unable