diff options
| -rw-r--r-- | chapter01/administrativa.xml | 92 | ||||
| -rw-r--r-- | chapter01/askforhelp.xml | 104 | ||||
| -rw-r--r-- | chapter01/bootcd.xml | 13 | ||||
| -rw-r--r-- | chapter01/chapter01.xml | 1 | ||||
| -rw-r--r-- | chapter01/how.xml | 67 |
5 files changed, 15 insertions, 262 deletions
diff --git a/chapter01/administrativa.xml b/chapter01/administrativa.xml index 436e661fe..f7ebba3d1 100644 --- a/chapter01/administrativa.xml +++ b/chapter01/administrativa.xml @@ -9,96 +9,4 @@ <para>See testing</para> -<!-- -<sect2 id="ch-scatter-faq"> -<title>FAQ</title> - -<para>If during the building of your LFS system you encounter any errors, or -have any questions, or think you found a typo in the book, then please first -consult the FAQ (Frequently Asked Questions) at -<ulink url="&faq-root;"/>.</para> - -</sect2> - - -<sect2 id="ch-scatter-irc"> -<title>IRC</title> - -<para>Several members of the LFS community offer assistance on our community -IRC (Internet Relay Chat) network. Before you utilize this mode of support, we -ask that you've at least checked the LFS FAQ (see above) and the mailing list -archives (see below) for the answer to your question. You can find the IRC -network at <uri>irc.linuxfromscratch.org</uri>, <uri>irc.linux-phreak.net</uri> -or <uri>irc.lfs-matrix.de</uri> port 6667. The support channel is named -#LFS-support.</para> - -</sect2> - - -<sect2 id="ch-scatter-maillists" xreflabel="Chapter 1 - Mailing lists"> -<title>Mailing lists</title> - -<para>The <uri>linuxfromscratch.org</uri> server is hosting a number -of mailing lists used for the development of the LFS project. These lists -include, among others, the main development and support lists.</para> - -<para>For information on which lists are available, how to subscribe to them, -their archive locations, and so on, visit <ulink url="&lfs-root;mail.html"/>.</para> - -</sect2> - - -<sect2 id="ch-scatter-newsserver"> -<title>News server</title> - -<para>All the mailing lists hosted at <uri>linuxfromscratch.org</uri> -are also accessible via the NNTP server. All messages posted to a mailing list -are copied to the corresponding newsgroup, and vice versa.</para> - -<para>The news server can be reached at -<uri>news.linuxfromscratch.org</uri>.</para> - -</sect2> - - -<sect2 id="ch-scatter-wiki"> -<title>Wiki</title> - -<para>For more information on a package, updated versions, tweaks, personal -experiences, and so on, see the LFS Wiki at <ulink url="&wiki-root;"/>. You -can add information there yourself too, to help others.</para> - -</sect2> - - -<sect2 id="ch-scatter-references"> -<title>References</title> - -<para>If you need still more detailed information on the packages, -you will find useful pointers on this page: -<ulink url="http://www.109bean.org.uk/LFS-references.html"/>.</para> - -</sect2> - - -<sect2 id="ch-scatter-mirrors" xreflabel="Chapter 1 - Mirror sites"> -<title>Mirror sites</title> - -<para>The LFS project has a number of mirrors set up world-wide to make -accessing the website and downloading the required packages more convenient. -Please visit the website at <ulink url="&lfs-root;"/> for a list of current -mirrors.</para> - -</sect2> - - -<sect2 id="ch-scatter-contactinfo"> -<title>Contact information</title> - -<para>Please direct all your questions and comments to one of the LFS mailing -lists (see above).</para> - -</sect2> ---> - </sect1> diff --git a/chapter01/askforhelp.xml b/chapter01/askforhelp.xml index de599d7c2..c7a53f63e 100644 --- a/chapter01/askforhelp.xml +++ b/chapter01/askforhelp.xml @@ -4,111 +4,9 @@ %general-entities; ]> <sect1 id="prepare-askforhelp"> -<title>How to ask for help</title> +<title>Help</title> <?dbhtml filename="askforhelp.html"?> <para>See testing</para> -<!-- -<para>If you run into a problem while working through this book, you should -first check the FAQ at <ulink url="&faq-root;"/> - often your question -is already answered there. If it is not, you should try to find the source of -the problem. The following hint might give you some ideas for your -troubleshooting: <ulink url="&hints-root;errors.txt"/>.</para> - -<para>If all that fails, you will find that most people on IRC and the mailing -lists (see <xref linkend="ch-scatter-administrativa"/>) are willing to help -you. But to assist them in diagnosing and solving your problem, please include -all relevant information in your request for help.</para> - -<sect2> -<title>Things to mention</title> - -<para>Apart from a brief explanation of the problem you're having, the -essential things to include in your request are:</para> - -<itemizedlist> -<listitem><para>the version of the book you are using (being &version;),</para></listitem> -<listitem><para>the host distribution and version you are using to create -LFS,</para></listitem> -<listitem><para>the package or section giving you problems,</para></listitem> -<listitem><para>the exact error message or symptom you are receiving,</para></listitem> -<listitem><para>whether you have deviated from the book at all.</para></listitem> -</itemizedlist> - -<note><para>Saying that you've deviated from the book doesn't mean -that we won't help you. After all, LFS is about choice. It'll just -help us to see other possible causes of your problem.</para></note> - -</sect2> - -<sect2> -<title>Configure problems</title> - -<para>When something goes wrong during the stage where the configure script -is run, look through the <filename>config.log</filename> file. This file -may contain errors encountered during configure which weren't printed to -the screen. Include those relevant lines if you decide to ask for -help.</para> - -</sect2> - -<sect2> -<title>Compile problems</title> - -<para>To help us find the cause of the problem, both screen output and -the contents of various files are useful. The screen output from both -the ./configure script and the make run can be useful. Don't blindly -include the whole thing but, on the other hand, don't include too little. -As an example, here is some screen output from make:</para> - -<screen><computeroutput>gcc -DALIASPATH=\"/mnt/lfs/usr/share/locale:.\" --DLOCALEDIR=\"/mnt/lfs/usr/share/locale\" -DLIBDIR=\"/mnt/lfs/usr/lib\" --DINCLUDEDIR=\"/mnt/lfs/usr/include\" -DHAVE_CONFIG_H -I. -I. --g -O2 -c getopt1.c -gcc -g -O2 -static -o make ar.o arscan.o commands.o dir.o expand.o file.o -function.o getopt.o implicit.o job.o main.o misc.o read.o remake.o rule.o -signame.o variable.o vpath.o default.o remote-stub.o version.o opt1.o --lutil job.o: In function `load_too_high': -/lfs/tmp/make-3.79.1/job.c:1565: undefined reference to `getloadavg' -collect2: ld returned 1 exit status -make[2]: *** [make] Error 1 -make[2]: Leaving directory `/lfs/tmp/make-3.79.1' -make[1]: *** [all-recursive] Error 1 -make[1]: Leaving directory `/lfs/tmp/make-3.79.1' -make: *** [all-recursive-am] Error 2</computeroutput></screen> - -<para>In this case, many people just include the bottom section where it -says:</para> - -<screen><computeroutput>make [2]: *** [make] Error 1</computeroutput></screen> - -<para>and onwards. This isn't enough for us to diagnose the problem because it -only tells us that <emphasis>something</emphasis> went wrong, not -<emphasis>what</emphasis> went wrong. The whole section, as in the example -above, is what should be included to be helpful, because it includes the -command that was executed and the command's error message(s).</para> - -<para>An excellent article on asking for help on the Internet in general -has been written by Eric S. Raymond. It is available online at -<ulink url="http://catb.org/~esr/faqs/smart-questions.html"/>. -Read and follow the hints in that document and you are much more likely -to get a response to start with and also to get the help you actually -need.</para> - -</sect2> - -<sect2> -<title>Test suite problems</title> - -<para>Many packages provide a test suite which, depending on the importance -of the package, we may encourage you to run. Sometimes packages will -generate false or expected failures. If you encounter these, you can check -the LFS Wiki page at <ulink url="&wiki-root;"/> to see whether we have -already noted and investigated them. If we already know -about them, then usually there is no need to be concerned.</para> - -</sect2> ---> - </sect1> diff --git a/chapter01/bootcd.xml b/chapter01/bootcd.xml new file mode 100644 index 000000000..7fc61cccb --- /dev/null +++ b/chapter01/bootcd.xml @@ -0,0 +1,13 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [ + <!ENTITY % general-entities SYSTEM "../general.ent"> + %general-entities; +]> +<sect1 id="prepare-bootcd"> +<title>About the Included CD</title> +<?dbhtml filename="bootcd.html"?> + +<para>See testing</para> + +</sect1> + diff --git a/chapter01/chapter01.xml b/chapter01/chapter01.xml index 2090daa0e..f06458600 100644 --- a/chapter01/chapter01.xml +++ b/chapter01/chapter01.xml @@ -12,5 +12,6 @@ <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="changelog.xml"/> <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="administrativa.xml"/> <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="askforhelp.xml"/> +<xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="bootcd.xml"/> </chapter> diff --git a/chapter01/how.xml b/chapter01/how.xml index d416d3d59..e273ce5a0 100644 --- a/chapter01/how.xml +++ b/chapter01/how.xml @@ -9,71 +9,4 @@ <para>See testing</para> -<!-- -<para>You are going to build your LFS system by using a previously installed -Linux distribution (such as Debian, Mandrake, Red Hat, or SuSE). This existing -Linux system (the host) will be used as a starting point, because you will need -programs like a compiler, linker and shell to build the new system. Normally -all the required tools are available if you selected <quote>development</quote> -as one of the options when you installed your distribution.</para> - -<para>In <xref linkend="chapter-partitioning"/> you will first create a new Linux native -partition and file system, the place where your new LFS system will be compiled -and installed. Then in <xref linkend="chapter-getting-materials"/> you download all the -packages and patches needed to build an LFS system, and store them on the new -file system. In <xref linkend="chapter-final-preps"/> you set up a good -environment to work in.</para> - -<para><xref linkend="chapter-temporary-tools"/> then discusses the installation of a number -of packages that will form the basic development suite (or <emphasis>toolchain</emphasis>) which is -used to build the actual system in <xref linkend="chapter-building-system"/>. Some of these -packages are needed to resolve circular dependencies - for example, to compile -a compiler you need a compiler.</para> - -<para>The first thing to be done in <xref linkend="chapter-temporary-tools"/> is build a -first pass of the toolchain, made up of Binutils and GCC. The programs from -these packages will be linked statically in order for them to be usable -independently of the host system. The second thing to do is build Glibc, the -C library. Glibc will be compiled by the toolchain programs just built in -the first pass. The third thing to do is build a second pass of the toolchain. -This time the toolchain will be dynamically linked against the newly built -Glibc. The remaining <xref linkend="chapter-temporary-tools"/> packages are all built using -this second pass toolchain and dynamically linked against the new -host-independent Glibc. When this is done, the LFS installation process will no -longer depend on the host distribution, with the exception of the running -kernel.</para> - -<para>You may be thinking that <quote>this seems like a lot of work, just to -get away from my host distribution</quote>. Well, a full technical explanation -is provided at the start of <xref linkend="chapter-temporary-tools"/>, including some notes -on the differences between statically and dynamically linked programs.</para> - -<para>In <xref linkend="chapter-building-system"/> your real LFS system will be built. The -<command>chroot</command> (change root) program is used to enter a virtual environment and start -a new shell whose root directory will be set to the LFS partition. This is very -similar to rebooting and instructing the kernel to mount the LFS partition as -the root partition. The reason that you don't actually reboot, but instead -chroot, is that creating a bootable system requires additional work which isn't -necessary just yet. But the major advantage is that <quote>chrooting</quote> allows you to -continue using the host while LFS is being built. While waiting for package -compilation to complete, you can simply switch to a different VC (Virtual -Console) or X desktop and continue using the computer as you normally -would.</para> - -<para>To finish the installation, the bootscripts are set up in -<xref linkend="chapter-bootscripts"/>, the kernel and bootloader are set up in -<xref linkend="chapter-bootable"/>, and <xref linkend="chapter-finalizing"/> contains some -pointers to help you after you finish the book. Then, finally, you're ready to -reboot your computer into your new LFS system.</para> - -<para>This is the process in a nutshell. Detailed information on the steps you -will take are discussed in the chapters and package descriptions as you -progress through them. If something isn't completely clear now, don't worry, -everything will fall into place soon.</para> - -<para>Please read <xref linkend="chapter-final-preps"/> carefully as it explains - a few important things you should be aware of before you begin to work through -<xref linkend="chapter-temporary-tools"/> and beyond.</para> ---> - </sect1> |