Changeset 6e35438


Ignore:
Timestamp:
08/08/2004 02:09:51 AM (20 years ago)
Author:
Gerard Beekmans <gerard@…>
Branches:
6.0
Children:
9a207c4
Parents:
2621275
Message:

Completed global edits for upcoming 6.0 release

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/branches/testing/BOOK@3995 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

Location:
chapter01
Files:
4 edited

Legend:

Unmodified
Added
Removed

  • chapter01/administrativa.xml

    r2621275 r6e35438  
    1212<title>FAQ</title>
    1313
    14 <para>If during the building of your LFS system you encounter any errors, or
    15 have any questions, or think you found a typo in the book, then please first
    16 consult the FAQ (Frequently Asked Questions) at
     14<para>If during the building of your LFS system you encounter any
     15errors, have any questions, or think you found a typo in the book,
     16please start by consulting the FAQs (Frequently Asked Questions) at
    1717<ulink url="&faq-root;"/>.</para>
    18 
    1918</sect2>
    2019
     20<sect2 id="ch-scatter-maillists" xreflabel="Chapter 1 - Mailing lists">
     21<title>Mailing lists</title>
     22
     23<para>The <uri>linuxfromscratch.org</uri> server hosts a number of
     24mailing lists used for the development of the LFS project. These lists
     25include, the main development and support lists, among others.</para>
     26
     27<para>For information on the different lists, how to subscribe, archive
     28locations, and additional information, visit
     29<ulink url="&lfs-root;mail.html"/>.</para>
     30</sect2>
    2131
    2232<sect2 id="ch-scatter-irc">
    2333<title>IRC</title>
    2434
    25 <para>Several members of the LFS community offer assistance on our community
    26 IRC (Internet Relay Chat) network. Before you utilize this mode of support, we
    27 ask that you've at least checked the LFS FAQ (see above) and the mailing list
    28 archives (see below) for the answer to your question. You can find the IRC
    29 network at <uri>irc.linuxfromscratch.org</uri> or
    30 <uri>irc.linux-phreak.net</uri> port 6667. The support channel is
    31 named #LFS-support.</para>
    32 
     35<para>Several members of the LFS community offer assistance on our
     36community Internet Relay Chat (IRC) network. Before using this
     37support, please make sure that your question isn't answered in the LFS
     38FAQs or the mailing list archives. You can find the IRC network at
     39irc.linuxfromscratch.org or irc.linux-phreak.net. The support channel
     40is named #LFS-support.</para>
    3341</sect2>
    34 
    35 
    36 <sect2 id="ch-scatter-maillists" xreflabel="Chapter 1 - Mailing lists">
    37 <title>Mailing lists</title>
    38 
    39 <para>The <uri>linuxfromscratch.org</uri> server is hosting a number
    40 of mailing lists used for the development of the LFS project. These lists
    41 include, among others, the main development and support lists.</para>
    42 
    43 <para>For information on which lists are available, how to subscribe to them,
    44 their archive locations, and so on, visit <ulink url="&lfs-root;mail.html"/>.</para>
    45 
    46 </sect2>
    47 
    4842
    4943<sect2 id="ch-scatter-newsserver">
    … …  
    5145
    5246<para>All the mailing lists hosted at <uri>linuxfromscratch.org</uri>
    53 are also accessible via the NNTP server. All messages posted to a mailing list
    54 are copied to the corresponding newsgroup, and vice versa.</para>
     47are also accessible via the NNTP server. All messages posted to a
     48mailing list are copied to the corresponding newsgroup, and vice
     49versa.</para>
    5550
    56 <para>The news server can be reached at
     51<para>The news server is located at
    5752<uri>news.linuxfromscratch.org</uri>.</para>
    58 
    5953</sect2>
    60 
    6154
    6255<sect2 id="ch-scatter-wiki">
    6356<title>Wiki</title>
    6457
    65 <para>For more information on a package, updated versions, tweaks, personal
    66 experiences, and so on, see the LFS Wiki at <ulink url="&wiki-root;"/>. You
    67 can add information there yourself too, to help others.</para>
    68 
     58<para>For more information on packages, updated versions, tweaks, and
     59personal experiences, see the LFS Wiki at <ulink url="&wiki-root;"/>.
     60Users can also add information there to help others with their future
     61LFS activities.</para>
    6962</sect2>
    70 
    7163
    7264<sect2 id="ch-scatter-references">
    7365<title>References</title>
    7466
    75 <para>If you need still more detailed information on the packages,
    76 you will find useful pointers on this page:
    77 <ulink url="http://www.109bean.org.uk/LFS-references.html"/>.</para>
    78 
     67<para>For additional information on the packages, useful tips are
     68available at
     69<ulink
     70url="http://www.linuxfromscratch.org/~matthew/LFS-references.html"/>.</para>
    7971</sect2>
    8072
    … …  
    8375<title>Mirror sites</title>
    8476
    85 <para>The LFS project has a number of mirrors set up world-wide to make
    86 accessing the website and downloading the required packages more convenient.
    87 Please visit the website at <ulink url="&lfs-root;"/> for a list of current
    88 mirrors.</para>
    89 
     77<para>The LFS project has a number of world-wide mirrors to make
     78accessing the website and downloading the required packages more
     79convenient. Please visit the LFS website at <ulink url="&lfs-root;"/>
     80for a list of current mirrors.</para>
    9081</sect2>
    91 
    9282
    9383<sect2 id="ch-scatter-contactinfo">
    … …  
    9686<para>Please direct all your questions and comments to one of the LFS mailing
    9787lists (see above).</para>
    98 
    9988</sect2>
    10089
     90</sect1>
    10191
    102 </sect1>

  • chapter01/askforhelp.xml

    r2621275 r6e35438  
    55]>
    66<sect1 id="prepare-askforhelp">
    7 <title>How to ask for help</title>
     7<title>Help</title>
    88<?dbhtml filename="askforhelp.html"?>
    99
    10 <para>If you run into a problem while working through this book, you should
    11 first check the FAQ at <ulink url="&faq-root;"/> -- often your question
    12 is already answered there. If it is not, you should try to find the source of
    13 the problem. The following hint might give you some ideas for your
    14 troubleshooting: <ulink url="&hints-root;errors.txt"/>.</para>
     10<para>If you encounter an issue or have a question while working
     11through this book, check our FAQs page at <ulink url="&faq-root;"/>.
     12Often times questions are already answered there. If your question is
     13not answered on this page, try to find the source of the problem. The
     14following hint will give you some guidance for troubleshooting: <ulink
     15url="&hints-root;errors.txt"/>.</para>
    1516
    16 <para>If all that fails, you will find that most people on IRC and the mailing
    17 lists (see <xref linkend="ch-scatter-administrativa"/>) are willing to help
    18 you. But to assist them in diagnosing and solving your problem, please include
     17<para>We also have a wonderful LFS community that is willing to offer
     18assistance through IRC and the mailing lists (see the <xref
     19linkend="ch-scatter-administrativa"/> section of this book). In order
     20to assist them with diagnosing and solving the problem, please include
    1921all relevant information in your request for help.</para>
    2022
    … …  
    2224<title>Things to mention</title>
    2325 
    24 <para>Apart from a brief explanation of the problem you're having, the
    25 essential things to include in your request are:</para>
     26<para>Apart from a brief explanation of the problem being experience,
     27the essential things to include in your request for help are:</para>
    2628
    2729<itemizedlist>
    28 <listitem><para>the version of the book you are using (being &version;),</para></listitem>
    29 <listitem><para>the host distribution and version you are using to create
    30 LFS,</para></listitem>
    31 <listitem><para>the package or section giving you problems,</para></listitem>
    32 <listitem><para>the exact error message or symptom you are receiving,</para></listitem>
    33 <listitem><para>whether you have deviated from the book at all.</para></listitem>
     30<listitem><para>The version of the book you are using (in this case
     31&version;)</para></listitem>
     32<listitem><para>The host distribution and version you are using to
     33create LFS</para></listitem>
     34<listitem><para>The package or section giving you problems</para></listitem>
     35<listitem><para>The exact error message or symptom you are receiving</para></listitem>
     36<listitem><para>Note whether you have deviated from the book at all </para></listitem>
    3437</itemizedlist>
    3538
    36 <note><para>Saying that you've deviated from the book doesn't mean
    37 that we won't help you. After all, LFS is about choice. It'll just
    38 help us to see other possible causes of your problem.</para></note>
    39 
     39<note><para>Deviating from this book does <emphasis>not</emphasis>
     40mean that we won't help you. After all, LFS is about your personal
     41preference. Being upfront any changes to the established procedure
     42help us evaluate and determine possible causes of your
     43problem.</para></note>
    4044</sect2>
    4145
    … …  
    4347<title>Configure problems</title>
    4448
    45 <para>When something goes wrong during the stage where the configure script
    46 is run, look through the <filename>config.log</filename> file. This file
    47 may contain errors encountered during configure which weren't printed to
    48 the screen. Include those relevant lines if you decide to ask for
    49 help.</para>
    50 
     49<para>If something goes wrong during the stage where the configure
     50script is run, review the <filename>config.log</filename> file. This
     51file may contain errors encountered during configure which were not
     52printed to the screen. Include those relevant lines if you need to ask
     53for help.</para>
    5154</sect2>
    5255
    … …  
    5457<title>Compile problems</title>
    5558
    56 <para>To help us find the cause of the problem, both screen output and
    57 the contents of various files are useful. The screen output from both
    58 the ./configure script and the make run can be useful. Don't blindly
    59 include the whole thing but, on the other hand, don't include too little.
    60 As an example, here is some screen output from make:</para>
     59<para>The both screen output and the contents of various files are
     60useful in determining the cause of compile issues. The screen output
     61from both the ./configure script and the make run can be helpful. It
     62is not necessary to include the entire output, but do include enough
     63of the relevant information. Below is an example of the type of
     64information to include from the screen output from make:</para>
    6165
    6266<screen><computeroutput>gcc -DALIASPATH=\"/mnt/lfs/usr/share/locale:.\"
    … …  
    7680make: *** [all-recursive-am] Error 2</computeroutput></screen>
    7781
    78 <para>In this case, many people just include the bottom section where it
    79 says:</para>
     82<para>In this case, many people would just include the bottom
     83section:</para>
    8084
    8185<screen><computeroutput>make [2]: *** [make] Error 1</computeroutput></screen>
    8286
    83 <para>and onwards. This isn't enough for us to diagnose the problem because it
    84 only tells us that <emphasis>something</emphasis> went wrong, not
    85 <emphasis>what</emphasis> went wrong. The whole section, as in the example
    86 above, is what should be included to be helpful, because it includes the
    87 command that was executed and the command's error message(s).</para>
     87<para>This is not enough information to properly diagnose the problem
     88because it only notes that something went wrong, not
     89<emphasis>what</emphasis> went wrong.  The entire section, as in the
     90example above, is what should be saved because it includes the command
     91that was executed and the associated error message(s).</para>
    8892
    89 <para>An excellent article on asking for help on the Internet in general
    90 has been written by Eric S. Raymond. It is available online at
    91 <ulink url="http://catb.org/~esr/faqs/smart-questions.html"/>.
    92 Read and follow the hints in that document and you are much more likely
    93 to get a response to start with and also to get the help you actually
    94 need.</para>
    95 
     93<para>An excellent article about asking for help on the Internet is
     94available online at <ulink
     95url="http://catb.org/~esr/faqs/smart-questions.html"/>.  Read and
     96follow the hints in this document to increase your changes of getting
     97the help you need.</para>
    9698</sect2>
    9799
    … …  
    99101<title>Test suite problems</title>
    100102
    101 <para>Many packages provide a test suite which, depending on the importance
    102 of the package, we may encourage you to run. Sometimes packages will
    103 generate false or expected failures. If you encounter these, you can check
    104 the LFS Wiki page at <ulink url="&wiki-root;"/> to see whether we have
    105 already noted and investigated them. If we already know
    106 about them, then usually there is no need to be concerned.</para>
    107 
     103<para>Many packages provide a test suite which, depending on the
     104importance of the package, should be run. Sometimes packages will
     105generate false or expected failures. If these errors are encountered,
     106check the LFS Wiki page at <ulink url="&wiki-root;"/> to see if we have
     107noted and investigated these issues. If these issues are noted and
     108addressed, there is no need to be concerned.</para>
    108109</sect2>
    109110
     111</sect1>
    110112
    111 </sect1>

  • chapter01/changelog.xml

    r2621275 r6e35438  
    2424<listitem><para>binutils-2.15</para></listitem>
    2525<listitem><para>bison-1.875a</para></listitem>
     26<listitem><para>expect-5.42.0</para></listitem>
    2627<listitem><para>file-4.10</para></listitem>
    2728<listitem><para>flex-2.5.31</para></listitem>
    … …  
    7980</listitem>
    8081
     82<listitem><para>August 7th, 2004 [gerard]: Completed global textual
     83edits.</para></listitem>
     84
     85<listitem><para>August 7th, 2004 [gerard]: Upgraded to
     86expect-5.42.0.</para></listitem>
     87
     88<listitem><para>August 7th, 2004 [gerard]: hostname binary moved to
     89/bin as well.</para></listitem>
     90
     91<listitem><para>August 3rd, 2004 [jim]: Made suggested change to the
     92home location of pt_chown</para></listitem>
     93
    8194<listitem><para>July 30, 2004 [jeremy]: Upgraded to automake-1.9, man-1.5n,
    8295file-4.10, bash-3.0, perl-5.8.5, readline-5.0, tcl-8.4.7, binutils-2.15.91.0.2

  • chapter01/how.xml

    r2621275 r6e35438  
    55]>
    66<sect1 id="ch-scatter-how">
    7 <title>How things are going to be done</title>
     7<title>How to Build an LFS System</title>
    88<?dbhtml filename="how.html"?>
    99
    10 <para>You are going to build your LFS system by using a previously installed
    11 Linux distribution (such as Debian, Mandrake, Red Hat, or SuSE). This existing
    12 Linux system (the host) will be used as a starting point, because you will need
    13 programs like a compiler, linker and shell to build the new system. Normally
    14 all the required tools are available if you selected <quote>development</quote>
    15 as one of the options when you installed your distribution.</para>
     10<para>The LFS system will be built by using a previously installed
     11Linux distribution (such as Debian, Mandrake, Red Hat, or SuSE). This
     12existing Linux system (the host) will be used as a starting point to
     13provide necessary programs, including a compiler, linker, and shell,
     14to build the new system. Select the <quote>development</quote> option
     15during the distribution installation to be able to access these
     16tools.</para>
    1617
    17 <para>In <xref linkend="chapter-partitioning"/> you will first create a new Linux native
    18 partition and file system, the place where your new LFS system will be compiled
    19 and installed. Then in <xref linkend="chapter-getting-materials"/> you download all the
    20 packages and patches needed to build an LFS system, and store them on the new
    21 file system. In <xref linkend="chapter-final-preps"/> you set up a good
    22 environment to work in.</para>
     18<para><xref linkend="chapter-partitioning"/> of this book describes how
     19to create a new Linux native partition and file system, the place
     20where the new LFS system will be compiled and installed. <xref
     21linkend="chapter-getting-materials"/> explains which packages and
     22patches need to be downloaded to build an LFS system, and how to store
     23them on the new file system. <xref linkend="chapter-final-preps"/>
     24discusses the setup for an appropriate work environment. Please read
     25<xref linkend="chapter-final-preps"/> carefully as it explains several
     26important issues the developer should be aware of before beginning to
     27work through <xref linkend="chapter-temporary-tools"/> and
     28beyond.</para>
    2329
    24 <para><xref linkend="chapter-temporary-tools"/> then discusses the installation of a number
    25 of packages that will form the basic development suite (or <emphasis>toolchain</emphasis>) which is
    26 used to build the actual system in <xref linkend="chapter-building-system"/>. Some of these
    27 packages are needed to resolve circular dependencies -- for example, to compile
    28 a compiler you need a compiler.</para>
     30<para><xref linkend="chapter-temporary-tools"/> explains the
     31installation of a number of packages that will form the basic
     32development suite (or toolchain) which is used to build the actual
     33system in <xref linkend="chapter-building-system"/>. Some of these
     34packages are needed to resolve circular dependencies -- for example,
     35to compile a compiler, you need a compiler.</para>
    2936
    30 <para>The first thing to be done in <xref linkend="chapter-temporary-tools"/> is build a
    31 first pass of the toolchain, made up of Binutils and GCC. The programs from
    32 these packages will be linked statically in order for them to be usable
    33 independently of the host system. The second thing to do is build Glibc, the
    34 C library. Glibc will be compiled by the toolchain programs just built in
    35 the first pass. The third thing to do is build a second pass of the toolchain.
    36 This time the toolchain will be dynamically linked against the newly built
    37 Glibc. The remaining <xref linkend="chapter-temporary-tools"/> packages are all built using
    38 this second pass toolchain and dynamically linked against the new
    39 host-independent Glibc. When this is done, the LFS installation process will no
    40 longer depend on the host distribution, with the exception of the running
    41 kernel.</para>
     37<para><xref linkend="chapter-temporary-tools"/> also shows the user how
     38to build a first pass of the toolchain, including Binutils and GCC
     39(first pass basically means these two core packages will be
     40re-installed a second time). The programs from these packages will be
     41linked statically in order to be used independently of the host
     42system. The next step is to build Glibc, the C library. Glibc will be
     43compiled by the toolchain programs built in the first pass. Then, a
     44second pass of the toolchain will be built. This time, the toolchain
     45will be dynamically linked against the newly built Glibc. The
     46remaining <xref linkend="chapter-temporary-tools"/> packages are built
     47using this second pass toolchain. When this is done, the LFS
     48installation process will no longer depend on the host distribution,
     49with the exception of the running kernel.</para>
    4250
    43 <para>You may be thinking that <quote>this seems like a lot of work, just to
    44 get away from my host distribution</quote>. Well, a full technical explanation
    45 is provided at the start of <xref linkend="chapter-temporary-tools"/>, including some notes
    46 on the differences between statically and dynamically linked programs.</para>
     51<para>While this may initially seem like a lot of work to get away
     52from a host distribution, a full technical explanation is provided at
     53the beginning of Chapter 5, including notes on the differences between
     54statically and dynamically-linked programs.</para>
    4755
    48 <para>In <xref linkend="chapter-building-system"/> your real LFS system will be built. The
    49 <command>chroot</command> (change root) program is used to enter a virtual environment and start
    50 a new shell whose root directory will be set to the LFS partition. This is very
    51 similar to rebooting and instructing the kernel to mount the LFS partition as
    52 the root partition. The reason that you don't actually reboot, but instead
    53 chroot, is that creating a bootable system requires additional work which isn't
    54 necessary just yet. But the major advantage is that <quote>chrooting</quote> allows you to
    55 continue using the host while LFS is being built. While waiting for package
    56 compilation to complete, you can simply switch to a different VC (Virtual
    57 Console) or X desktop and continue using the computer as you normally
    58 would.</para>
     56<para>In <xref linkend="chapter-building-system"/>, the full LFS system is
     57built. The chroot (change root) program is used to enter a virtual
     58environment and start a new shell whose root directory will be set to
     59the LFS partition. This is very similar to rebooting and instructing
     60the kernel to mount the LFS partition as the root partition. The
     61system doesn't actually reboot, but instead chroots because creating a
     62bootable system requires additional work which isn't necessary just
     63yet. The major advantage is that <quote>chrooting</quote> allows the
     64builder to continue using the host while LFS is being built. While
     65waiting for package compilation to complete, a user can switch to a
     66different virtual console (VC) or X desktop and continue using the
     67computer as normal.</para>
    5968
    60 <para>To finish the installation, the bootscripts are set up in
    61 <xref linkend="chapter-bootscripts"/>, the kernel and bootloader are set up in
    62 <xref linkend="chapter-bootable"/>, and <xref linkend="chapter-finalizing"/> contains some
    63 pointers to help you after you finish the book. Then, finally, you're ready to
    64 reboot your computer into your new LFS system.</para>
     69<para>To finish the installation, the bootscripts are set up in <xref
     70linkend="chapter-bootscripts"/>, and the kernel and bootloader are set
     71up in <xref linkend="chapter-bootable"/>. <xref
     72linkend="chapter-finalizing"/> contains information on furthering the
     73LFS experience beyond this book.  After the steps in this book have
     74been implemented, the computer will be ready to reboot into the new
     75LFS system.</para>
    6576
    66 <para>This is the process in a nutshell. Detailed information on the steps you
    67 will take are discussed in the chapters and package descriptions as you
    68 progress through them. If something isn't completely clear now, don't worry,
    69 everything will fall into place soon.</para>
    70 
    71 <para>Please read <xref linkend="chapter-final-preps"/> carefully as it explains
    72  a few important things you should be aware of before you begin to work through
    73 <xref linkend="chapter-temporary-tools"/> and beyond.</para>
     77<para>This is the process in a nutshell. Detailed information on each
     78step is discussed in the following chapters and package descriptions.
     79Items that may seem complicated will be clarified, and everything will
     80fall into place as the developer embarks on the LFS adventure.</para>
    7481
    7582</sect1>
     83
Note: See TracChangeset for help on using the changeset viewer.