Changeset 0708c2a


Ignore:
Timestamp:
01/19/2005 10:38:21 PM (19 years ago)
Author:
Randy McMurchy <randy@…>
Branches:
10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.0, 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:
3809022
Parents:
9cf73e3
Message:

Added indexing tags to blfs-bootscripts instructions; misc. tagging and grammar corrections

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

Location:
introduction/important
Files:
3 edited

Legend:

Unmodified
Added
Removed

  • introduction/important/beyond.xml

    r9cf73e3 r0708c2a  
    2121
    2222<para>When you want to install a package to a location other than
    23 <filename class='directory'>/</filename>, or <filename class='directory'>/usr</filename>, you are installing
     23<filename class='directory'>/</filename>, or
     24<filename class='directory'>/usr</filename>, you are installing
    2425outside the default environment settings on most machines.  The following
    2526examples should assist you in determining how to correct this situation.
    … …  
    3031<listitem><para>Expand the <envar>PATH</envar> to include
    3132<filename class='directory'>$PREFIX/bin</filename>.</para></listitem>
     33
    3234<listitem><para>Expand the <envar>PATH</envar> for root to include
    3335<filename class='directory'>$PREFIX/sbin</filename>.</para></listitem>
     36
    3437<listitem><para>Add <filename class='directory'>$PREFIX/lib</filename>
    3538to <filename>/etc/ld.so.conf</filename> or expand
    3639<envar>LD_LIBRARY_PATH</envar> to include it. Before using the latter option,
    3740check out <ulink url="http://www.visi.com/~barr/ldpath.html"/>. If you
    38 modify <filename>/etc/ld.so.conf</filename> remember to update
    39 <filename>/etc/ld.so.cache</filename> by executing <command>ldconfig</command>.</para></listitem>
     41modify <filename>/etc/ld.so.conf</filename>, remember to update
     42<filename>/etc/ld.so.cache</filename> by executing <command>ldconfig</command>
     43as the root user.</para></listitem>
     44
    4045<listitem><para>Add <filename class='directory'>$PREFIX/man</filename>
    41 to <filename>/etc/man.conf</filename> or expand <envar>MANPATH</envar>.</para></listitem>
     46to <filename>/etc/man.conf</filename> or expand <envar>MANPATH</envar>.</para>
     47</listitem>
     48
    4249<listitem><para>Add <filename class='directory'>$PREFIX/info</filename>
    4350to <envar>INFOPATH</envar>.</para></listitem>
     51
    4452<listitem><para>Add <filename
    4553class='directory'>$PREFIX/lib/pkgconfig</filename> to
    4654<envar>PKG_CONFIG_PATH</envar>.</para></listitem>
     55
    4756<listitem><para>Add <filename
    48 class='directory'>$PREFIX/include</filename> to <envar>CPPFLAGS</envar> when compiling packages
    49 that depend on the package you installed.</para></listitem>
     57class='directory'>$PREFIX/include</filename> to <envar>CPPFLAGS</envar> when
     58compiling packages that depend on the package you installed.</para></listitem>
    5059</itemizedlist>
    5160
    … …  
    5665
    5766<listitem><para>If you know the name of the package, then search FreshMeat for
    58 at <ulink url="http://freshmeat.net/"/>. Also search Google at
     67it at <ulink url="http://freshmeat.net/"/>. Also search Google at
    5968<ulink url="http://google.com/"/>. Sometimes a search for the rpm at
    6069<ulink url="http://rpmfind.net/"/> or the deb at
    6170<ulink url="http://www.debian.org/distrib/packages#search_packages"/> can also
    62 lead to the website for the package.</para></listitem>
     71lead to a link to the package.</para></listitem>
    6372
    6473<listitem><para>If you know the name of the executable, but not the package
    … …  
    8796<listitem><para>If you are having a problem compiling the package, try
    8897searching the lfs archives at <ulink url="http://search.linuxfromscratch.org/"/>
    89 for the error or if that fails try searching google. If everything else fails,
     98for the error or if that fails try searching Google. If everything else fails,
    9099try the blfs support mailing-list/news-server.</para></listitem>
    91100
    … …  
    93102
    94103<tip><para>If you have found a package that is only available in .deb or .rpm
    95 format, there are two small scripts rpm2targz and deb2targz that are available
    96 at <ulink url="&downloads-project;/deb2targz.tar.bz2"/> and <ulink
    97 url="&downloads-project;/rpm2targz.tar.bz2"/> to convert the archives into a
    98 simple tar.gz format.</para></tip>
     104format, there are two small scripts, <command>rpm2targz</command> and
     105<command>deb2targz</command> that are available at
     106<ulink url="&downloads-project;/deb2targz.tar.bz2"/> and
     107<ulink url="&downloads-project;/rpm2targz.tar.bz2"/> to convert the archives
     108into a simple <filename>tar.gz</filename> format.</para></tip>
    99109
    100110</sect1>

  • introduction/important/bootscripts.xml

    r9cf73e3 r0708c2a  
    1313<?dbhtml filename="bootscripts.html"?>
    1414<title><acronym>BLFS</acronym> Boot Scripts</title>
     15<indexterm zone="intro-important-bootscripts">
     16<primary sortas="a-BLFS-Bootscripts">BLFS Bootscripts</primary></indexterm>
     17<indexterm zone="intro-important-bootscripts">
     18<primary sortas="f-AA-General-Information">General Information</primary>
     19</indexterm>
    1520
    16 <para>The <acronym>BLFS</acronym> Bootscripts package contains the init scripts that are
    17 used throughout the book. It is assumed that you will be using the blfs-bootscripts
    18 package in conjuction with a compatible lfs-bootscripts package.
    19 Refer to
    20 <ulink url="&lfs-root;/chapter07/bootscripts.html"/>
    21 for more
     21<para>The <acronym>BLFS</acronym> Bootscripts package contains the init
     22scripts that are used throughout the book. It is assumed that you will be
     23using the blfs-bootscripts package in conjuction with a compatible
     24lfs-bootscripts package. Refer to
     25<ulink url="&lfs-root;/chapter07/bootscripts.html"/> for more
    2226information on the lfs-bootscripts package.</para>
    23 
    2427
    2528<itemizedlist spacing='compact'>
    2629<title>Package information</title>
    27 <listitem><para>Download: <ulink url="&blfs-bootscripts-download;"/></para></listitem>
     30<listitem><para>Download: <ulink url="&blfs-bootscripts-download;"/></para>
     31</listitem>
    2832</itemizedlist>
    2933
    30 
    31 <para>The blfs-bootscripts package will be used throughout the <acronym>BLFS</acronym>
    32 book for startup scripts.  Unlike <acronym>LFS</acronym>, each init script
    33 has a separate install target in the blfs-bootscripts package.
    34 It is recomended you keep the package
    35 source directory around until completion of your
    36 <acronym>BLFS</acronym> system.  When a script is requested from
    37 blfs-bootscripts, simply change to the directory and execute the given
    38 <command>make install-&lt;init-script&gt;</command> command. This command installs the
    39 init script to its proper location (along with any auxillary configuration
    40 scripts) and also creates the appropriate symlinks to start and stop the
    41 service at the appropriate run-level.</para>
     34<para>The blfs-bootscripts package will be used throughout the
     35<acronym>BLFS</acronym> book for startup scripts.  Unlike
     36<acronym>LFS</acronym>, each init script has a separate install target in the
     37blfs-bootscripts package. It is recomended you keep the package source
     38directory around until completion of your <acronym>BLFS</acronym> system. When
     39a script is requested from blfs-bootscripts, simply change to the directory
     40and execute the given
     41<command>make install-<replaceable>[init-script]</replaceable></command>
     42command. This command installs the init script to its proper location (along
     43with any auxillary configuration scripts) and also creates the appropriate
     44symlinks to start and stop the service at the appropriate run-level.</para>
    4245
    4346<note><para>It is advisable to peruse each bootscript before installation to

  • introduction/important/patches.xml

    r9cf73e3 r0708c2a  
    2525</itemizedlist>
    2626
    27 <para>In short, the book only includes patches that are either required or
    28 recommended. There is a <ulink url="http://www.linuxfromscratch.org/patches">Patches subproject</ulink>
    29 which hosts various patches (including the patches referenced in the books)
    30 to enable you to configure your <acronym>LFS</acronym> the way you like it.</para>
     27<para>In short, the book only includes patches that are either required or
     28recommended. There is a
     29<ulink url="http://www.linuxfromscratch.org/patches">Patches subproject</ulink>
     30which hosts various patches (including the patches referenced in the books)
     31to enable you to configure your <acronym>LFS</acronym> the way you like
     32it.</para>
    3133
    3234</sect1>
Note: See TracChangeset for help on using the changeset viewer.