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
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/mips64el
xry111/pip3
xry111/rust-wip-20221008
xry111/update-glibc
| Line | |
|---|
| 1 | <sect1 id="ch05-installasroot">
|
|---|
| 2 | <title>Install all software as user root</title>
|
|---|
| 3 |
|
|---|
| 4 | <para>
|
|---|
| 5 | It's best if the user logs in as root or su's to root when installing these
|
|---|
| 6 | files. That way he is assured that all files are owned by user and
|
|---|
| 7 | group root (and not owned by the userid of the non-root user), and if a
|
|---|
| 8 | package wants to set special permissions, it can do so without problems
|
|---|
| 9 | due to non-root access.
|
|---|
| 10 | </para>
|
|---|
| 11 |
|
|---|
| 12 | <para>
|
|---|
| 13 | The documentation that comes with Glibc, Gcc, and other
|
|---|
| 14 | packages recommend not to compile the packages as user root. We
|
|---|
| 15 | feel it's safe to ignore that recommendation and compile as user root
|
|---|
| 16 | anyway. Hundreds of people using LFS have done so without any problems
|
|---|
| 17 | whatsoever, and we haven't encountered any bugs in the compile processes
|
|---|
| 18 | that cause harm. So it's pretty safe (never can be 100% safe though, so
|
|---|
| 19 | it's up to the user what he ends up doing).
|
|---|
| 20 | </para>
|
|---|
| 21 |
|
|---|
| 22 | </sect1>
|
|---|
| 23 |
|
|---|
Note:
See
TracBrowser
for help on using the repository browser.
