Changeset 607c7370


Ignore:
Timestamp:
04/14/2001 01:29:56 AM (23 years ago)
Author:
Gerard Beekmans <gerard@…>
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, 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
Children:
3dc72c19
Parents:
a4142a8
Message:

Grammar updates

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

Files:
3 edited

Legend:

Unmodified
Added
Removed
  • chapter05/installasroot.xml

    ra4142a8 r607c7370  
    33
    44<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
     5It's best to log in as root or su's to root when installing the
     6packages. That way you are assured that all files are owned by user and
    77group root (and not owned by the userid of the non-root user), and if a
    88package wants to set special permissions, it can do so without problems
     
    1717whatsoever, and we haven't encountered any bugs in the compile processes
    1818that 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).
     19it's up to you what you ends up doing).
    2020</para>
    2121
  • chapter05/introduction.xml

    ra4142a8 r607c7370  
    44<para>
    55In the following chapters we will install all the software that belongs to
    6 a basic Linux system. After a user is done with this chapter he has a
    7 fully working Linux system. The remaining chapters deal with setting up
    8 networking, creating the boot scripts and adding an entry to lilo.conf so
    9 that the LFS system can be booted.
     6a basic Linux system. After you're done with this and the next chapter,
     7you'll have a fully working Linux system. The remaining chapters deal
     8with creating the boot scripts, making the LFS system bootable and
     9setting up basic networking.
    1010</para>
    1111
     
    2828
    2929<para>
    30 We're about to start with installing the first set of packages. These
    31 packages will be, as previously explained, linked statically.
     30During the installation of various packages, you will more than likely see
     31all kinds of compiler warnings scrolling by on the screen. These are
     32normal and can be safely ignored. They are just that, warnings (mostly
     33about improper use of the C or C++ syntax, but not illegal use. It's just
     34that, often, C standards changed and packages still use the old standard
     35which is not a problem).
    3236</para>
    3337
    3438<para>
    35 During the installation of various packages, the user will most likely see
    36 compiler warnings scrolling by on the screen. These are normal and can
    37 be safely ignored. They are just that, warnings (mostly about improper
    38 use of the C or C++ syntax, but not illegal use. It's just that, often, C
    39 standards changed and packages still use the old standard which is not a
    40 problem).
    41 </para>
    42 
    43 <para>
    44 Before we start, it should be made sure the LFS environment variable was
    45 setup
    46 if it was planned to be used, by running the following command:
     39Before we start, make sure the LFS environment variable is setup
     40properly if you decided to make use of it. Run the following:
    4741</para>
    4842
     
    5347</literallayout></blockquote>
    5448
     49<para>
     50Check to make sure the output contains the correct directory to the LFS
     51partition's mount point (/mnt/lfs for example).
     52</para>
     53
    5554</sect1>
    5655
  • chapter06/chroot.xml

    ra4142a8 r607c7370  
    88
    99<para>
    10 Enter the following command to enter the chroot'ed environment. From
     10Enter the following commands to enter the chroot'ed environment. From
    1111this point on there's no need to use the $LFS variable anymore, because
    1212everything a user does will be restricted to the LFS partition (since / is
     
    3333install all the basic system software. You have to make sure all the
    3434following commands in this and following chapters are run from within the
    35 chroot'ed environment. If you ever leave this environment for a reason
    36 (say when rebooting or something) please remember to mount $LFS/proc
    37 again like you just did and re-enter chroot before continuing with the
     35chroot'ed environment. If you ever leave this environment for any reason
     36(when rebooting for example) please remember to mount $LFS/proc
     37again and re-enter chroot before continuing with the
    3838book.
    3939</para>
    4040
    4141<para>
    42 Note that the bash prompt will contain "I have no name!". This is
     42Note that the bash prompt will contain "I have no name!" This is
    4343normal because Glibc hasn't been installed yet.
    4444</para>
Note: See TracChangeset for help on using the changeset viewer.