Changeset 72033583 for chapter05/installasroot.xml
- Timestamp:
- 03/18/2001 07:30:50 PM (24 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, 12.2, 12.2-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, v3_0, v3_1, v3_2, v3_3, v4_0, v4_1, 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/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- 137bd50
- Parents:
- ab8b352
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter05/installasroot.xml
rab8b352 r72033583 3 3 4 4 <para> 5 It's best if you login as root or suto root when installing these6 files. That way you areassured that all files are owned by user root,7 group root (and not owned by the userid of yournon-root user) and if a5 It's best if the user logins as root or su's to root when installing these 6 files. That way he is assured that all files are owned by user root, 7 group root (and not owned by the userid of the non-root user) and if a 8 8 package wants to set special permissions it can do so without problems 9 9 due to non-root access. … … 11 11 12 12 <para> 13 If you read the documentation that comes with Glibc, Gcc and other14 packages theyrecommend not to compile the packages as user root. We13 The documentation that comes with Glibc, Gcc and other 14 packages recommend not to compile the packages as user root. We 15 15 feel it's safe to ignore that recommendation and compile as user root 16 16 anyways. Hundreds of people using LFS have done so without any problems 17 17 whatsoever and we haven't encountered any bugs in the compile processes 18 18 that cause harm. So it's pretty safe (never can be 100% safe though, so 19 it's up to you what you endup doing).19 it's up to the user what he ends up doing). 20 20 </para> 21 21
Note:
See TracChangeset
for help on using the changeset viewer.