- Timestamp:
- 04/23/2006 09:00:37 AM (18 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.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:
- b179883
- Parents:
- 830492e
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter05/changingowner.xml
r830492e r07e8db2 19 19 </note> 20 20 21 <para>Currently, the <filename class="directory"> /tools</filename> directory21 <para>Currently, the <filename class="directory">$LFS/tools</filename> directory 22 22 is owned by the user <systemitem class="username">lfs</systemitem>, a user 23 23 that exists only on the host system. If the <filename 24 class="directory"> /tools</filename> directory is kept as is, the files are24 class="directory">$LFS/tools</filename> directory is kept as is, the files are 25 25 owned by a user ID without a corresponding account. This is dangerous because 26 26 a user account created later could get this same user ID and would own the 27 <filename class="directory"> /tools</filename> directory and all the files27 <filename class="directory">$LFS/tools</filename> directory and all the files 28 28 therein, thus exposing these files to possible malicious manipulation.</para> 29 29 … … 32 32 creating the <filename>/etc/passwd</filename> file, taking care to assign it 33 33 the same user and group IDs as on the host system. Better yet, change the 34 ownership of the <filename class="directory"> /tools</filename> directory to34 ownership of the <filename class="directory">$LFS/tools</filename> directory to 35 35 user <systemitem class="username">root</systemitem> by running the following 36 36 command:</para> 37 37 38 <screen><userinput>chown -R root:root /tools</userinput></screen>38 <screen><userinput>chown -R root:root $LFS/tools</userinput></screen> 39 39 40 <para>Although the <filename class="directory"> /tools</filename> directory can41 be deleted once the LFS system has been finished, it can be retained to build40 <para>Although the <filename class="directory">$LFS/tools</filename> directory 41 can be deleted once the LFS system has been finished, it can be retained to build 42 42 additional LFS systems <emphasis>of the same book version</emphasis>. How best 43 to backup <filename class="directory"> /tools</filename> is a matter of43 to backup <filename class="directory">$LFS/tools</filename> is a matter of 44 44 personal preference and is left as an exercise for the reader.</para> 45 45
Note:
See TracChangeset
for help on using the changeset viewer.