Ignore:
Timestamp:
07/22/2001 07:45:10 PM (23 years ago)
Author:
Mark Hymers <markh@…>
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:
f1da843
Parents:
46f5461
Message:

XML changes

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter05/installasroot.xml

    r46f5461 rb822811  
    22<title>Install all software as user root</title>
    33
    4 <para>
    5 It's best to log in as root or su's to root when installing the
     4<para>It's best to log in as root or su's to root when installing the
    65packages. That way you are assured that all files are owned by user and
    76group root (and not owned by the userid of the non-root user), and if a
    87package wants to set special permissions, it can do so without problems
    9 due to non-root access.
    10 </para>
     8due to non-root access.</para>
    119
    12 <para>
    13 The documentation that comes with Glibc, Gcc, and other
     10<para>The documentation that comes with Glibc, Gcc, and other
    1411packages recommend not to compile the packages as user root. We
    1512feel it's safe to ignore that recommendation and compile as user root
     
    1714whatsoever, and we haven't encountered any bugs in the compile processes
    1815that cause harm. So it's pretty safe (never can be 100% safe though, so
    19 it's up to you what you end up doing).
    20 </para>
     16it's up to you what you end up doing).</para>
    2117
    2218</sect1>
Note: See TracChangeset for help on using the changeset viewer.