Ignore:
Timestamp:
09/12/2003 03:09:56 AM (21 years ago)
Author:
Larry Lawrence <larry@…>
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, v5_0, v5_0-pre1, v5_1, v5_1-pre1, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
Children:
7891efc
Parents:
1aacd4b5
Message:

Part I review with modification to better match LFS

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

Location:
introduction/important
Files:
4 edited

Legend:

Unmodified
Added
Removed

  • introduction/important/beyond.xml

    r1aacd4b5 racfc391  
    11<sect1 id="intro-important-beyond">
    22<?dbhtml filename="beyond.html" dir="introduction"?>
    3 <title>Going Beyond BLFS</title>
     3<title>Going Beyond <acronym>BLFS</acronym></title>
    44
    55<para>The packages that are installed in this book are only the tip of the
    6 iceberg. We hope that the experience you gained with the LFS book and the BLFS
    7 book will give you the background needed to compile, install and configure
    8 packages that are not included in this book.</para>
     6iceberg. We hope that the experience you gained with the <acronym>LFS</acronym>
     7book and the <acronym>BLFS</acronym> book will give you the background needed
     8to compile, install and configure packages that are not included in this book.
     9</para>
    910
    1011<para>If you are in search of a package that is not in the book, the following
    … …  
    2021lead to the website for the package.</para></listitem>
    2122
    22 <listitem><para>If you know the name of the executable, but not the package that
    23 the executable belongs to, first try a google
    24 search with the name of the executable. If the results are overwhelming, try
    25 searching for the given executable in the debian repository at
     23<listitem><para>If you know the name of the executable, but not the package
     24that the executable belongs to, first try a google search with the name of the
     25executable. If the results are overwhelming, try searching for the given
     26executable in the debian repository at
    2627<ulink url="http://www.debian.org/distrib/packages#search_contents"/>.
    2728</para></listitem>
    … …  
    3536<listitem><para>Many of the newer packages follow the <command>./configure
    3637&amp;&amp; make &amp;&amp; make install</command> <emphasis>dance</emphasis>
    37 routine. Help on the
    38 options accepted by configure can be obtained via the command
    39 <command>./configure --help</command>.</para></listitem>
     38routine. Help on the options accepted by configure can be obtained via the
     39command <command>./configure --help</command>.</para></listitem>
    4040
    4141<listitem><para>Most of the packages contain documentation on compiling and
    … …  
    5151</itemizedlist>
    5252
    53 <tip><para>If you have found a package that is only available in .deb or .rpm format,
    54 there are two small scripts rpm2targz and deb2targz that are available at
    55 <ulink url="http://www.linuxfromscratch.org/~tushar/downloads/"/> to convert
     53<tip><para>If you have found a package that is only available in .deb or .rpm
     54format, there are two small scripts rpm2targz and deb2targz that are available
     55at <ulink url="http://www.linuxfromscratch.org/~tushar/downloads/"/> to convert
    5656the archives into a simple tar.gz format.</para></tip>
    5757

  • introduction/important/bootscripts.xml

    r1aacd4b5 racfc391  
    55<para>The scripts included for packages such as <xref linkend="gpm"/>
    66and <xref linkend="alsa"/> are based around the template supplied with
    7 the lfs-bootscripts package from version 3.2 and later of the LFS book.
    8 Note that this is lfs-bootscripts-1.6 and later (the old numbering
    9 changed as of LFS-3.2).  The scripts won't work with versions of LFS
    10 before 3.2 because of a change in their organization with the new
    11 scripts.  However, it should be trivial to adapt the scripts if needed
    12 for older LFS versions.</para>
     7the lfs-bootscripts package from version 3.2 and later of the <acronym>
     8LFS</acronym> book. Note that this is lfs-bootscripts-1.6 and later (the old
     9numbering changed as of LFS-3.2).  The scripts won't work with versions
     10of <acronym>LFS</acronym> before 3.2 because of a change in their organization
     11with the new scripts.  However, it should be trivial to adapt the scripts if
     12needed for older <acronym>LFS</acronym> versions.</para>
    1313
    1414</sect1>

  • introduction/important/position.xml

    r1aacd4b5 racfc391  
    33<title>The /usr versus /usr/local debate</title>
    44
    5 <para><emphasis>Should I install XXX in /usr or
    6 /usr/local?</emphasis></para>
     5<para><emphasis>Should I install XXX in <filename>/usr</filename> or
     6<filename>/usr/local</filename>?</emphasis></para>
    77
    8 <para>This is a question without an obvious answer for an LFS based
    9 system.</para>
     8<para>This is a question without an obvious answer for an
     9<acronym>LFS</acronym> based system.</para>
    1010
    1111<para>In traditional unix systems, <filename>/usr</filename> usually
    12 contains files that come
    13 with the system distribution, and the <filename>/usr/local</filename> tree
    14 is free for the local administrator to add things to.  The only
    15 really hard and fast
    16 rule is that unix distributions should not touch
    17 <filename>/usr/local</filename>, except
    18 perhaps for creating the basic directories within it.</para>
     12contains files that come with the system distribution, and the <filename>
     13/usr/local</filename> tree is free for the local administrator to add things
     14to.  The only really hard and fast rule is that unix distributions should not
     15touch <filename>/usr/local</filename>, except perhaps for creating the basic
     16directories within it.</para>
    1917
    2018<para>With Linux distributions, like Red Hat, Debian etc. a possible rule is
    … …  
    2422<filename>/usr</filename>.</para>
    2523
    26 <para>LFS users build their own system and so deciding where the system ends
    27 and local files begin is not straightforward.  So the choice should be
    28 made in order to make things easier to administer.  There are several
     24<para><acronym>LFS</acronym> users build their own system and so deciding where
     25the system ends and local files begin is not straightforward.  So the choice
     26should be made in order to make things easier to administer.  There are several
    2927reasons for dividing files between <filename>/usr</filename> and
    3028<filename>/usr/local</filename>.</para>
    … …  
    3230<itemizedlist>
    3331
    34 <listitem><para>On a network of several machines all running LFS, or mixed
    35 LFS and
    36 other Linux distributions, <filename>/usr/local</filename> could be used to
    37 hold packages
     32<listitem><para>On a network of several machines all running <acronym>LFS
     33</acronym>, or mixed <acronym>LFS</acronym> and other Linux distributions,
     34<filename>/usr/local</filename> could be used to hold packages
    3835that are common between all the computers in the network.  It can be
    39 NFS mounted or mirrored from a single server.  Here local indicates
    40 local to the site.</para></listitem>
     36<acronym>NFS</acronym> mounted or mirrored from a single server.  Here local
     37indicates local to the site.</para></listitem>
    4138
    4239<listitem><para>On a network of several computers all running an identical
    43 LFS system <filename>/usr/local</filename> could hold packages that
    44 are different between the machines.  In this case local refers to
    45 the individual computers.</para></listitem>
     40<acronym>LFS</acronym> system <filename>/usr/local</filename> could hold
     41packages that are different between the machines.  In this case local refers
     42to the individual computers.</para></listitem>
    4643
    4744<listitem><para>Even on a single computer <filename>/usr/local</filename> can
    4845be useful if you have several distributions installed simultaneously, and want
    49 a place to put packages that will be the same on all of
    50 them.</para></listitem>
     46a place to put packages that will be the same on all of them.</para></listitem>
    5147
    52 <listitem><para>Or you might regularly rebuild your LFS, but want
    53 a place to put files
    54 that you don't want to rebuild each time.  This way you can wipe the
    55 LFS filesystem and start from a clean partition every time without losing
    56 everything.</para></listitem>
     48<listitem><para>Or you might regularly rebuild your <acronym>LFS</acronym>, but
     49want a place to put files that you don't want to rebuild each time.  This way
     50you can wipe the <acronym>LFS</acronym> filesystem and start from a clean
     51partition every time without losing everything.</para></listitem>
    5752
    5853</itemizedlist>
    5954
    60 <para>Some people ask why not use your own directory tree, e.g.
    61 <filename>/usr/site</filename> rather than
    62 <filename>/usr/local</filename>?</para>
     55<para>Some people ask why not use your own directory tree, e.g. <filename>
     56/usr/site</filename> rather than <filename>/usr/local</filename>?</para>
    6357
    64 <para>There is nothing stopping you, many sites do make their own trees, however
    65 it makes installing new software more difficult.  Automatic installers
     58<para>There is nothing stopping you, many sites do make their own trees,
     59however it makes installing new software more difficult.  Automatic installers
    6660often look for dependencies in <filename>/usr</filename> and
    6761<filename>/usr/local</filename>, and if the file it is looking
    6862for is in <filename>/usr/site</filename> instead, the installer will
    69 probably fail unless
    70 you specifically tell it where to look.</para>
     63probably fail unless you specifically tell it where to look.</para>
    7164
    72 <para><emphasis>What is the BLFS position on this?</emphasis></para>
     65<para><emphasis>What is the <acronym>BLFS</acronym> position on this?</emphasis>
     66</para>
    7367
    74 <para>All of the BLFS instructions install programs in
     68<para>All of the <acronym>BLFS</acronym> instructions install programs in
    7569<filename>/usr</filename> unless specifically stated otherwise.  There
    7670are examples where some files are placed in the
    7771<filename>/usr/local</filename> hierarchy but these are documented and
    7872are generally for a good reason. These exceptions should be well documented
    79 in the book.  If you think you have
    80 found one which isn't please tell us!</para>
     73in the book.  If you think you have found one which isn't please tell us!</para>
    8174
    8275</sect1>

  • introduction/important/unpacking.xml

    r1aacd4b5 racfc391  
    33<title>Getting and unpacking the software</title>
    44
    5 <para>Those people who have built a LFS system will be aware of the
    6 general principles of downloading and unpacking software.  We will
     5<para>Those people who have built a <acronym>LFS</acronym> system will be aware
     6of the general principles of downloading and unpacking software.  We will
    77however repeat some of that information here for those new to building
    88their own software.</para>
    99
    10 <para>One difference from the LFS book is that we do <emphasis>not</emphasis>
    11 mirror the packages on the BLFS website.
    12 Instead, each set of installation instructions contains a URL from which
    13 you can download the package.  We do however keep a selection of patches
    14 available via http/ftp.  These are referenced as needed in the
     10<para>Each set of installation instructions contains a <acronym>URL</acronym>
     11from which you can download the package.  We do however keep a selection of
     12patches available via http.  These are referenced as needed in the
    1513installation instructions.</para>
    1614
    … …  
    3230the following two commands, depending on the filename:</para>
    3331
    34 <screen><userinput>tar -xvzf filename.tar.gz
     32<screen><command>tar -xvzf filename.tar.gz
    3533tar -xvzf filename.tgz
    36 tar -xvzf filename.tar.Z</userinput></screen>
     34tar -xvzf filename.tar.Z</command></screen>
    3735
    3836<para>If a file is tar'ed and bzip2'ed, it can usually be unpacked by
    3937running:</para>
    4038
    41 <screen><userinput>tar -jxvf filename.tar.bz2</userinput></screen>
     39<screen><command>tar -jxvf filename.tar.bz2</command></screen>
    4240
    43 <para>This applies as long as you patched tar to include the j option
    44 during your LFS install.  If you didn't, you can use a slightly
    45 different method:</para>
     41<para>You can also use a slightly different method:</para>
    4642
    47 <screen><userinput>bzcat filename.tar.bz2 | tar -xv</userinput></screen>
     43<screen><command>bzcat filename.tar.bz2 | tar -xv</command></screen>
    4844
    4945<para>Finally, you need to be able to unpack patches which are generally
    … …  
    5248commands depending on whether the file is .gz or .bz2:</para>
    5349
    54 <screen><userinput>gunzip patchname.gz
    55 bunzip2 patchname.bz2</userinput></screen>
     50<screen><command>gunzip patchname.gz
     51bunzip2 patchname.bz2</command></screen>
    5652
    5753</sect2>
Note: See TracChangeset for help on using the changeset viewer.