source: chapter06/changingowner.xml@ 27d9bc1a

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
Last change on this file since 27d9bc1a was 21ba4e3, checked in by Greg Schafer <greg@…>, 21 years ago

Internal markup reworking to fix the extraneous whitespace problem in the "tidy generated" web site pages. Essentially replace all ocurrences of <para><screen> with <screen> (and of course the matching closing tags).

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

  • Property mode set to 100644
File size: 1.6 KB
RevLine 
[062461b]1<sect1 id="ch06-changingowner">
[a2cd10f]2<title>Changing ownership</title>
[062461b]3<?dbhtml filename="changingowner.html" dir="chapter06"?>
4
[148bb04]5<para>Right now the <filename class="directory">/tools</filename> directory
[b74e415]6is owned by the user <emphasis>lfs</emphasis>, a user that exists only on your
7host system. Although you will probably want to delete the
[148bb04]8<filename class="directory">/tools</filename> directory once you have
[b74e415]9finished your LFS system, you may want to keep it around, for example to
10build more LFS systems. But if you keep the
[148bb04]11<filename class="directory">/tools</filename> directory as it is, you end up
[b74e415]12with files owned by a user ID without a corresponding account. This is
13dangerous because a user account created later on could get this same user ID
[148bb04]14and would suddenly own the <filename class="directory">/tools</filename>
[b74e415]15directory and all the files therein, thus exposing these files to possible
16malicious manipulation.</para>
[062461b]17
[b74e415]18<para>To avoid this issue, you could add the <emphasis>lfs</emphasis> user to
19your new LFS system later on when creating the <filename>/etc/passwd</filename>
20file, taking care to assign it the same user and group IDs as on your host
21system. Alternatively, you can (and the book assumes you do) assign the
[148bb04]22contents of the <filename class="directory">/tools</filename> directory to
[b74e415]23user <emphasis>root</emphasis> by running the following command:</para>
[062461b]24
[21ba4e3]25<screen><userinput>chown -R 0:0 /tools</userinput></screen>
[44c2fd8]26
[d066924]27<para>The command uses "0:0" instead of "root:root", because chown is unable
[c94dd38]28to resolve the name "root" until the password file has been created.</para>
[062461b]29
30</sect1>
31
Note: See TracBrowser for help on using the repository browser.