Changeset 9c10139


Ignore:
Timestamp:
01/30/2005 10:21:16 AM (19 years ago)
Author:
Manuel Canales Esparcia <manuel@…>
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.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, 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:
d7ea6f24
Parents:
a460953
Message:

Removed obsolete commented text, chapter01. Added bootcd.xml.

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

Location:
chapter01
Files:
1 added
4 edited

Legend:

Unmodified
Added
Removed

  • chapter01/administrativa.xml

    ra460953 r9c10139  
    1010<para>See testing</para>
    1111
    12 <!--
    13 <sect2 id="ch-scatter-faq">
    14 <title>FAQ</title>
    15 
    16 <para>If during the building of your LFS system you encounter any errors, or
    17 have any questions, or think you found a typo in the book, then please first
    18 consult the FAQ (Frequently Asked Questions) at
    19 <ulink url="&faq-root;"/>.</para>
    20 
    21 </sect2>
    22 
    23 
    24 <sect2 id="ch-scatter-irc">
    25 <title>IRC</title>
    26 
    27 <para>Several members of the LFS community offer assistance on our community
    28 IRC (Internet Relay Chat) network. Before you utilize this mode of support, we
    29 ask that you've at least checked the LFS FAQ (see above) and the mailing list
    30 archives (see below) for the answer to your question. You can find the IRC
    31 network at <uri>irc.linuxfromscratch.org</uri>, <uri>irc.linux-phreak.net</uri>
    32 or <uri>irc.lfs-matrix.de</uri> port 6667. The support channel is named
    33 #LFS-support.</para>
    34 
    35 </sect2>
    36 
    37 
    38 <sect2 id="ch-scatter-maillists" xreflabel="Chapter 1 - Mailing lists">
    39 <title>Mailing lists</title>
    40 
    41 <para>The <uri>linuxfromscratch.org</uri> server is hosting a number
    42 of mailing lists used for the development of the LFS project. These lists
    43 include, among others, the main development and support lists.</para>
    44 
    45 <para>For information on which lists are available, how to subscribe to them,
    46 their archive locations, and so on, visit <ulink url="&lfs-root;mail.html"/>.</para>
    47 
    48 </sect2>
    49 
    50 
    51 <sect2 id="ch-scatter-newsserver">
    52 <title>News server</title>
    53 
    54 <para>All the mailing lists hosted at <uri>linuxfromscratch.org</uri>
    55 are also accessible via the NNTP server. All messages posted to a mailing list
    56 are copied to the corresponding newsgroup, and vice versa.</para>
    57 
    58 <para>The news server can be reached at
    59 <uri>news.linuxfromscratch.org</uri>.</para>
    60 
    61 </sect2>
    62 
    63 
    64 <sect2 id="ch-scatter-wiki">
    65 <title>Wiki</title>
    66 
    67 <para>For more information on a package, updated versions, tweaks, personal
    68 experiences, and so on, see the LFS Wiki at <ulink url="&wiki-root;"/>. You
    69 can add information there yourself too, to help others.</para>
    70 
    71 </sect2>
    72 
    73 
    74 <sect2 id="ch-scatter-references">
    75 <title>References</title>
    76 
    77 <para>If you need still more detailed information on the packages,
    78 you will find useful pointers on this page:
    79 <ulink url="http://www.109bean.org.uk/LFS-references.html"/>.</para>
    80 
    81 </sect2>
    82 
    83 
    84 <sect2 id="ch-scatter-mirrors" xreflabel="Chapter 1 - Mirror sites">
    85 <title>Mirror sites</title>
    86 
    87 <para>The LFS project has a number of mirrors set up world-wide to make
    88 accessing the website and downloading the required packages more convenient.
    89 Please visit the website at <ulink url="&lfs-root;"/> for a list of current
    90 mirrors.</para>
    91 
    92 </sect2>
    93 
    94 
    95 <sect2 id="ch-scatter-contactinfo">
    96 <title>Contact information</title>
    97 
    98 <para>Please direct all your questions and comments to one of the LFS mailing
    99 lists (see above).</para>
    100 
    101 </sect2>
    102 -->
    103 
    10412</sect1>

  • chapter01/askforhelp.xml

    ra460953 r9c10139  
    55]>
    66<sect1 id="prepare-askforhelp">
    7 <title>How to ask for help</title>
     7<title>Help</title>
    88<?dbhtml filename="askforhelp.html"?>
    99
    1010<para>See testing</para>
    1111
    12 <!--
    13 <para>If you run into a problem while working through this book, you should
    14 first check the FAQ at <ulink url="&faq-root;"/> - often your question
    15 is already answered there. If it is not, you should try to find the source of
    16 the problem. The following hint might give you some ideas for your
    17 troubleshooting: <ulink url="&hints-root;errors.txt"/>.</para>
    18 
    19 <para>If all that fails, you will find that most people on IRC and the mailing
    20 lists (see <xref linkend="ch-scatter-administrativa"/>) are willing to help
    21 you. But to assist them in diagnosing and solving your problem, please include
    22 all relevant information in your request for help.</para>
    23 
    24 <sect2>
    25 <title>Things to mention</title>
    26  
    27 <para>Apart from a brief explanation of the problem you're having, the
    28 essential things to include in your request are:</para>
    29 
    30 <itemizedlist>
    31 <listitem><para>the version of the book you are using (being &version;),</para></listitem>
    32 <listitem><para>the host distribution and version you are using to create
    33 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>whether you have deviated from the book at all.</para></listitem>
    37 </itemizedlist>
    38 
    39 <note><para>Saying that you've deviated from the book doesn't mean
    40 that we won't help you. After all, LFS is about choice. It'll just
    41 help us to see other possible causes of your problem.</para></note>
    42 
    43 </sect2>
    44 
    45 <sect2>
    46 <title>Configure problems</title>
    47 
    48 <para>When something goes wrong during the stage where the configure script
    49 is run, look through the <filename>config.log</filename> file. This file
    50 may contain errors encountered during configure which weren't printed to
    51 the screen. Include those relevant lines if you decide to ask for
    52 help.</para>
    53 
    54 </sect2>
    55 
    56 <sect2>
    57 <title>Compile problems</title>
    58 
    59 <para>To help us find the cause of the problem, both screen output and
    60 the contents of various files are useful. The screen output from both
    61 the ./configure script and the make run can be useful. Don't blindly
    62 include the whole thing but, on the other hand, don't include too little.
    63 As an example, here is some screen output from make:</para>
    64 
    65 <screen><computeroutput>gcc -DALIASPATH=\"/mnt/lfs/usr/share/locale:.\"
    66 -DLOCALEDIR=\"/mnt/lfs/usr/share/locale\" -DLIBDIR=\"/mnt/lfs/usr/lib\"
    67 -DINCLUDEDIR=\"/mnt/lfs/usr/include\" -DHAVE_CONFIG_H -I. -I.
    68 -g -O2 -c getopt1.c
    69 gcc -g -O2 -static -o make ar.o arscan.o commands.o dir.o expand.o file.o
    70 function.o getopt.o implicit.o job.o main.o misc.o read.o remake.o rule.o
    71 signame.o variable.o vpath.o default.o remote-stub.o version.o opt1.o
    72 -lutil job.o: In function `load_too_high':
    73 /lfs/tmp/make-3.79.1/job.c:1565: undefined reference to `getloadavg'
    74 collect2: ld returned 1 exit status
    75 make[2]: *** [make] Error 1
    76 make[2]: Leaving directory `/lfs/tmp/make-3.79.1'
    77 make[1]: *** [all-recursive] Error 1
    78 make[1]: Leaving directory `/lfs/tmp/make-3.79.1'
    79 make: *** [all-recursive-am] Error 2</computeroutput></screen>
    80 
    81 <para>In this case, many people just include the bottom section where it
    82 says:</para>
    83 
    84 <screen><computeroutput>make [2]: *** [make] Error 1</computeroutput></screen>
    85 
    86 <para>and onwards. This isn't enough for us to diagnose the problem because it
    87 only tells us that <emphasis>something</emphasis> went wrong, not
    88 <emphasis>what</emphasis> went wrong. The whole section, as in the example
    89 above, is what should be included to be helpful, because it includes the
    90 command that was executed and the command's error message(s).</para>
    91 
    92 <para>An excellent article on asking for help on the Internet in general
    93 has been written by Eric S. Raymond. It is available online at
    94 <ulink url="http://catb.org/~esr/faqs/smart-questions.html"/>.
    95 Read and follow the hints in that document and you are much more likely
    96 to get a response to start with and also to get the help you actually
    97 need.</para>
    98 
    99 </sect2>
    100 
    101 <sect2>
    102 <title>Test suite problems</title>
    103 
    104 <para>Many packages provide a test suite which, depending on the importance
    105 of the package, we may encourage you to run. Sometimes packages will
    106 generate false or expected failures. If you encounter these, you can check
    107 the LFS Wiki page at <ulink url="&wiki-root;"/> to see whether we have
    108 already noted and investigated them. If we already know
    109 about them, then usually there is no need to be concerned.</para>
    110 
    111 </sect2>
    112 -->
    113 
    11412</sect1>

  • chapter01/chapter01.xml

    ra460953 r9c10139  
    1313<xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="administrativa.xml"/>
    1414<xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="askforhelp.xml"/>
     15<xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="bootcd.xml"/>
    1516
    1617</chapter>

  • chapter01/how.xml

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