Ignore:
Timestamp:
07/30/2005 06:14:25 PM (19 years ago)
Author:
Tushar Teredesai <tushar@…>
Branches:
10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.1, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
Children:
bfb7882
Parents:
a05dbe6
Message:

Fix some typos

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@4840 af4574ff-66df-0310-9fd7-8a98e5e911e0

Location:
introduction/important
Files:
3 edited

Legend:

Unmodified
Added
Removed
  • introduction/important/bootscripts.xml

    ra05dbe6 r919683dc  
    2626  <para>The BLFS Bootscripts package contains the init
    2727  scripts that are used throughout the book. It is assumed that you will be
    28   using the BLFS Bootscripts package in conjuction with a compatible
     28  using the BLFS Bootscripts package in conjunction with a compatible
    2929  LFS-Bootscripts package. Refer to
    3030  <ulink url="&lfs-root;/chapter07/bootscripts.html"/> for more
     
    4040  <para>The BLFS Bootscripts package will be used throughout the BLFS book
    4141  for startup scripts.  Unlike LFS, each init script has a separate install target
    42   in the BLFS Bootscripts package. It is recomended you keep the package source
     42  in the BLFS Bootscripts package. It is recommended you keep the package source
    4343  directory around until completion of your BLFS system. When a script is
    4444  requested from BLFS Bootscripts, simply change to the directory and as the
     
    4646  <command>make install-<replaceable>[init-script]</replaceable></command>
    4747  command. This command installs the init script to its proper location (along
    48   with any auxillary configuration scripts) and also creates the appropriate
     48  with any auxiliary configuration scripts) and also creates the appropriate
    4949  symlinks to start and stop the service at the appropriate run-level.</para>
    5050
  • introduction/important/pkgmgt.xml

    ra05dbe6 r919683dc  
    3636    <listitem>
    3737      <para>There are multiple solutions for package management, each having
    38       its strengths and drawbacks. Including one that satifies all audiences is
     38      its strengths and drawbacks. Including one that satisfies all audiences is
    3939      difficult.</para>
    4040    </listitem>
     
    5858        (<application>Glibc</application>, <application>GCC</application> or
    5959        <application>Binutils</application>) needs to be upgraded to a newer
    60         minor vesion, it is safer to rebuild LFS. Though you
     60        minor version, it is safer to rebuild LFS. Though you
    6161        <emphasis>may</emphasis> be able to get by rebuilding all the packages
    6262        in their dependency order, we do not recommend it. For example, if
     
    200200      <command>install</command>, <command>mv</command> and tracking the system
    201201      calls that modify the filesystem. For this approach to work, all the executables
    202       need to be dymanically linked without the suid or sgid bit. Preloading the
     202      need to be dynamically linked without the suid or sgid bit. Preloading the
    203203      library may cause some unwanted side-effects during installation. Therefore,
    204204      do perform some tests to ensure that the package manager does not break
  • introduction/important/unpacking.xml

    ra05dbe6 r919683dc  
    4242
    4343    <para>The golden rule of Unix System Administration is to use your
    44     superpowers only when neccessary. Hence, BLFS recommends that you
     44    superpowers only when necessary. Hence, BLFS recommends that you
    4545    build software as an unprivileged user and only become the
    4646    <systemitem class='username'>root</systemitem> user when installing the
Note: See TracChangeset for help on using the changeset viewer.