Changeset 387a32af for chapter07/changingowner.xml
- Timestamp:
- 06/11/2020 03:13:43 AM (4 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, 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:
- aefc822
- Parents:
- bc8cca5
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter07/changingowner.xml
rbc8cca5 r387a32af 29 29 these files to possible malicious manipulation.</para> 30 30 31 <para>To avoid this issue, you could add the <systemitem 32 class="username">lfs</systemitem> user to the new LFS system later when 33 creating the <filename>/etc/passwd</filename> file, taking care to assign it 34 the same user and group IDs as on the host system. Better yet, change the 31 <para>To address this issue, change the 35 32 ownership of the <filename class="directory">$LFS/*</filename> directories to 36 33 user <systemitem class="username">root</systemitem> by running the following
Note:
See TracChangeset
for help on using the changeset viewer.