Changeset 3f0c882 for chapter06/changingowner.xml
- Timestamp:
- 12/21/2004 07:38:32 PM (20 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.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, 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:
- 3d36131c
- Parents:
- aaa3260
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter06/changingowner.xml
raaa3260 r3f0c882 8 8 <?dbhtml filename="changingowner.html"?> 9 9 10 <para>Right now the <filename class="directory">/tools</filename> directory 11 is owned by the user <emphasis>lfs</emphasis>, a user that exists only on your 12 host system. Although you will probably want to delete the 13 <filename class="directory">/tools</filename> directory once you have 14 finished your LFS system, you may want to keep it around, for example to 15 build more LFS systems. But if you keep the 16 <filename class="directory">/tools</filename> directory as it is, you end up 17 with files owned by a user ID without a corresponding account. This is 18 dangerous because a user account created later on could get this same user ID 19 and would suddenly own the <filename class="directory">/tools</filename> 20 directory and all the files therein, thus exposing these files to possible 21 malicious manipulation.</para> 22 23 <para>To avoid this issue, you could add the <emphasis>lfs</emphasis> user to 24 your new LFS system later on when creating the <filename>/etc/passwd</filename> 25 file, taking care to assign it the same user and group IDs as on your host 26 system. Alternatively, you can (and the book assumes you do) assign the 27 contents of the <filename class="directory">/tools</filename> directory to 28 user <emphasis>root</emphasis> by running the following command:</para> 10 <para>Change the owner of <filename class="directory">/tools</filename>:</para> 29 11 30 12 <screen><userinput>chown -R 0:0 /tools</userinput></screen> 31 13 32 <para>The command uses <parameter>0:0</parameter> instead of <parameter>root:root</parameter>,33 because <userinput>chown</userinput> is unable to resolve the name34 <quote>root</quote> until the password file has been created.</para>35 36 14 </sect1>
Note:
See TracChangeset
for help on using the changeset viewer.