aboutsummaryrefslogtreecommitdiffstats
path: root/chapter05/installasroot.xml
diff options
context:
space:
mode:
authorSimon Perreault <nomis80@videotron.ca>2001-03-25 08:46:07 +0000
committerSimon Perreault <nomis80@videotron.ca>2001-03-25 08:46:07 +0000
commit13dd793404cca56ba1dc8c1d60bce8128753ea47 (patch)
treeadbcd0d565b9fb21c59a2fa93a84a2946fd740f4 /chapter05/installasroot.xml
parentc85f9761b07ded83b473fe1b99b2141e91b658b1 (diff)
Grammar fixes.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@364 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter05/installasroot.xml')
-rw-r--r--chapter05/installasroot.xml14
1 files changed, 7 insertions, 7 deletions
diff --git a/chapter05/installasroot.xml b/chapter05/installasroot.xml
index d8207f440..4e787875f 100644
--- a/chapter05/installasroot.xml
+++ b/chapter05/installasroot.xml
@@ -2,19 +2,19 @@
<title>Install all software as user root</title>
<para>
-It's best if the user logins as root or su's to root when installing these
-files. That way he is assured that all files are owned by user root,
-group root (and not owned by the userid of the non-root user) and if a
-package wants to set special permissions it can do so without problems
+It's best if the user logs in as root or su's to root when installing these
+files. That way he is assured that all files are owned by user and
+group root (and not owned by the userid of the non-root user), and if a
+package wants to set special permissions, it can do so without problems
due to non-root access.
</para>
<para>
-The documentation that comes with Glibc, Gcc and other
+The documentation that comes with Glibc, Gcc, and other
packages recommend not to compile the packages as user root. We
feel it's safe to ignore that recommendation and compile as user root
-anyways. Hundreds of people using LFS have done so without any problems
-whatsoever and we haven't encountered any bugs in the compile processes
+anyway. Hundreds of people using LFS have done so without any problems
+whatsoever, and we haven't encountered any bugs in the compile processes
that cause harm. So it's pretty safe (never can be 100% safe though, so
it's up to the user what he ends up doing).
</para>