From 673b0d84ba9591e07c0bdf0ee49d92eba10f502c Mon Sep 17 00:00:00 2001 From: Matthew Burgess Date: Mon, 3 May 2004 10:59:46 +0000 Subject: * Merged newxml into HEAD git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3435 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter01/administrativa.xml | 101 +++++++++++++++++++++++++++++++++++++++++++ chapter01/askforhelp.xml | 18 +++++--- chapter01/changelog.xml | 75 +++++++++++++++++++++++++------- chapter01/chapter01.xml | 23 +++++++--- chapter01/contactinfo.xml | 98 ----------------------------------------- chapter01/how.xml | 92 +++++++++++++++++++++------------------ 6 files changed, 240 insertions(+), 167 deletions(-) create mode 100644 chapter01/administrativa.xml delete mode 100644 chapter01/contactinfo.xml (limited to 'chapter01') diff --git a/chapter01/administrativa.xml b/chapter01/administrativa.xml new file mode 100644 index 000000000..9046c9217 --- /dev/null +++ b/chapter01/administrativa.xml @@ -0,0 +1,101 @@ + + + %general-entities; +]> + +Resources + + + + +FAQ + +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 +. + + + + + +IRC + +Several members of the LFS community offer assistance on our community +IRC (Internet Relay Chat) server. 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 +server at irc.linuxfromscratch.org port 6667. The +support channel is named #LFS-support. + + + + + +Mailing lists + +The linuxfromscratch.org 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. + +For information on which lists are available, how to subscribe to them, +their archive locations, and so on, visit . + + + + + +News server + +All the mailing lists hosted at linuxfromscratch.org +are also accessible via the NNTP server. All messages posted to a mailing list +are copied to the corresponding newsgroup, and vice versa. + +The news server can be reached at +news.linuxfromscratch.org. + + + + + +Wiki + +For more information on a package, updated versions, tweaks, personal +experiences, and so on, see the LFS Wiki at . You +can add information there yourself too, to help others. + + + + + +References + +If you need still more detailed information on the packages, +you will find useful pointers on this page: +. + + + + + +Mirror sites + +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 for a list of current +mirrors. + + + + + +Contact information + +Please direct all your questions and comments to one of the LFS mailing +lists (see above). + + + + + diff --git a/chapter01/askforhelp.xml b/chapter01/askforhelp.xml index b04a8161b..747a74b92 100644 --- a/chapter01/askforhelp.xml +++ b/chapter01/askforhelp.xml @@ -1,9 +1,14 @@ + + + %general-entities; +]> How to ask for help - + If you run into a problem while working through this book, you should -first check the FAQ at -- most likely your question +first check the FAQ at -- 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: . @@ -22,7 +27,7 @@ essential things to include in your request are: the version of the book you are using (being &version;), the host distribution and version you are using to create -LFS from, +LFS, the package or section giving you problems, the exact error message or symptom you are receiving, whether you have deviated from the book at all. @@ -51,7 +56,7 @@ help. 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. +include the whole thing but, on the other hand, don't include too little. As an example, here is some screen output from make: gcc -DALIASPATH=\"/mnt/lfs/usr/share/locale:.\" @@ -82,8 +87,8 @@ above, is what should be included to be helpful, because it includes the command that was executed and the command's error message(s). An excellent article on asking for help on the Internet in general -has been written by Eric S. Raymond. It is available online at . +has been written by Eric S. Raymond. It is available online at +. 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. @@ -104,4 +109,3 @@ about them, then usually there is no need to be concerned. - diff --git a/chapter01/changelog.xml b/chapter01/changelog.xml index 744056af0..d152c2a3e 100644 --- a/chapter01/changelog.xml +++ b/chapter01/changelog.xml @@ -1,12 +1,17 @@ + + + %general-entities; +]> Changelog - + This is version &version; of the Linux From Scratch book, dated &releasedate;. If this book is more than two months old, a newer and better version is probably already available. To find out, please check one of the mirrors via . - + Below is a list of changes made since the previous release of the book, first a summary, then a detailed log. @@ -14,37 +19,78 @@ first a summary, then a detailed log. Upgraded to: +autoconf-2.59 +automake-1.8.4 +coreutils-5.2.1 +e2fsprogs-1.35 +expect-5.41.0 +file-4.09 +gcc-3.3.3 +gettext-0.14.1 +grub-0.94 +kbd-1.12 less-382 -lfs-utils-0.5 -linux-2.4.25 +lfs-bootscripts-2.0.4 +libtool-2.5.6 +linux-2.4.26 man-pages-1.66 +modutils-2.4.27 ncurses-5.4 -procps-3.2.0 +perl-5.8.4 +procps-3.2.1 +psmisc-21.4 +sed-4.0.9 +shadow-4.0.4.1 +tar-1.13.94 +tcl-8.4.6 +texinfo-4.7 +util-linux-2.12a Added: +iana-etc-1.00 +inetutils-1.4.2-no_server_man_pages-1.patch make_devices-1.2 +mktemp-1.5 + mktemp-1.5-add-tempfile.patch Removed: +gcc-3.3.1-suppress-libiberty.patch +lfs-utils-0.5 MAKEDEV-1.7 +man-1.5m2-manpath.patch +man-1.5m2-pager.patch ncurses-5.3-etip-2.patch +ncurses-5.3-vsscanf.patch +perl-5.8.0-libc-3.patch +procps-3.1.11-locale-fix.patch +shadow-4.0.3-newgrp-fix.patch +zlib-1.1.4-vsnprintf.patch -March 21st, 2004 [jeremy]: Chapter 6 - Grub - Removed the sed -used with grub-0.93 for gcc 3.3 compliance, as it's not necessary with -0.94 +May 2nd, 2004 [matt]: Quoted chroot commands in chapter 6 (bug +#818). +May 2nd, 2004 [matt]: Removed description of the now +non-existent part IV from the structure section in the prologue. + +May 1st, 2004 [jeremy]: Added creation of the /media and /srv +directories, as well as 2 directories under /media for floppy and cdrom, as per +FHS - fixes bugzilla bug #785 and #819. + +April 14th, 2004 [jeremy]: Updated to lfs-bootscripts-2.0.3, no +textual changes needed -March 9th, 2004 [alex]: Chapter 6 - Removed --login from the -chroot commands. +March 24th, 2004 [jeremy]: Chapter 7 - Updated to the new +lfs-bootscripts-2.0.2, and all necessary changes to the bootscript +configuration -March 6th, 2004 [alex]: Rotated the contents of chapters 2, 3 -and 4. +March 21st, 2004 [winkie]: Chapter 6 - Replaced Lfs-Utils +with Iana-Etc and Mktemp. February 27th, 2004 [jeremy]: Upgraded to Procps-3.2.0. @@ -71,7 +117,7 @@ system from chapter 9 to the end of chapter 6. E2fsprogs: Clarified the prerequisites for running the tests. February 19th, 2004 [alex]: Chapter 5 - Stripping: Removed -an unnecessary "{,share/}" from the documentation's rm +an unnecessary {,share/} from the documentation's rm command. February 14th, 2004 [jeremy]: Chapter 6 - Upgraded to @@ -91,7 +137,7 @@ installation section to chapter 7. Man-pages-1.66. February 7th, 2004 [alex]: Chapter 1 - Moved the Conventions -and Acknowledgements sections to the Preface. +and Acknowledgments sections to the Preface. February 7th, 2004 [alex]: Chapter 6 - Creating devices: replaced the MAKEDEV script with the make_devices script. Contributed by @@ -110,4 +156,3 @@ added a little arch script for Perl. Release of version 5.1-pre1 on February 1st, 2004. - diff --git a/chapter01/chapter01.xml b/chapter01/chapter01.xml index 0782d3e5c..0698615df 100644 --- a/chapter01/chapter01.xml +++ b/chapter01/chapter01.xml @@ -1,10 +1,21 @@ - + + + %general-entities; +]> + + Introduction - + -&c1-how; -&c1-changelog; -&c1-resources; -&c1-askforhelp; + + + + + + + + + diff --git a/chapter01/contactinfo.xml b/chapter01/contactinfo.xml deleted file mode 100644 index 0d8351e43..000000000 --- a/chapter01/contactinfo.xml +++ /dev/null @@ -1,98 +0,0 @@ - -Resources - - - - -FAQ - -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 -. - - - - - -IRC - -Several members of the LFS community offer assistance on our community -IRC (Internet Relay Chat) server. 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 -server at irc.linuxfromscratch.org port 6667. The -support channel is named #LFS-support. - - - - - -Mailing lists - -The linuxfromscratch.org 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. - -For information on which lists are available, how to subscribe to them, -their archive locations, and so on, visit . - - - - - -News server - -All the mailing lists hosted at linuxfromscratch.org -are also accessible via the NNTP server. All messages posted to a mailing list -are copied to the correspondent newsgroup, and vice versa. - -The news server can be reached at -news.linuxfromscratch.org. - - - - - -Wiki - -For more information on a package, updated versions, tweaks, personal -experiences, and so on, see the LFS Wiki at . You -can add information there yourself too, to help others. - - - - - -References - -If you need still more detailed information on the packages, -you will find useful pointers on this page: -. - - - - - -Mirror sites - -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 for a list of current -mirrors. - - - - - -Contact information - -Please direct all your questions and comments to one of the LFS mailing -lists (see above). - - - - - - diff --git a/chapter01/how.xml b/chapter01/how.xml index 18bbfc3fc..1181abb3e 100644 --- a/chapter01/how.xml +++ b/chapter01/how.xml @@ -1,6 +1,11 @@ + + + %general-entities; +]> How things are going to be done - + 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 @@ -9,57 +14,62 @@ programs like a compiler, linker and shell to build the new system. Normally all the required tools are available if you selected development as one of the options when you installed your distribution. -In you will first create a new +In 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 you download -all the packages and patches needed to build an LFS system, and store them on -the new file system. In you set up a good +and installed. Then in you download all the +packages and patches needed to build an LFS system, and store them on the new +file system. In you set up a good environment to work in. - then discusses the installation -of a number of packages that form the basic development suite used to build the -actual system in . + then discusses the installation of a number +of packages that will form the basic development suite (or toolchain) which is +used to build the actual system in . Some of these +packages are needed to resolve circular dependencies -- for example, to compile +a compiler you need a compiler. -The first thing to be done in -is build a first pass of the toolchain, consisting 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 (thus making it -in theory possible to skip the second passes). The second thing to do is build -Glibc, the C library. Glibc will be compiled by the just-built toolchain -programs. The third thing to do is build a second pass of the toolchain, this -time linking it dynamically against the newly built Glibc. The remaining packages are all built using this second -pass toolchain and are 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. +The first thing to be done in 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 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. You may be thinking that this seems like a lot of work, just to get away from my host distribution. Well, a full technical explanation -is provided at the start of , -including some notes on the differences between statically and dynamically -linked programs. +is provided at the start of , including some notes +on the differences between statically and dynamically linked programs. -In your real LFS system will be -built. The chroot (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 chrooting 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. +In your real LFS system will be built. The +chroot (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 chrooting 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. To finish the installation, the bootscripts are set up in , the kernel and bootloader are set up in -, and -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. +, and 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. -This is the process in a nutshell. Detailed information on all the steps -taken is given in the chapters and sections as you progress through them. If -something isn't completely clear now, don't worry, everything will fall into -place soon. +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. + +Please read carefully as it explains + a few important things you should be aware of before you begin to work through + and beyond. -- cgit v1.2.3-54-g00ecf