Details on this package are located in Section 10.5.2, “Contents of Linux-Headers.”
Copyright © 2005–2008 Jim Gifford & Ryan Oliver
Copyright © 2005-2008, Jim Gifford & Ryan Oliver
All rights reserved.
This material may be distributed only subject to the terms and conditions set forth in the Open Publication License v1.0 or later (the latest version is presently available at http://www.opencontent.org/openpub/).
Linux® is a registered trademark of Linus Torvalds.
This book is based on the "Linux From Scratch" book, that was released under the following license:
Copyright (c) 1999–2006, Gerard Beekmans
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions in any form must retain the above copyright notice, this list of conditions and the following disclaimer
Neither the name of “Linux From Scratch” nor the names of its contributors may be used to endorse or promote products derived from this material without specific prior written permission
Any material derived from Linux From Scratch must contain a reference to the “Linux From Scratch” project
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The Linux From Scratch Project has seen many changes in the few years of its existence. I personally became involved with the project in 1999, around the time of the 2.x releases. At that time, the build process was to create static binaries with the host system, then chroot and build the final binaries on top of the static ones.
Later came the use of the /static directory to hold the initial static builds, keeping them separated from the final system, then the PureLFS process developed by Ryan Oliver and Greg Schafer, introducing a new toolchain build process that divorces even our initial builds from the host. Finally, LFS 6 bought Linux Kernel 2.6, the udev dynamic device structure, sanitized kernel headers, and other improvements to the Linux From Scratch system.
The one "flaw" in LFS is that it has always been based on an x86 class processor. With the advent of the Athlon 64 and Intel EM64T processors, the x86-only LFS is no longer ideal. Throughout this time, Ryan Oliver developed and documented a process by which you could build Linux for any system and from any system, by use of cross-compilation techniques. Thus, the Cross-Compiled LFS (CLFS) was born.
CLFS follows the same guiding principles the LFS project has always followed, e.g., knowing your system inside and out by virtue of having built the system yourself. Additionally, during a CLFS build, you will learn advanced techniques such as cross-build toolchains, multilib support (32 & 64-bit libraries side-by-side), alternative architectures such as Sparc, MIPS, and Alpha, and much more.
We hope you enjoy building your own CLFS system, and the benefits that come from a system tailored to your needs.
--
Jeremy Utley, CLFS 1.x Release Manager (Page Author)
Jim Gifford, CLFS Project Co-leader
Ryan Oliver, CLFS Project Co-leader
Joe Ciccone, Justin Knierim, Chris Staub, Matt Darcy, Ken Moffat,
Manuel Canales Esparcia, and Nathan Coulson - CLFS Developers
There are many reasons why somebody would want to read this book. The principal reason is to install a Linux system from the source code. A question many people raise is, “why go through all the hassle of manually building a Linux system from scratch when you can just download and install an existing one?” That is a good question and is the impetus for this section of the book.
One important reason for the existence of CLFS is to help people understand how a Linux system works. Building an CLFS system helps demonstrate what makes Linux tick, and how things work together and depend on each other. One of the best things this learning experience provides is the ability to customize Linux to your own tastes and needs.
A key benefit of CLFS is that it allows users to have more control over their system without any reliance on a Linux implementation designed by someone else. With CLFS, you are in the driver's seat and dictate every aspect of the system, such as the directory layout and bootscript setup. You also dictate where, why, and how programs are installed.
Another benefit of CLFS is the ability to create a very compact Linux system. When installing a regular distribution, one is often forced to include several programs which are probably never used. These programs waste disk space or CPU cycles. It is not difficult to build an CLFS system of less than 100 megabytes (MB), which is substantially smaller than the majority of existing installations. Does this still sound like a lot of space? A few of us have been working on creating a very small embedded CLFS system. We successfully built a system that was specialized to run the Apache web server with approximately 8MB of disk space used. Further stripping could bring this down to 5 MB or less. Try that with a regular distribution! This is only one of the many benefits of designing your own Linux implementation.
We could compare Linux distributions to a hamburger purchased at a fast-food restaurant—you have no idea what might be in what you are eating. CLFS, on the other hand, does not give you a hamburger. Rather, CLFS provides the recipe to make the exact hamburger desired. This allows users to review the recipe, omit unwanted ingredients, and add your own ingredients to enhance the flavor of the burger. When you are satisfied with the recipe, move on to preparing it. It can be made to exact specifications—broil it, bake it, deep-fry it, or barbecue it.
Another analogy that we can use is that of comparing CLFS with a finished house. CLFS provides the skeletal plan of a house, but it is up to you to build it. CLFS maintains the freedom to adjust plans throughout the process, customizing it to the needs and preferences of the user.
Security is an additional advantage of a custom built Linux system. By compiling the entire system from source code, you are empowered to audit everything and apply all the security patches desired. It is no longer necessary to wait for somebody else to compile binary packages that fix a security hole. Unless you examine the patch and implement it yourself, you have no guarantee that the new binary package was built correctly and adequately fixes the problem.
The goal of Cross Linux From Scratch is to build a complete and usable foundation-level system. Readers who do not wish to build their own Linux system from scratch may not benefit from the information in this book. If you only want to know what happens while the computer boots, we recommend the “From Power Up To Bash Prompt” HOWTO located at http://axiom.anu.edu.au/~okeefe/p2b/ or on The Linux Documentation Project's (TLDP) website at http://www.tldp.org/HOWTO/From-PowerUp-To-Bash-Prompt-HOWTO.html. The HOWTO builds a system which is similar to that of this book, but it focuses strictly on creating a system capable of booting to a BASH prompt. Consider your objective. If you wish to build a Linux system and learn along the way, this book is your best choice.
There are too many good reasons to build your own CLFS system to list them all here. This section is only the tip of the iceberg. As you continue in your CLFS experience, you will find the power that information and knowledge truly bring.
Building a CLFS system is not a simple task. It requires a certain level of existing knowledge of Unix system administration in order to resolve problems, and correctly execute the commands listed. In particular, as an absolute minimum, the reader should already have the ability to use the command line (shell) to copy or move files and directories, list directory and file contents, and change the current directory. It is also expected that the reader has a reasonable knowledge of using and installing Linux software. A basic knowledge of the architectures being used in the Cross LFS process and the host operating systems in use is also required.
Because the CLFS book assumes at least this basic level of skill, the various CLFS support forums are unlikely to be able to provide you with much assistance. Your questions regarding such basic knowledge will likely go unanswered, or you will be referred to the CLFS essential pre-reading list.
Before building a CLFS system, we recommend reading the following HOWTOs:
Software-Building-HOWTO http://www.tldp.org/HOWTO/Software-Building-HOWTO.html
This is a comprehensive guide to building and installing “generic” Unix software distributions under Linux.
The Linux Users' Guide http://www.linuxhq.com/guides/LUG/guide.html
This guide covers the usage of assorted Linux software.
The Essential Pre-Reading Hint http://hints.cross-lfs.org/essential_prereading.txt
This is a hint written specifically for users new to Linux. It includes a list of links to excellent sources of information on a wide range of topics. Anyone attempting to install CLFS should have an understanding of many of the topics in this hint.
You should be able to build a CLFS system from just about any Unix-type operating system. Your host system should have the following software with the minimum versions indicated. Also note that many distributions will place software headers into separate packages, often in the form of “[package-name]-devel” or “[package-name]-dev”. Be sure to install those if your distribution provides them.
Bash-2.05a
Binutils-2.12 (Versions greater than 2.18 are not recommended as they have not been tested)
Bison-1.875
Bzip2-1.0.2
Coreutils-5.0 (or Sh-Utils-2.0, Textutils-2.0, and Fileutils-4.1)
Diffutils-2.8
Findutils-4.1.20
Gawk-3.0
Gcc-2.95.3 (Versions greater than 4.2.4 are not recommended as they have not been tested)
Glibc-2.2.5 (Versions greater than 2.7 are not recommended as they have not been tested)
Grep-2.5
Gzip-1.2.4
Make-3.79.1
Ncurses-5.3
Patch-2.5.4
Sed-3.0.2
Tar-1.14
Texinfo-4.4
To see whether your host system has all the appropriate versions, run the following:
cat > version-check.sh << "EOF"
#!/bin/bash
# Simple script to list version numbers of critical development tools
bash --version | head -n1 | cut -d" " -f2-4
echo -n "Binutils: "; ld --version | head -n1 | cut -d" " -f3-
bison --version | head -n1
bzip2 --version 2>&1 < /dev/null | head -n1 | cut -d" " -f1,6-
echo -n "Coreutils: "; chown --version | head -n1 | cut -d")" -f2
diff --version | head -n1
find --version | head -n1
gawk --version | head -n1
gcc --version | head -n1
/lib/libc.so.6 | head -n1 | cut -d" " -f1-7
grep --version | head -n1
gzip --version | head -n1
make --version | head -n1
tic -V
patch --version | head -n1
sed --version | head -n1
tar --version | head -n1
makeinfo --version | head -n1
EOF
bash version-check.sh
To make things easier to follow, there are a few typographical conventions used throughout this book. This section contains some examples of the typographical format found throughout Cross-Compiled Linux From Scratch.
./configure --prefix=/usr
This form of text is designed to be typed exactly as seen unless otherwise noted in the surrounding text. It is also used in the explanation sections to identify which of the commands is being referenced.
install-info: unknown option '--dir-file=/mnt/clfs/usr/info/dir'
This form of text (fixed-width text) shows screen output,
probably as the result of commands issued. This format is also
used to show filenames, such as /etc/ld.so.conf
.
Emphasis
This form of text is used for several purposes in the book. Its main purpose is to emphasize important points or items.
This format is used for hyperlinks, both within the CLFS community and to external pages. It includes HOWTOs, download locations, and websites.
cat > ${CLFS}/etc/group << "EOF"
root:x:0:
bin:x:1:
......
EOF
This format is used when creating configuration files. The first
command tells the system to create the file ${CLFS}/etc/group
from whatever is typed on the
following lines until the sequence end of file (EOF) is
encountered. Therefore, this entire section is generally typed as
seen.
[REPLACED TEXT]
This format is used to encapsulate text that is not to be typed as seen or copied-and-pasted.
passwd(5)
This format is used to refer to a specific manual page
(hereinafter referred to simply as a “man” page). The number inside parentheses
indicates a specific section inside of man. For example, passwd has two man pages. Per
CLFS installation instructions, those two man pages will be
located at /usr/share/man/man1/passwd.1
and /usr/share/man/man5/passwd.5
. Both man pages
have different information in them. When the book uses
passwd(5)
it is specifically
referring to /usr/share/man/man5/passwd.5
. man passwd will print the first
man page it finds that matches “passwd”, which will be /usr/share/man/man1/passwd.1
. For this example,
you will need to run man 5
passwd in order to read the specific page being
referred to. It should be noted that most man pages do not have
duplicate page names in different sections. Therefore,
man [program name]
is
generally sufficient.
This book is divided into the following parts.
Part I explains a few important notes on how to proceed with the Cross-LFS installation. This section also provides meta-information about the book.
Part II describes how to prepare for the building process—making a partition and downloading the packages.
Part III shows you how to make a set of Cross-Compiler tools. These tools can run on your host system but allow you to build packages that will run on your target system.
Part IV explains how to build a tool chain designed to operate on your target system. These are the tools that will allow you to build a working system on your target computer.
Part V guides the reader through the building of the CLFS system—compiling and installing all the packages one by one, setting up the boot scripts, and installing the kernel. The resulting Linux system is the foundation on which other software can be built to expand the system as desired. At the end of this book, there is an easy to use reference listing all of the programs, libraries, and important files that have been installed.
The appendices contain information that doesn't really fit anywhere else in the book. Appendix A contains definitions of acronyms and terms used in the book; Appendix B gives acknowledgments to people who have helped work on the CLFS project and website; Appendix C and D have information about package dependencies and the the build order. Some architectures may have additional appendices for arch-specific issues.
The software used to create a CLFS system is constantly being updated and enhanced. Security warnings and bug fixes may become available after the CLFS book has been released. Some host systems may also have problems building CLFS. To check whether the package versions or instructions in this release of CLFS need any modifications to accommodate security vulnerabilities, other bug fixes, or host-specific issues, please visit http://trac.cross-lfs.org/clfs/errata/1.1.0/ before proceeding with your build. You should note any changes shown and apply them to the relevant section of the book as you progress with building the CLFS system.
The CLFS team would like to acknowledge people who have assisted in making the book what it is today.
Our Leaders:
Ryan Oliver - Build Process Developer.
Jim Gifford - Lead Developer.
Jeremy Utley - Release Manager 1.x Series.
Our CLFS Team:
Joe Ciccone - Alpha, MIPS, Sparc builds.
Nathan Coulson - Bootscripts.
Matt Darcy - x86, X86_64, and Sparc builds.
Manuel Canales Esparcia - Book XML.
Karen McGuiness - Proofreader.
Jeremy Huntwork - PowerPC, x86, Sparc builds.
Justin Knierim - Website Architect.
Ken Moffat - PowerPC and X86_64 builds. Developer of Pure 64 Hint.
Alexander E. Patrakov - Udev/Hotplug Integration
Chris Staub - x86 builds. Leader of Quality Control.
Outside the Development Team
Jürg Billeter - Testing and assisting in the development of the Linux Headers Package
Richard Downing - Testing, typo, and content fixes.
Peter Ennis - Typo and content fixes.
Tony Morgan - Typo and content fixes.
The CLFS team would also like to acknowledge contributions of people from clfs-dev@lists.cross-lfs.org and associated mailing lists who have provided valuable technical and editorial corrections while testing the Cross-LFS book.
G. Moko - Text updates and Typos
Maxim Osipov - MIPS Testing.
Doug Ronne - Various x86_64 fixes.
William Zhou - Text updates and Typos
Theo Schneider - Testing of the Linux Headers Package
Thank you all for your support.
The CLFS system will be built by using a previously installed Unix system or Linux distribution (such as Debian, Fedora, Mandriva, SUSE, or Ubuntu). This existing system (the host) will be used as a starting point to provide necessary programs, including a compiler, linker, and shell, to build the new system. Select the “development” option during the distribution installation to be able to access these tools.
As an alternative to installing an entire separate distribution onto your machine, you may wish to use the Linux From Scratch LiveCD. This CD works well as a host system, providing all the tools you need to successfully follow the instructions in this book. It does also contain source packages and patches for the LFS book, and a copy of the LFS book, but not the needed packages or book for CLFS. You can still use the CD for building CLFS, but you will need to download the packages, patches and book separately. You can also look at http://hints.cross-lfs.org/lfscd-remastering-howto.txt for infomation on building your own CD, replacing the LFS packages and book with those for CLFS. Once you have the CD, no network connection or additional downloads are necessary. For more information about the LFS LiveCD or to download a copy, visit http://www.linuxfromscratch.org/livecd/.
Preparing a New Partition of this book describes how to create a new Linux native partition and file system, the place where the new CLFS system will be compiled and installed. Packages and Patches explains which packages and patches need to be downloaded to build a CLFS system and how to store them on the new file system. Final Preparations discusses the setup for an appropriate working environment. Please read Final Preparations carefully as it explains several important issues the developer should be aware of before beginning to work through Constructing Cross-Compile Tools and beyond.
Constructing Cross-Compile Tools explains the installation of cross-compile tools which will be built on the host but be able to compile programs that run on the target machine. These cross-compile tools will be used to create a temporary, minimal system that will be the basis for building the final CLFS system. Some of these packages are needed to resolve circular dependencies—for example, to compile a compiler, you need a compiler.
The process of building cross-compile tools first involves building and installing all the necessary tools to create a build system for the target machine. With these cross-compiled tools, we eliminate any dependencies on the toolchain from our host distro.
After we build our “Cross-Tools”, we start building a very minimal working system in /tools. This minimal system will be built using the cross-toolchain in /cross-tools.
In Installing Basic System Software, the full CLFS system is built. Depending on the system you are cross-compiling for, you will either boot the minimal temp-system on the target machine, or chroot into it.
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 CLFS partition. This is very similar to rebooting and instructing the kernel to mount the CLFS partition as the root partition. The major advantage is that “chrooting” allows the builder to continue using the host while CLFS is being built. While waiting for package compilation to complete, a user can switch to a different virtual console (VC) or X desktop and continue using the computer as normal.
Some systems cannot be built by chrooting so they must be booted instead. Generally, if you building for a different arch than the host system, you must reboot because the kernel will likely not support the target machine. Booting involves installing a few additional packages that are needed for bootup, installing bootscripts, and building a miminal kernel. We also describe some alternative booting methods in Section 7.20, “What to do next”
To finish the installation, the CLFS-Bootscripts are set up in Setting Up System Bootscripts, and the kernel and boot loader are set up in Making the CLFS System Bootable. The End contains information on furthering the CLFS experience beyond this book. After the steps in this book have been implemented, the computer will be ready to reboot into the new CLFS system.
This is the process in a nutshell. Detailed information on each step is discussed in the following chapters and package descriptions. Items that may seem complicated will be clarified, and everything will fall into place as the reader embarks on the CLFS adventure.
This is version 1.1.0 of the Cross-Compiled Linux From Scratch book, dated September 14, 2008. If this book is more than six months old, a newer and better version is probably already available. To find out, please check one of the mirrors via http://trac.cross-lfs.org/.
Below is a list of detailed changes made since the previous release of the book.
Changelog Entries:
September 13, 2008
[jciccone] - Checked and updated all download locations.
September 7, 2008
[jciccone] - A lot of text changes.
August 27, 2008
[jciccone] - Add Texinfo to the list of Host System Requirements.
August 24, 2008
[jciccone] - Update the paths to ld.so when configuring Glibc for each arch.
July 13, 2008
[jciccone] - Add a page right before Entering the Chroot Enviornment. This page covers the problem of building a 32bit system from a 64bit host or building a older 32bit system from another newer 32bit system.
July 12, 2008
[jciccone] - Drop the minix tools from the chroot Util-Linux-NG build.
July 11, 2008
[ken] - Add a patch to address known perl vulnerabilities.
July 7, 2008
[jciccone] - Change the command that creates the clfs user to not include -k /dev/null. Newer versions of Shadow (4.1.2) apparently any argument passed to -k to be a directory.
July 7, 2008
[jciccone] - Fix a omission in the Udev lib64 patch. Thanks to AcidPoison for catching this and reporting it in Trac.
July 6, 2008
[jciccone] - Now that shadow doesn't provide any libraries we only need to build it once on multilib.
June 28, 2008
[jciccone] - Downgraded the Vim Branch Update patch back to -2 from -3.
[jciccone] - Remove the commands that relocate the Shadow libraries as they are not provided in newer versions of shadow. Also only build 64bit, since there are no libraries anymore.
[jciccone] - Link /tools/bin/echo to /bin/echo foe one of the Glibc tests.
[jciccone] - Updated GCC to 4.2.4.
June 28, 2008
[jciccone] - Fixed the Glibc i586 chk patch entity.
[jciccone] - Updated Tar to 1.20.
[jciccone] - Updated Udev to 124.
[jciccone] - Updated the Ncurses Branch Update patch to -3/
[jciccone] - Add a config.cache entry to Coreutils so that the df program will be built
[jciccone] - Fixed descriptions for lib64= in procps on the various multilib pages.
[jciccone] - Corrected the entities for the lilo x86_64 cross compile patch.
[jciccone] - Added a patch to perl so it wont include asm/page.h.
[jciccone] - Updated the Vim Branch Update patch to -3.
[jciccone] - Updated Shadow to 4.1.2.
[jciccone] - Fixed GCC Posix patch MD5SUM.
[jciccone] - Fixed Inetutils MD5SUM.
[jciccone] - Updated Util-Linux-NG to 2.14.
[jciccone] - Updated the Util-Linux-NG homepage link.
[jciccone] - Updated Man-Pages to 3.01.
[jciccone] - Updated the Bash Fixes patch to -8.
June 17, 2008
[Ken] - Fix all known kernel vulnerabilities by upgrading to 2.6.24.7 plus a patch extracted from debian for the more recent fixes.
June 7, 2008
[Chris] - Updated dependency info for several packages.
Date
[jciccone] - Updated Flex to 2.5.35. This update fixes numerous compilation issues against 2.5.34.
February 12, 2008
[ken] - Added cs_CZ.UTF-8 locale for grep's fmbtest.sh test.
Frburary 3, 2008
[jciccone] - Updated the Kernel to 2.6.24.
Feburary 2, 2008
[jciccone] - Updated Man-Pages to 2.77.
[jciccone] - Updated Libtool to 1.5.26.
[jciccone] - Updated Findutils to 4.2.32.
[jciccone] - Updated Automake to 1.10.1.
[jciccone] - Updated the bootscripts to 1.1-pre10. These use udevadm instead of the individual udevcontrol, udevtrigger, and udevsettle programs. Which are currently symlinked to udevadm.
January 20, 2008
[Bigdissaved] - Changed the minimum ${CLFS} size from 1.5Gb to 2.5Gb. Thanks to Copper for seeing this
January 19, 2008
[jciccone] - Update the Kernel to 2.6.23.14.
January 19, 2008
[jciccone] - Updated Man-Pages to 2.76.
[jciccone] - Updated Util-Linux-NG to 2.13.1.
[jciccone] - Updated Less to 418.
January 14, 2008
[ken] - Add patch for man pages in module-init-tools.
January 13, 2008
[jciccone] - Updated the Kernel to 2.6.23.13.
January 6, 2008
[jciccone] - Updated File to 4.23.
[ken] - Updated Glibc branch update patch to 1A, so that ppc and ppc64 build again.
January 2, 2008
[jciccone] - Updated E2fsprogs to 1.40.4.
Janurary 1, 2007
[jciccone] - Updated Shadow to 4.1.0.
December 29, 2007
[ken] - Make the current Module-Init-Tools testsuite run, update the instructions because distclean is no longer useful, and comment on the DOCBOOKTOMAN parameter.
December 23, 2007
[jciccone] - Added a config.cache entry to Gettext to resolve some errors.
December 19, 2007
[jciccone] - Updated Util-Linux-NG to 2.13.0.1.
[jciccone] - Updated Various Branch Update Patches.
[jciccone] - Updated Udev to 118.
[jciccone] - Updated Psmisc to 22.6.
[jciccone] - Updated Module Init Tools to 3.4.
[jciccone] - Updated Man-Pages to 2.73.
[jciccone] - Updated the Kernel to 2.6.23.12.
[jciccone] - Updated Less to 416.
December 16, 2007
[jciccone] - Updated Gettext to 0.17.
[jciccone] - Updated e2fsprogs to 1.40.3.
[jciccone] - Updated Flex to 2.5.34.
[jciccone] - Updated the Kernel to 2.6.23.11.
[jciccone] - Updated the bootscripts to 1.1-pre9.
December 10, 2007
[jciccone] - Added --disable-makeinstall-chown to util-linux-ng in the boot section.
November 27, 2007
[jciccone] - Updated the bootscripts to 1.1-pre8.
October 30, 2007
[jim] - Updated to TCL 8.4.16.
[jim] - Updated to Man-Pages 2.67.
[jim] - Replaced Shadow Patch with better patch.
October 29, 2007
[jim] - Updated Binutils 2.18 Branch Update Patch.
[jim] - Updated Vim 7.1 Branch Update Patch.
[jim] - Added Ncurses 5.6 Branch Update Patch.
[jim] - Updated to Gawk 3.1.6.
[jim] - Updated to Shadow 4.0.18.2.
[jim] - Added Updated Useradd Fix Patch to Shadow 4.0.18.2.
October 26, 2007
[jim] - Added Binutils 2.18 Branch Update Patch.
[jim] - Added GCC 4.2.2 Branch Update Patch.
[jim] - Added Glibc 2.7 Branch Update Patch.
October 25, 2007
[jim] - Updated the bootscripts to 1.1-pre7.
[jim] - Updated to Glibc 2.7.
[jim] - Updated Bootscripts build to make sure the udev devices get created correctly in boot section.
October 16, 2007
[jim] - Updated the bootscripts to 1.1-pre6. Combined with cblfs bootscripts, all bootscripts in one package.
[jim] - Updated to Linux 2.6.23.1.
[jim] - Removed Linux-Headers Package.
[jim] - Updated to GCC 4.2.2.
[jim] - Updated to Tar 1.19.
[jim] - Updated to Texinfo 4.11.
[jim] - Updated to Less 409.
[jim] - Updated to Udev 116.
[jim] - Added patch to correct the detction of texinfo in binutils.
[jim] - Updated to IPRoute2 2.6.23.
October 13, 2007
[jciccone] - Updated the bootscripts to 1.1-pre5. The Makefile now creates the static nodes that the udev Makefile used to.
[jim] - Updated the boot section Util-Linux-NG Build. Fixes issues where files were missing during bootup and the ability to login.
September 24, 2007
[Chris] - More dependency updates for several packages.
September 23, 2007
[Chris] - Updates to dependency info for several packages.
September 12, 2007
[Chris] - Added more new programs to Util-Linux-Ng installed programs list.
September 11, 2007
[Chris] - Updated list of installed programs for Util-Linux-ng.
[jim] - Updated CLFS Bootscripts to 1.1-pre4.
September 10, 2007
[Chris] - Added needed mkdir command to IPRoute2 instructions.
[Chris] - Fixed descriptive text in testsuite-tools introduction page. Reported by gomoko (ticket #118).
September 09, 2007
[jciccone] - Build a PIC libfl.a with Flex.
[jim] - Updated Util-Linux-ng in Boot Section, to cross-compile.
September 03, 2007
[jim] - Updated Udev to 115. This change also removed udev-cross-lfs package since our rules are the same as base ones installed.
[jim] - Updated Grep to 2.5.3.
[jim] - Updated Man-Pages to 2.64.
[jim] - Updated TCL to 8.4.15.
[jim] - Updated to Linux 2.6.22.6.
[jim] - Updated to Linux Headers 2.6.22.6-09032007.
[jim] - Updated Less to 406.
[jim] - Updated Sysklogd to 1.5.
[jim] - Updated Kbd to 1.13.
[jim] - Updated IPRoute2 to 2.6.22-070710.
[jim] - Updated Shadow Patch for more fixes. Man Page Typos, buffer overflows, useradd -G fixes, better name support, and the previous useradd fix.
[jim] - Updated Bash 3.2 Patch to -6.
[jim] - Updated Readline 5.2 Patch to -3.
[jim] - Updated Vim 3.1 Patch to -3.
September 02, 2007
[jim] - Updated Util-linux-ng to 2.13.
[jim] - Updated Tree to 1.5.1.1.
[jciccone] - Updated Glibc to 2.6.1.
[jim] - Updated Binutils to 2.18.
August 05, 2007
[jciccone] - Updated the bash config.cache to contain all of the differences between a cross-compiled and a native build.
July 23, 2007
[jciccone] - Updated Texinfo to 4.9.
[jciccone] - Updated E2fsprogs to 1.40.2.
[jciccone] - Updated M4 to 1.4.10.
[jciccone] - Updated Tar to 1.18.
[jciccone] - Updated Libtool to 1.5.24.
[jciccone] - Updated the Man Pages to 2.63.
July 22, 2007
[jciccone] - Updated GCC to 4.2.1.
July 20, 2007
[ken] - Make coreutils build in temp-system when the host cannot run the target programs.
July 1, 2007
[jciccone] - Updated the download location for the Man Pages package.
June 23, 2007
[jciccone] - Updated to Glibc 2.6. This includes adding a sed to Coreutils and Gzip to rename their internal implementations of futimens which are incompatible with the implementation provided by Glibc.
June 18, 2007
[jciccone] - Updated to Tar 1.17.
June 17, 2007
[jciccone] - Updated to Vim 7.1.
[jciccone] - Updated to Findutils 4.2.31.
[jciccone] - Updated to File 4.21.
[jciccone] - Updated to Less 403.
[jciccone] - Updated to Man Pages 2.57.
June 16, 2007
[Chris] - Removed creation of config.cache from temp-system Coreutils, as it no longer looks for setvbuf.
May 19, 2007
[jciccone] - Added a patch to Perl that accounts
for a change in GCC 4.2.0. The patch causes
makedepend.sh to also remove <command-line>
as well as
<command line>
.
May 18, 2007
[jciccone] - Updated to GCC 4.2.0.
April 30, 2007
[jciccone] - Updated to Man Pages 2.46.
April 27, 2007
[jhuntwork] - We don't use the uname patch for temp-system Coreutils. No need to 'touch man/uname.1'.
April 24, 2007
[jciccone] - Updated to Psmisc 22.5.
April 20, 2007
[jciccone] - Updated to Gzip 1.3.12.
[jciccone] - Updated to Psmisc 22.4.
[jciccone] - Updated to Man Pages 2.44.
[jciccone] - Updated to M4 1.4.9.
[jciccone] - Updated to Coreutils 6.9.
April 10, 2007
[Chris] - Updated Gzip's list of installed programs - compress is no longer installed, and gunzip, uncompress, and zcat are now bash scripts rather than links.
February 25, 2007
[jim] - Updated to Linux 2.6.20.1.
[jim] - Updated to Linux Headers 2.6.20.1-02252007.
February 17, 2007
[Chris] - Moved the build of the File package in cross-tools to the beginning of the chapter.
[jim] - Updated to Gzip 1.3.11.
February 16, 2007
[Chris] - Changed the wording in the "Build Variables" page to make it clearer.
[Chris] - Added command to Udev installation to remove Udev rules it installs.
[Chris] - Removed Ncurses patch for buggy versions of Bash from from the final-system build (it's still in the temp-system).
[Chris] - Removed unneeded /tools/bin/cc symlink.
February 15, 2007
[jim] - Fix a building of Ncurses when an unpatched version of Bash 3.x is used.
February 14, 2007
[jim] - Updated to GCC 4.1.2.
February 5, 2007
[jim] - Updated to Automake 1.10.
February 4, 2007
[jim] - Updated to Linux 2.6.20.
[jim] - Updated to Linux Headers 2.6.20-02042007.
[jim] - Updated to Udev 105.
January 23, 2007
[jim] - Updated to Linux Headers 2.6.19.2-01232007.
[jim] - Update to Glibc Branch Update Patch.
January 15, 2007
[jim] - Updated to Linux 2.6.19.2.
[jim] - Updated to Linux Headers 2.6.19.2-01152007.
[jim] - Updated to Tree 1.5.1.
[jim] - Updated to Udev 104.
[jim] - Updated to Udev Rules 1.1-pre4.
[Chris] - Removed obsolete note from bzip2 instructions about performing rm /usr/bin/bz*.
January 12, 2007
[jim] - Update to Glibc Branch Update Patch.
[jim] - Update to Binutils Branch Update Patch.
January 7, 2007
[jim] - Updated to Bzip2 1.0.4.
December 23, 2006
[jciccone] - Updated to Ncurses 5.6.
December 15, 2006
[jim] - Updated to Gzip 1.3.9.
[jim] - Updated to IPRoute2 2.6.19-061214.
December 13, 2006
[jim] - Added File to Cross-tools.
December 12, 2006
[jim] - Updated to Linux 2.6.19.1.
[jim] - Updated to Linux Headers 2.6.19.1-12122006.
[jim] - Added Readline Upstream Patch.
[jim] - Update Bash Upstream Patch.
[jim] - Updated to File 4.19.
December 10, 2006
[jim] - Updated to Gzip 1.3.8.
December 9, 2006
[jim] - Updated to Tar 1.16.1.
December 7, 2006
[jim] - Updated to Gzip 1.3.7.
[jim] - Updated to Coreutils 6.7.
[jim] - Reverting sysroot changes.
December 1, 2006
[jim] - Updated to Man-Pages 2.43.
[jim] - Removed MINOR patch and replaced it with a more complete upstream patch will all current updates to the 2.5 branch of glibc.
[jim] - Added Binutils Branch Update Patch.
[jim] - Reverted change in gettext build in temp-system.
[jim] - Updated to Coreutils 6.7.
November 29, 2006
[jim] - Updated to Linux Headers 2.6.19-11302006.
[jim] - Updated to Udev Rules 1.1-pre3.
November 29, 2006
[jim] - Updated to Linux 2.6.19.
[jim] - Updated to Linux Headers 2.6.19-11292006.
November 27, 2006
[jim] - Updated to Gettext 0.16.1.
November 26, 2006
[jim] - Updated to Man-Pages 2.42.
[jim] - Updated to Gzip 1.3.6.
November 25, 2006
[jim] - Updated to Findutils 4.2.29.
November 23, 2006
[Chris] - Added /bin/rm to essential symlinks - e2fsprogs testsuite hard-codes the location to that binary.
November 22, 2006
[jim] - Updated to Coreutils 6.6.
[jim] - Updated to Man 1.6e.
November 20, 2006
[jim] - Updated to Coreutils 6.5.
[jim] - Added Patch for Coreutils 6.5 ls segfault.
[jim] - Updated to M4 1.4.8.
[jim] - Updated to Linux 2.6.18.3.
[jim] - Updated to Linux Headers 2.6.18.3-11202006.
November 17, 2006
[jim] - Updated to Autoconf 2.61.
November 15, 2006
[jim] - Updated to IANA-Etc 2.20.
November 14, 2006
[jim] - Change to E2FSProgs, does not pick up the CC or LD variables.
November 12, 2006
[jim] - Updated to Linux Headers 2.6.18.2-11122006.
[jim] - Bash 3.2 patch updated with upstream fixes 001-005.
November 5, 2006
[jim] - Updated to Linux 2.6.18.2.
[jim] - Updated to Linux Headers 2.6.18.2-11052006.
November 4, 2006
[Chris] - Modified the instructions for disabling the installation of the groups program to account for changes in shadow's Makefile.
November 2, 2006
[jim] - Updated to File 4.18.
October 31, 2006
[jim] - Bash 3.2 patch updated with upstream fixes.
[jim] - Updated to Bootscripts 1.1-pre3.
October 30, 2006
[jim] - Updated to Udev Rules 1.1-pre2.
October 27, 2006
[jim] - Updated to Bootscripts 1.1-pre2.
[jim] - Updated syslog.conf file.
October 26, 2006
[jim] - Updated to Linux-Headers 2.6.18.1-10262006.
[jim] - Updated to Gettext 0.16.
[jim] - The nscd sed is no longer needed to build Glibc 2.5.
October 25, 2006
[Chris] - Updated to Psmisc 22.3.
[Chris] - Updated to Tcl 8.4.14.
[Chris] - Moved e2fsprogs and sed before coreutils, as Coreutils testsuite now requires e2fsprogs.
October 23, 2006
[Chris] - Removed unneeded additions to config.cache for temp-system Tar and Coreutils.
[jim] - Added touch man/uname.1 in temp-system Coreutils to prevent a build failure.
[jim] - Added Patch for a Versioning issue with Glibc 2.5.
October 22, 2006
[jim] - Updated to Linux 2.6.18.1.
[jim] - Updated to Linux Headers 2.6.18.1-10222006.
[jim] - Updated to Coreutils 6.4.
[jim] - Removed out of place udev text in bootscripts Networking.
October 21, 2006
[jim] - Updated to Inetutils 1.5.
[jim] - Updated to IPRoute2 2.6.18-061002.
[jim] - Updated to Tar 1.16.
[jim] - Updated to Udev 103.
[jim] - Updated to Coreutils 6.3.
October 20, 2006
[Chris] - Removed command to add "setvbuf_reversed" to temp-system bash as it is no longer needed with Bash 3.2.
[Chris] - Added command to man instructions to comment out MANPATH /usr/local/man (in addition to /usr/man).
October 15, 2006
[jim] - Updated Bash 3.2 with some unofficial upstream fixes. Thank you Chet Ramey.
October 12, 2006
[jim] - Added patch to fix build issue with Bash 3.2.
[jim] - Updated to Man-Pages 2.41.
[jim] - Updated to Glibc 2.5.
October 11, 2006
[jim] - Updated to Bash 3.2.
[jim] - Updated to Readline 5.2.
[jim] - Updated to Man-Pages 2.40.
[jim] - Updated to Udev 102.
October 4, 2006
[manuel] - Changed book license to the Open Publication License v1.0.
October 1, 2006
[Chris] - Removed obsolete command from Tcl instructions, as the issue it fixes has been fixed in the latest Tcl version.
September 29, 2006
[jim] - Updated to Linux Headers to 2.6.18-09302006.
[jim] - New patch for util-linux, replaces GCC 4 Fixes, the new patches fixes the same issues, and removes the use of syscalls. Syscalls were removed the unistd.h during santization.
September 28, 2006
[jim] - Added patch for Util-Linux to fix build issues due to headers change in the kernel.
[jim] - Updated to Texinfo 4.8a.
September 25, 2006
[jim] - Updated Bootscripts to 1.1-pre1. Adding in the boot logging feature.
[jim] - Updated to Udev 100.
[jim] - Updated Udev Rules for Udev 100.
[jim] - Updated to M4 1.4.7.
[jim] - Updated to Linux to 2.6.18.
[jim] - Updated to Linux Headers to 2.6.18-09252006.
[jim] - Udev library libvolume_id is used by HAL, which makes us change our build to a multilib build of udev libaries only for 32 and N32.
September 18, 2006
[jim] - Updated Bison to a multilib build in all support architectures.
August 28, 2006
[jim] - Updated to Gettext 0.15.
[jim] - Updated to Shadow 4.0.18.1.
[jim] - Updated to Coreutils 5.97.
[jim] - Updated to Procps 3.2.7.
[jim] - Updated to Man-Pages 2.39.
[jim] - Updated to Autoconf 2.60.
[jim] - Updated to TCL 8.4.13.
[jim] - Updated to M4 1.4.6.
[jim] - Updated to Findutils 4.2.28.
[jim] - Updated to Coreutils Uname Patch -2, which supports all architectures.
[jim] - Updated to Vim Patch -10, which contains upstream fixes.
[jim] - Updated to Udev 098 and udev-cross-lfs to 1.1-08272006 rules.
August 28, 2006
[jim] - Changelog restarted, see the 1.0.0 book for the old changelog.
Branch Synced from the Release of LFS 6.0 on February 23rd, 2005
Below is a list of changes specifics for this architecture made since the previous release of the book. For general changes see Master Changelog,
Changelog Entries:
August 24, 2008
[jciccone] - Added Ratrophy's memcpy patch to inetutils to resolve the Bus Error problem with ping on sparc64.
June 02, 2008
[ken] - create libstdc++.so symlinks in /usr/lib64 so that the glibc and ld tests all link, and delete them safely before installing binutils.
[ken] - ensure binutils does not install libiberty.a into /usr/lib64.
February 3, 2008
[jciccone] - Added a patch to the kernel that includes spitfire.h in elf.h outside of kernel space. This fixed a compilation error with elftoaout.
November 2, 2006
[jim] - Updated Silo for 2.6.18.1 headers.
October 24, 2006
[jim] - Fixed glibc in Sparc builds, add patch to fix missing symbols.
September 11, 2006
[jim] - Updated to Silo 1.4.13.
August 28, 2006
[jim] - Changelog restarted, see the 1.0.0 book for the old changelog.
If during the building of the CLFS system you encounter any errors, have any questions, or think there is a typo in the book, please start by consulting the Frequently Asked Questions (FAQ) that is located at http://trac.cross-lfs.org/wiki/faq.
The cross-lfs.org
server hosts a
number of mailing lists used for the development of the CLFS
project. These lists include the main development and support
lists, among others. If the FAQ does not contain your answer,
you can search the CLFS lists via The Mail Archive http://www.mail-archive.com.
You can find the mail lists with the following link:
http://www.mail-archive.com/index.php?hunt=clfs
For information on the different lists, how to subscribe, archive locations, and additional information, visit http://trac.cross-lfs.org/wiki/lists.
Cross-LFS does not maintain it's own News Server, but we do
provide access via gmane.org
http://gmane.org. If you want to
subscribe to the Cross-LFS via a newsreader you can utilize
gmane.org
. You can find the game
search for CLFS with the following link:
Several members of the CLFS community offer assistance on our
community Internet Relay Chat (IRC) network. Before using
this support, please make sure that your question is not
already answered in the CLFS FAQ or the mailing list
archives. You can find the IRC network at chat.freenode.net
. The support channel for
cross-lfs is named #cross-lfs. If you need to show people the
output of your problems, please use
http://pastebin.cross-lfs.org and reference the pastebin URL
when asking your questions.
The CLFS project has a number of world-wide mirrors to make accessing the website and downloading the required packages more convenient. Please visit the CLFS website at http://trac.cross-lfs.org/wiki/mirrors for mirrors of CLFS.
If an issue or a question is encountered while working through this book, check the FAQ page at http://trac.cross-lfs.org/wiki/faq#generalfaq. Questions are often already answered there. If your question is not answered on this page, try to find the source of the problem. The following hint will give you some guidance for troubleshooting: http://hints.cross-lfs.org/errors.txt.
We also have a wonderful CLFS community that is willing to offer assistance through the mailing lists and IRC (see the Section 1.5, “Resources” section of this book). However, we get several support questions everyday and many of them can be easily answered by going to the FAQ and by searching the mailing lists first. So for us to offer the best assistance possible, you need to do some research on your own first. This allows us to focus on the more unusual support needs. If your searches do not produce a solution, please include all relevant information (mentioned below) in your request for help.
Apart from a brief explanation of the problem being experienced, the essential things to include in any request for help are:
The version of the book being used (in this case 1.1.0)
The host distribution and version being used to create CLFS.
The architecture of the host and target.
The value of the $CLFS_HOST, $CLFS_TARGET, $BUILD32, and $BUILD64 environment variables.
The package or section in which the problem was encountered.
The exact error message or symptom received. See Section 1.6.3, “Compilation Problems” below for an example.
Note whether you have deviated from the book at all. A package version change or even a minor change to any command is considered deviation.
Deviating from this book does not mean that we will not help you. After all, the CLFS project is about personal preference. Be upfront about any changes to the established procedure—this helps us evaluate and determine possible causes of your problem.
If something goes wrong while running the configure script, review
the config.log
file. This file
may contain the errors you encountered during configure. It often logs
errors that may have not been printed to the screen. Include
only the relevant
lines if you need to ask for help.
Both the screen output and the contents of various files are useful in determining the cause of compilation problems. The screen output from the configure script and the make run can be helpful. It is not necessary to include the entire output, but do include enough of the relevant information. Below is an example of the type of information to include from the screen output from make:
gcc -DALIASPATH=\"/mnt/clfs/usr/share/locale:.\"
-DLOCALEDIR=\"/mnt/clfs/usr/share/locale\"
-DLIBDIR=\"/mnt/clfs/usr/lib\"
-DINCLUDEDIR=\"/mnt/clfs/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':
/clfs/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 `/clfs/tmp/make-3.79.1'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/clfs/tmp/make-3.79.1'
make: *** [all-recursive-am] Error 2
In this case, many people would just include the bottom section:
make [2]: *** [make] Error 1
This is not enough information to properly diagnose the problem because it only notes that something went wrong, not what went wrong. The entire section, as in the example above, is what should be saved because it includes the command that was executed and the associated error message(s).
An excellent article about asking for help on the Internet is available online at http://catb.org/~esr/faqs/smart-questions.html. Read and follow the hints in this document to increase the likelihood of getting the help you need.
In this chapter, the partition which will host the CLFS system is prepared. We will create the partition itself, create a file system on it, and mount it.
Like most other operating systems, CLFS is usually installed on a dedicated partition. The recommended approach to building a CLFS system is to use an available empty partition or, if you have enough unpartitioned space, to create one. However, if your building for a different architecture you can simply build everything in “/mnt/clfs” and transfer it to your target machine.
A minimal system requires around 2.5 gigabytes (GB). This is enough to store all the source tarballs and compile the packages. The CLFS system itself will not take up this much room. A large portion of this requirement is to provide sufficient free temporary storage. Compiling packages can require a lot of disk space which will be reclaimed after the package is installed. If the CLFS system is intended to be the primary Linux system, additional software will probably be installed which will require additional space (2-10 GB).
Because there is not always enough Random Access Memory (RAM) available for compilation processes, it is a good idea to use a small disk partition as swap space. This is used by the kernel to store seldom-used data and leave more memory available for active processes. The swap partition for an CLFS system can be the same as the one used by the host system, in which case it is not necessary to create another one.
Start a disk partitioning program such as cfdisk or fdisk with a command line
option naming the hard disk on which the new partition will be
created—for example /dev/hda
for the primary Integrated Drive
Electronics (IDE) disk. Create a Linux native partition and a
swap partition, if needed. Please refer to cfdisk(8)
or fdisk(8)
if you do not yet know how to use
the programs.
Remember the designation of the new partition (e.g.,
hda5
). This book will refer to
this as the CLFS partition. Also remember the designation of
the swap partition. These names will be needed later for the
/etc/fstab
file.
On a Sparc system we have to create an special partition first. This partition is called “Whole disk”, and must be the 3rd partition on the disk.
The other partitions are virtual slices of this
“Whole disk” partition.
But there are some limitations on the first partion of
hda
or sda
on the system. This partition must be
less than 2 gigabytes and this partition must be root.
Now that a blank partition has been set up, the file system can
be created. The most widely-used system in the Linux world is
the second extended file system (ext2), but with newer
high-capacity hard disks, journaling file systems are becoming
increasingly popular. We will create an ext2
file system. Instructions for other
file systems can be found at
http://cblfs.cross-lfs.org/index.php?section=6#File_System_.2F_Block_Device_.2F_Inode_Management_Tools.
To create an ext2
file system
on the CLFS partition, run the following:
mke2fs /dev/[xxx]
Replace [xxx]
with
the name of the CLFS partition (hda5
in our previous example).
Some host distributions use custom features in their
filesystem creation tools (E2fsprogs). This can cause
problems when booting into your new CLFS system, as those
features will not be supported by the CLFS-installed
E2fsprogs; you will get an error similar to unsupported filesystem features, upgrade
your e2fsprogs
. To check if your host system uses
custom enhancements, run the following command:
debugfs -R feature /dev/[xxx]
If the output contains features other than: dir_index; filetype; large_file; resize_inode or sparse_super then your host system may have custom enhancements. In that case, to avoid later problems, you should compile the stock E2fsprogs package and use the resulting binaries to re-create the filesystem on your CLFS partition:
cd /tmp
tar xjf /path/to/sources/e2fsprogs-1.40.4.tar.bz2
cd e2fsprogs-1.40.4
mkdir build
cd build
../configure
make #note that we intentionally don't 'make install' here!
./misc/mke2fs /dev/[xxx]
cd /tmp
rm -rf e2fsprogs-1.40.4
If a swap partition was created, it will need to be initialized for use by issuing the command below. If you are using an existing swap partition, there is no need to format it.
mkswap /dev/[yyy]
Replace [yyy]
with
the name of the swap partition.
Now that a file system has been created, the partition needs to
be made accessible. In order to do this, the partition needs to
be mounted at a chosen mount point. For the purposes of this
book, it is assumed that the file system is mounted under
/mnt/clfs
, but the directory
choice is up to you.
Choose a mount point and assign it to the CLFS
environment variable by running:
export CLFS=/mnt/clfs
Next, create the mount point and mount the CLFS file system by running:
mkdir -pv ${CLFS}
mount -v /dev/[xxx]
${CLFS}
Replace [xxx]
with
the designation of the CLFS partition.
If using multiple partitions for CLFS (e.g., one for
/
and another for /usr
), mount them using:
mkdir -pv ${CLFS} mount -v /dev/[xxx]
${CLFS} mkdir -v ${CLFS}/usr mount -v /dev/[yyy]
${CLFS}/usr
Replace [xxx]
and
[yyy]
with the
appropriate partition names.
Ensure that this new partition is not mounted with permissions
that are too restrictive (such as the nosuid, nodev, or noatime
options). Run the mount command without any
parameters to see what options are set for the mounted CLFS
partition. If nosuid
, nodev
, and/or noatime
are set, the partition will need to be
remounted.
Now that there is an established place to work, it is time to download the packages.
This chapter includes a list of packages that need to be downloaded for building a basic Linux system. The listed version numbers correspond to versions of the software that are known to work, and this book is based on their use. We highly recommend not using newer versions because the build commands for one version may not work with a newer version. The newest package versions may also have problems that require work-arounds. These work-arounds will be developed and stabilized in the development version of the book.
Download locations may not always be accessible. If a download location has changed since this book was published, Google (http://www.google.com/) provides a useful search engine for most packages. If this search is unsuccessful, try one of the alternative means of downloading discussed at http://cross-lfs.org/files/packages/1.1.0/.
Create a directory called ${CLFS}/sources
and use it to store your
sources and patches. All packages should be compiled there as
well. Using any other location for compiling may have
unexpected results.
To create this directory, execute, as user root
, the following command before starting
the download session:
mkdir -v ${CLFS}/sources
Make this directory writable and sticky. When a directory is marked “sticky”, that means that even if multiple users have write permission on that directory, any file within that directory can only be deleted or modified by its owner. The following command will enable the write and sticky modes:
chmod -v a+wt ${CLFS}/sources
Download or otherwise obtain the following packages:
Home page: http://www.gnu.org/software/autoconf
Download: http://ftp.gnu.org/gnu/autoconf/autoconf-2.61.tar.bz2
MD5 sum: 36d3fe706ad0950f1be10c46a429efe0
Home page: http://www.gnu.org/software/automake
Download: http://ftp.gnu.org/gnu/automake/automake-1.10.1.tar.bz2
MD5 sum: 4510391e6b3edaa4cffb3ced87c9560c
Home page: http://www.gnu.org/software/bash
Download: http://ftp.gnu.org/gnu/bash/bash-3.2.tar.gz
MD5 sum: 00bfa16d58e034e3c2aa27f390390d30
Download: http://ftp.gnu.org/gnu/bash/bash-doc-3.2.tar.gz
MD5 sum: 0e904cb46ca873fcfa65df19b024bec9
Home page: http://sources.redhat.com/binutils
Download: http://ftp.gnu.org/gnu/binutils/binutils-2.18.tar.bz2
MD5 sum: 9d22ee4dafa3a194457caf4706f9cf01
Home page: http://www.gnu.org/software/bison
Download: http://ftp.gnu.org/gnu/bison/bison-2.3.tar.bz2
MD5 sum: c18640c6ec31a169d351e3117ecce3ec
Home page: http://www.bzip.org/
Download: http://www.bzip.org/1.0.4/bzip2-1.0.4.tar.gz
MD5 sum: fc310b254f6ba5fbb5da018f04533688
Download: http://cross-lfs.org/files/packages/1.1.0/bootscripts-cross-lfs-1.1.0.tar.bz2
MD5 sum: 1e6fcdfcc25cee2b53091a2d9f07e464
Home page: http://www.gnu.org/software/coreutils
Download: http://ftp.gnu.org/gnu/coreutils/coreutils-6.9.tar.bz2
MD5 sum: c9607d8495f16e98906e7ed2d9751a06
Home page: http://www.gnu.org/software/dejagnu
Download: http://ftp.gnu.org/gnu/dejagnu/dejagnu-1.4.4.tar.gz
MD5 sum: 053f18fd5d00873de365413cab17a666
Home page: http://www.gnu.org/software/diffutils
Download: ftp://alpha.gnu.org/gnu/diffutils/diffutils-2.8.7.tar.gz
MD5 sum: 18d6587cb915e7aa110a5d463d6ed156
Home page: http://e2fsprogs.sourceforge.net
Download: http://downloads.sourceforge.net/e2fsprogs/e2fsprogs-1.40.4.tar.gz
MD5 sum: 124d744bdf9d443591eb8193c085944b
Home page: http://expect.nist.gov
Download: http://expect.nist.gov/src/expect-5.43.0.tar.gz
MD5 sum: 43e1dc0e0bc9492cf2e1a6f59f276bc3
Home page: http://www.darwinsys.com/file
Download: http://cross-lfs.org/files/packages/1.1.0/file-4.23.tar.gz
MD5 sum: 014a69979a8d5225a6ca2bcc4d7e967e
File (4.23) may no longer be available at the listed location. The site administrators of the master download location occasionally remove older versions when new ones are released. An alternative download location that may have the correct version available is http://cross-lfs.org/files/packages/1.1.0/.
Home page: http://www.gnu.org/software/findutils
Download: http://ftp.gnu.org/gnu/findutils/findutils-4.2.32.tar.gz
MD5 sum: aaa6beeb41a6f04963dff58f24a55b96
Home page: http://flex.sourceforge.net
Download: http://downloads.sourceforge.net/flex/flex-2.5.35.tar.bz2
MD5 sum: 10714e50cea54dc7a227e3eddcd44d57
Home page: http://www.gnu.org/software/gawk
Download: http://ftp.gnu.org/gnu/gawk/gawk-3.1.6.tar.bz2
MD5 sum: c9926c0bc8c177cb9579708ce67f0d75
Home page: http://gcc.gnu.org
Download: http://ftp.gnu.org/gnu/gcc/gcc-4.2.4/gcc-4.2.4.tar.bz2
MD5 sum: d79f553e7916ea21c556329eacfeaa16
Home page: http://www.gnu.org/software/gettext
Download: http://ftp.gnu.org/gnu/gettext/gettext-0.17.tar.gz
MD5 sum: 58a2bc6d39c0ba57823034d55d65d606
Home page: http://www.gnu.org/software/libc
Download: http://ftp.gnu.org/gnu/glibc/glibc-2.7.tar.bz2
MD5 sum: 065c5952b439deba40083ccd67bcc8f7
Home page: http://www.gnu.org/software/grep
Download: http://ftp.gnu.org/gnu/grep/grep-2.5.3.tar.bz2
MD5 sum: 27061ce1fde82876970b6549a156da8b
Home page: http://www.gnu.org/software/groff
Download: http://ftp.gnu.org/gnu/groff/groff-1.19.2.tar.gz
MD5 sum: f7c9cf2e4b9967d3af167d7c9fadaae4
Home page: http://www.gzip.org
Download: http://ftp.gnu.org/gnu/gzip/gzip-1.3.12.tar.gz
MD5 sum: b5bac2d21840ae077e0217bc5e4845b1
Home page: http://www.sethwklein.net/projects/iana-etc
Download: http://www.sethwklein.net/projects/iana-etc/downloads/iana-etc-2.20.tar.bz2
MD5 sum: 51d584b7b6115528c21e8ea32250f2b1
Home page: http://www.gnu.org/software/inetutils
Download: http://ftp.gnu.org/gnu/inetutils/inetutils-1.5.tar.gz
MD5 sum: aeacd11d19bf25c89d4eff38346bdfb9
Home page: http://linux-net.osdl.org/index.php/Iproute2
Download: http://developer.osdl.org/dev/iproute2/download/iproute2-2.6.23.tar.bz2
MD5 sum: 2e59da739ef19990408cf0a5cb0cae3e
Download: http://ftp.altlinux.com/pub/people/legion/kbd/kbd-1.13.tar.bz2
MD5 sum: 2639fdfe2412b29cbf6936d7db91cee3
Home page: http://www.greenwoodsoftware.com/less
Download: http://www.greenwoodsoftware.com/less/less-418.tar.gz
MD5 sum: b5864d76c54ddf4627fd57ab333c88b4
Home page: http://www.gnu.org/software/libtool
Download: http://ftp.gnu.org/gnu/libtool/libtool-1.5.26.tar.gz
MD5 sum: aa9c5107f3ec9ef4200eb6556f3b3c29
Home page: http://www.kernel.org
Download: http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.24.7.tar.bz2
MD5 sum: 40a73780d51525d28d36dec852c680c4
Home page: http://www.gnu.org/software/m4
Download: http://ftp.gnu.org/gnu/m4/m4-1.4.10.tar.bz2
MD5 sum: 0a35bab2f5d605e08083d7e3cbd4b8b0
Home page: http://www.gnu.org/software/make
Download: http://ftp.gnu.org/gnu/make/make-3.81.tar.bz2
MD5 sum: 354853e0b2da90c527e35aabb8d6f1e6
Home page: http://primates.ximian.com/~flucifredi/man
Download: http://primates.ximian.com/~flucifredi/man/man-1.6e.tar.gz
MD5 sum: d8187cd756398baefc48ba7d60ff6a8a
Home page: http://www.win.tue.nl/~aeb/linux/man
Download: http://www.kernel.org/pub/linux/docs/manpages/Archive/man-pages-3.01.tar.bz2
MD5 sum: ef311ffb0c4f43bad822345fb88498f7
Home page: http://www.mktemp.org/
Download: ftp://ftp.mktemp.org/pub/mktemp/mktemp-1.5.tar.gz
MD5 sum: 9a35c59502a228c6ce2be025fc6e3ff2
Home page: http://www.kerneltools.org/KernelTools.org
Download: http://www.kernel.org/pub/linux/utils/kernel/module-init-tools/module-init-tools-3.4.tar.bz2
MD5 sum: db6ac059e80e8dd4389dbe81ee61f3c6
Home page: http://dickey.his.com/ncurses
Download: ftp://invisible-island.net/ncurses/ncurses-5.6.tar.gz
MD5 sum: b6593abe1089d6aab1551c105c9300e3
Home page: http://www.gnu.org/software/patch
Download: ftp://alpha.gnu.org/gnu/diffutils/patch-2.5.9.tar.gz
MD5 sum: dacfb618082f8d3a2194601193cf8716
Home page: http://www.perl.com
Download: http://ftp.funet.fi/pub/CPAN/src/perl-5.8.8.tar.bz2
MD5 sum: a377c0c67ab43fd96eeec29ce19e8382
Home page: http://procps.sourceforge.net
Download: http://procps.sourceforge.net/procps-3.2.7.tar.gz
MD5 sum: f490bca772b16472962c7b9f23b1e97d
Home page: http://psmisc.sourceforge.net
Download: http://downloads.sourceforge.net/psmisc/psmisc-22.6.tar.gz
MD5 sum: 2e81938855cf5cc38856bd4a31d79a4c
Home page: http://cnswww.cns.cwru.edu/php/chet/readline/rltop.html
Download: http://ftp.gnu.org/gnu/readline/readline-5.2.tar.gz
MD5 sum: e39331f32ad14009b9ff49cc10c5e751
Home page: http://www.gnu.org/software/sed
Download: http://ftp.gnu.org/gnu/sed/sed-4.1.5.tar.gz
MD5 sum: 7a1cbbbb3341287308e140bd4834c3ba
Home page: http://pkg-shadow.alioth.debian.org
Download: ftp://pkg-shadow.alioth.debian.org/pub/pkg-shadow/shadow-4.1.2.tar.bz2
MD5 sum: ce90cbe9cba7f6673cb10cad49083c1c
Home page: http://www.infodrom.org/projects/sysklogd
Download: http://www.infodrom.org/projects/sysklogd/download/sysklogd-1.5.tar.gz
MD5 sum: e053094e8103165f98ddafe828f6ae4b
Download: ftp://ftp.cistron.nl/pub/people/miquels/sysvinit/sysvinit-2.86.tar.gz
MD5 sum: 7d5d61c026122ab791ac04c8a84db967
Home page: http://www.gnu.org/software/tar
Download: http://ftp.gnu.org/gnu/tar/tar-1.20.tar.bz2
MD5 sum: 1a7e17f27abf583b3b0bc059a827e68b
Home page: http://www.tcl.tk
Download: http://downloads.sourceforge.net/tcl/tcl8.4.16-src.tar.gz
MD5 sum: f1c783a49547778d160e10be2fb5d76f
Home page: http://www.gnu.org/software/texinfo
Download: http://ftp.gnu.org/gnu/texinfo/texinfo-4.11.tar.bz2
MD5 sum: c6bf13df4fbeff8ce874aacd6a51e814
Home page: http://mama.indstate.edu/users/ice/tree
Download: ftp://mama.indstate.edu/linux/tree/old/tree-1.5.1.1.tgz
MD5 sum: f8fc70a9260b50bf8b4613e9d5f5e589
Home page: http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev.html
Download: http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev-124.tar.bz2
MD5 sum: 4da0471c0ca3a2a2a77692f67120c03d
Home page: http://userweb.kernel.org/~kzak/util-linux-ng/
Download: http://www.kernel.org/pub/linux/utils/util-linux-ng/v2.14/util-linux-ng-2.14.tar.bz2
MD5 sum: 23f227da49df36f33fe47e917e332cd8
Home page: http://www.vim.org
Download: ftp://ftp.vim.org/pub/vim/unix/vim-7.1.tar.bz2
MD5 sum: 44c6b4914f38d6f9aa959640b89da329
Download: ftp://ftp.vim.org/pub/vim/extra/vim-7.1-lang.tar.gz
MD5 sum: 144aa049ba70621acf4247f0459f3ee7
Home page: http://www.zlib.net
Download: http://www.zlib.net/zlib-1.2.3.tar.gz
MD5 sum: debc62758716a169df9f62e6ab2bc634
Total size of these packages: about 200 MB
Download: http://gd.tuwien.ac.at/opsys/linux/Owl/pool/sources/elftoaout/elftoaout-2.3.tgz
MD5 sum: be3bd6f7ba8ae107cbdbaa820ba64f86
Home page: http://www.sparc-boot.org
Download: http://cross-lfs.org/files/packages/1.1.0/silo-1.4.13.tar.bz2
MD5 sum: 7039aabf3c1b3858ae8d0ccdde21343e
Total size of these packages: about 153 KB
In addition to the packages, several patches are also required. These patches correct any mistakes in the packages that should be fixed by the maintainer. The patches also make small modifications to make the packages easier to work with. The following patches will be needed to build a CLFS system:
Download: http://patches.cross-lfs.org/1.1.0/bash-3.2-fixes-8.patch
MD5 sum: 9f57c9bd5d7278529a9b13d8fc36a02e
Download: http://patches.cross-lfs.org/1.1.0/binutils-2.18-branch_update-3.patch
MD5 sum: afc0cc91efe7d2e5a14008d0625462ef
Download: http://patches.cross-lfs.org/1.1.0/binutils-2.18-posix-1.patch
MD5 sum: f2020cb369c2facbfd8987fa2263f31f
Download: http://patches.cross-lfs.org/1.1.0/coreutils-6.9-suppress_uptime_kill_su-1.patch
MD5 sum: 8bc938ec7210fff3885b37b1339dca45
Download: http://patches.cross-lfs.org/1.1.0/coreutils-6.9-uname-1.patch
MD5 sum: 865d271bec9039f45a3be0ada21edae0
Download: http://patches.cross-lfs.org/1.1.0/expect-5.43.0-spawn-2.patch
MD5 sum: 7706e1e8238c72eed8dc905d6f3b6aa9
Download: http://patches.cross-lfs.org/1.1.0/gcc-4.2.4-cross_search_paths-1.patch
MD5 sum: 2d316305d73bb14b3acd6a1f3a2ee4e9
Download: http://patches.cross-lfs.org/1.1.0/gcc-4.2.4-posix-1.patch
MD5 sum: 8df4fe6a9f77135ae1b0851786c40410
Download: http://patches.cross-lfs.org/1.1.0/gcc-4.2.4-PR31490-1.patch
MD5 sum: 43f3d086b57f02cb605819452936c4d7
Download: http://patches.cross-lfs.org/1.1.0/glibc-2.7-branch_update-1A.patch
MD5 sum: dd1119b68f26308446d33ccde05732b4
Download: http://patches.cross-lfs.org/1.1.0/glibc-2.7-libgcc_eh-1.patch
MD5 sum: f868605171066a0d8f572314feea415c
Download: http://patches.cross-lfs.org/1.1.0/glibc-2.7-localedef_segfault-1.patch
MD5 sum: 3ce6946b16e90a73d90ac701a5940709
Download: http://patches.cross-lfs.org/1.1.0/inetutils-1.5-no_server_man_pages-2.patch
MD5 sum: b04f46e66c4b438f609565073590ffd5
Download: http://patches.cross-lfs.org/1.1.0/linux-2.6.24.7-security_fixes-1.patch
MD5 sum: 7f244856cc40e478f5f66a6a6267d4c6
Download: http://patches.cross-lfs.org/1.1.0/mktemp-1.5-add_tempfile-3.patch
MD5 sum: 65d73faabe3f637ad79853b460d30a19
Download: http://patches.cross-lfs.org/1.1.0/module-init-tools-3.4-manpages-1.patch
MD5 sum: 2271047586981ae23adf01cc13d97791
Download: http://patches.cross-lfs.org/1.1.0/ncurses-5.6-bash_fix-1.patch
MD5 sum: c6f7f2ab0ebaf7721ebeb266641352db
Download: http://patches.cross-lfs.org/1.1.0/ncurses-5.6-branch_update-3.patch
MD5 sum: 5c5436409af4699e8b81e4100b5203ec
Download: http://patches.cross-lfs.org/1.1.0/perl-5.8.8-gcc42_fix-1.patch
MD5 sum: cd84d28231ea7f23d7e619d9304cc741
Download: http://patches.cross-lfs.org/1.1.0/perl-5.8.8-libc-2.patch
MD5 sum: 3bf8aef1fb6eb6110405e699e4141f99
Download: http://patches.cross-lfs.org/1.1.0/perl-5.8.8-no_page_h-1.patch
MD5 sum: fe49a8a539b14f53adfe24482c1fbe1f
Download: http://patches.cross-lfs.org/1.1.0/perl-5.8.8-security_fixes-1.patch
MD5 sum: 918a8f41d9e4fe1e272381e58be71497
Download: http://patches.cross-lfs.org/1.1.0/readline-5.2-fixes-4.patch
MD5 sum: 14ae1c3f3ff7223656f874bcf36e6f19
Download: http://patches.cross-lfs.org/1.1.0/texinfo-4.11-mbstate_fix-1.patch
MD5 sum: 37e3d170d809bb1c90e9741864839f66
Download: http://patches.cross-lfs.org/1.1.0/vim-7.1-branch_update-2.patch
MD5 sum: bd5ee693b6ed59567dc0e7c003d22694
Download: http://patches.cross-lfs.org/1.1.0/zlib-1.2.3-fPIC-1.patch
MD5 sum: 545d60b20bfde6f53023de44438cef59
Total size of these patches: about 8 MB
In addition to the above required patches, there exist a number of optional patches created by the CLFS community. These optional patches solve minor problems or enable functionality that is not enabled by default. Feel free to peruse the patches database located at http://patches.cross-lfs.org/1.1.0/ and acquire any additional patches to suit the system needs.
Download: http://patches.cross-lfs.org/1.1.0/elftoaout-2.3-64bit_fixes-1.patch
MD5 sum: 485e77cf2ed082d3d0ea99c703f1f14b
Download: http://patches.cross-lfs.org/1.1.0/gcc-4.2.4-pure64-1.patch
MD5 sum: 04d9b9cd2c3dad221d53a83d3a45d66f
Download: http://patches.cross-lfs.org/1.1.0/gcc-4.2.4-pure64_specs-1.patch
MD5 sum: a543edb70d0fbebb4f365bdad0a9a393
Download: http://patches.cross-lfs.org/1.1.0/inetutils-1.5-memcpy_sparc64-1.patch
MD5 sum: 04ed919685f6790931eaa8684452a755
Download: http://patches.cross-lfs.org/1.1.0/linux-2.6.24.7-elf_spitfire_fix-1.patch
MD5 sum: e0198bd54b7d1a2cd142d1bb22ae61f8
Download: http://patches.cross-lfs.org/1.1.0/silo-1.4.13-fixes-3.patch
MD5 sum: c65334fd6b3b99d824c458d0a3eac9b1
Total size of these patches: about 730.7 KB
Throughout this book, the environment variable CLFS
will be used several times. It is paramount
that this variable is always defined. It should be set to the
mount point chosen for the CLFS partition. Check that the
CLFS
variable is set up properly
with:
echo ${CLFS}
Make sure the output shows the path to the CLFS partition's
mount point, which is /mnt/clfs
if the provided example was followed. If the output is
incorrect, the variable can be set with:
export CLFS=/mnt/clfs
Having this variable set is beneficial in that commands such as install -dv ${CLFS}/tools can be typed literally. The shell will automatically replace “${CLFS}” with “/mnt/clfs” (or whatever the variable was set to) when it processes the command line.
If you haven't created the ${CLFS}
directory, do so at this time by
issuing the following commands:
install -dv ${CLFS}
Do not forget to check that ${CLFS}
is set whenever you leave and reenter the current working
environment (as when doing a “su” to root
or another user).
All programs compiled in Constructing
a Temporary System will be installed under ${CLFS}/tools
to keep them separate from the
programs compiled in Installing
Basic System Software. The programs compiled here are
temporary tools and will not be a part of the final CLFS
system. By keeping these programs in a separate directory, they
can easily be discarded later after their use. This also
prevents these programs from ending up in the host production
directories (easy to do by accident in Constructing
a Temporary System).
Create the required directory by running the following as
root
:
install -dv ${CLFS}/tools
The next step is to create a /tools
symlink on the host system. This will
point to the newly-created directory on the CLFS partition. Run
this command as root
as well:
ln -sv ${CLFS}/tools /
The above command is correct. The ln command has a few
syntactic variations, so be sure to check info coreutils ln and
ln(1)
before reporting what you
may think is an error.
The created symlink enables the toolchain to be compiled so
that it always refers to /tools
,
meaning that the compiler, assembler, and linker will work.
This will provide a common place for our temporary tools
system.
The cross-binutils and cross-compiler built in Constructing
Cross-Compile Tools will be installed under ${CLFS}/cross-tools
to keep them separate
from the host programs. The programs compiled here are
cross-tools and will not be a part of the final CLFS system or
the temp-system. By keeping these programs in a separate
directory, they can easily be discarded later after their use.
Create the required directory by running the following as
root
:
install -dv ${CLFS}/cross-tools
The next step is to create a /cross-tools
symlink on the host system. This
will point to the newly-created directory on the CLFS
partition. Run this command as root
as well:
ln -sv ${CLFS}/cross-tools /
The symlink isn't technically necessary (though the book's instructions do assume its existence), but is there mainly for consistency (because /tools is also symlinked to ${CLFS}/tools) and to simplify the installation of the cross-compile tools.
When logged in as user root
,
making a single mistake can damage or destroy a system.
Therefore, we recommend building the packages as an
unprivileged user. You could use your own user name, but to
make it easier to set up a clean work environment, create a new
user called clfs
as a member of
a new group (also named clfs
)
and use this user during the installation process. As
root
, issue the following
commands to add the new user:
groupadd clfs useradd -s /bin/bash -g clfs -d /home/clfs clfs mkdir -pv /home/clfs chown -v clfs:clfs /home/clfs
The meaning of the command line options:
-s
/bin/bash
This makes bash the default shell
for user clfs
.
-g
clfs
This option adds user clfs
to group clfs
.
clfs
This is the actual name for the created group and user.
To log in as clfs
(as opposed
to switching to user clfs
when
logged in as root
, which does
not require the clfs
user to
have a password), give clfs
a
password:
passwd clfs
Grant clfs
full access to
${CLFS}/cross-tools
and
${CLFS}/tools
by making
clfs
the directorys' owner:
chown -v clfs ${CLFS}/tools chown -v clfs ${CLFS}/cross-tools
If a separate working directory was created as suggested, give
user clfs
ownership of this
directory:
chown -v clfs ${CLFS}/sources
Next, login as user clfs
. This
can be done via a virtual console, through a display manager,
or with the following substitute user command:
su - clfs
The “-
” instructs
su to start a
login shell as opposed to a non-login shell. The difference
between these two types of shells can be found in detail in
bash(1)
and info bash.
Set up a good working environment by creating two new startup
files for the bash shell. While logged in
as user clfs
, issue the
following command to create a new .bash_profile
:
cat > ~/.bash_profile << "EOF"
exec env -i HOME=${HOME} TERM=${TERM} PS1='\u:\w\$ ' /bin/bash
EOF
When logged on as user clfs
,
the initial shell is usually a login shell which reads the
/etc/profile
of the host
(probably containing some settings and environment variables)
and then .bash_profile
. The
exec env
-i.../bin/bash command in the .bash_profile
file replaces the running shell
with a new one with a completely empty environment, except for
the HOME
, TERM
, and PS1
variables. This ensures that no unwanted and potentially
hazardous environment variables from the host system leak into
the build environment. The technique used here achieves the
goal of ensuring a clean environment.
The new instance of the shell is a non-login shell, which does not read
the /etc/profile
or .bash_profile
files, but rather reads the
.bashrc
file instead. Create the
.bashrc
file now:
cat > ~/.bashrc << "EOF"
set +h
umask 022
CLFS=/mnt/clfs
LC_ALL=POSIX
PATH=/cross-tools/bin:/bin:/usr/bin
export CLFS LC_ALL PATH
EOF
The set +h
command turns off bash's hash function. Hashing
is ordinarily a useful feature—bash uses a hash table to
remember the full path of executable files to avoid searching
the PATH
time and again to find the
same executable. However, the new tools should be used as soon
as they are installed. By switching off the hash function, the
shell will always search the PATH
when a program is to be run. As such, the shell will find the
newly compiled tools in /cross-tools
as soon as they are available
without remembering a previous version of the same program in a
different location.
Setting the user file-creation mask (umask) to 022 ensures that newly created files and directories are only writable by their owner, but are readable and executable by anyone (assuming default modes are used by the open(2) system call, new files will end up with permission mode 644 and directories with mode 755).
The CLFS
variable should be set to
the chosen mount point.
The LC_ALL
variable controls the
localization of certain programs, making their messages follow
the conventions of a specified country. If the host system uses
a version of Glibc older than 2.2.4, having LC_ALL
set to something other than
“POSIX” or
“C” (during this
chapter) may cause issues if you exit the chroot environment
and wish to return later. Setting LC_ALL
to “POSIX” or “C” (the two are equivalent) ensures that
everything will work as expected in the chroot environment.
By putting /cross-tools/bin
at
the beginning of the PATH
, the
cross-compiler built in Constructing
Cross-Compile Tools will be picked up by the build process
for the temp-system packages before anything that may be
installed on the host. This, combined with turning off hashing,
helps to ensure that you will be using the cross-compile tools
to build the temp-system in /tools.
Finally, to have the environment fully prepared for building the temporary tools, source the just-created user profile:
source ~/.bash_profile
Most packages provide a test suite. Running the test suite for a newly built package is a good idea because it can provide a “sanity check” indicating that everything compiled correctly. A test suite that passes its set of checks usually proves that the package is functioning as the developer intended. It does not, however, guarantee that the package is totally bug free.
It is not possible to run testsuites when cross-compiling, so package installation instructions do not explain how to run testsuites until Installing Basic System Software.
This chapter shows you how to create cross platform tools.
If for some reason you have to stop and come back later, remember to use the su - clfs command, and it will setup the build environment that you left.
Before issuing the build instructions for a package, the
package should be unpacked as user clfs
, and a cd into the created
directory should be performed. The build instructions
assume that the bash shell is in use.
Several of the packages are patched before compilation, but only when the patch is needed to circumvent a problem. A patch is often needed in both this and the next chapters, but sometimes in only one or the other. Therefore, do not be concerned if instructions for a downloaded patch seem to be missing. Warning messages about offset or fuzz may also be encountered when applying a patch. Do not worry about these warnings, as the patch was still successfully applied.
During the compilation of most packages, there will be several warnings that scroll by on the screen. These are normal and can safely be ignored. These warnings are as they appear—warnings about deprecated, but not invalid, use of the C or C++ syntax. C standards change fairly often, and some packages still use the older standard. This is not a problem, but does prompt the warning.
After installing each package, both in this and the next chapters, delete its source and build directories, unless specifically instructed otherwise. Deleting the sources prevents mis-configuration when the same package is reinstalled later.
CFLAGS
and CXXFLAGS
must not be set during the building of
cross-tools.
To disable CFLAGS
and CXXFLAGS
use the following commands:
unset CFLAGS unset CXXFLAGS
Now add these to ~/.bashrc
, just
in case you have to exit and restart building later:
echo unset CFLAGS >> ~/.bashrc echo unset CXXFLAGS >> ~/.bashrc
During the building of the cross-compile tools you will need to
set a few variables that will be dependent on your particular
needs. The first variable will be the triplet of the host
machine, which will be put into the CLFS_HOST
variable. To account for the
possibility that the host and target are the same arch, as
cross-compiling won't work when host and target are the same,
part of the triplet needs to be changed slightly to add
"cross". Set CLFS_HOST
using the
following command:
export CLFS_HOST="$(echo $MACHTYPE | \ sed "s/$(echo $MACHTYPE | cut -d- -f2)/cross/")"
Now you will need to set the triplet for the target architecture. Set the target variable using the following command:
export CLFS_TARGET="sparc64-unknown-linux-gnu"
Now add these to ~/.bashrc
, just
in case you have to exit and restart building later:
echo export CLFS_HOST=\""${CLFS_HOST}\"" >> ~/.bashrc echo export CLFS_TARGET=\""${CLFS_TARGET}\"" >> ~/.bashrc
We will need to setup target specific flags for the compiler and linkers.
export BUILD64="[BUILD64 entries]
" export GCCTARGET="[GCCTARGET entries]
"
Lets add the build flags to ~/.bashrc
to prevent issues if we stop and
come back later.
echo export BUILD64=\""${BUILD64}\"" >> ~/.bashrc echo export GCCTARGET=\""${GCCTARGET}\"" >> ~/.bashrc
The following table gives the entires for different Sparc 64 capable processors. Pick the processor that matches your system. Note: GCC settings are only needed in the early sections of the book, and will not be used in the final-system builds.
Table 5.1. List of architectures, target triplets, and recommended book
Processor | BUILD64 | GCCTARGET |
---|---|---|
Ultrasparc and Ultrasparc2 | -m64 -mcpu=ultrasparc -mtune=ultrasparc | -mcpu=ultrasparc -mtune=ultrasparc |
Ultrasparc3 | -m64 -mcpu=ultrasparc3 -mtune=ultrasparc3 | -mcpu=ultrasparc3 -mtune=ultrasparc3 |
The Linux Kernel contains a make target that installs “sanitized” kernel headers.
For this step you will need the kernel tarballs.
The following patch includes spitfire.h outside of kernel space in elf.h. It also adds spitfire.h to the list of headers installed on the system.
patch -Np1 -i ../linux-2.6.24.7-elf_spitfire_fix-1.patch
Install the header files that are common to all architectures:
install -dv /tools/include make mrproper make ARCH=sparc64 headers_check make ARCH=sparc64 INSTALL_HDR_PATH=dest headers_install cp -rv dest/include/* /tools/include
Details on this package are located in Section 10.5.2, “Contents of Linux-Headers.”
The File package contains a utility for determining the type of a given file or files.
Prepare File for compilation:
./configure --prefix=/cross-tools
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.30.2, “Contents of File.”
The Binutils package contains a linker, an assembler, and other tools for handling object files.
It is important that Binutils be compiled before Glibc and GCC because both Glibc and GCC perform various tests on the available linker and assembler to determine which of their own features to enable.
To make sure that the proper syntax is used for a couple of tools, apply the following patch:
patch -Np1 -i ../binutils-2.18-posix-1.patch
The following patches merges all updates from the 2.18 Branch from the Binutils developers:
patch -Np1 -i ../binutils-2.18-branch_update-3.patch
The Binutils documentation recommends building Binutils outside of the source directory in a dedicated build directory:
mkdir -v ../binutils-build cd ../binutils-build
Prepare Binutils for compilation:
AR=ar AS=as ../binutils-2.18/configure --prefix=/cross-tools \ --host=${CLFS_HOST} --target=${CLFS_TARGET} --with-lib-path=/tools/lib \ --disable-nls --enable-shared --enable-64-bit-bfd --disable-multilib
The meaning of the configure options:
--prefix=/cross-tools
This tells the configure script to prepare to install
the package in the /cross-tools
directory.
--host=${CLFS_HOST}
When used with --target, this creates a cross-architecture executable that creates files for ${CLFS_TARGET} but runs on ${CLFS_HOST}.
--target=${CLFS_TARGET}
When used with --host, this creates a cross-architecture executable that creates files for ${CLFS_TARGET} but runs on ${CLFS_HOST}.
--with-lib-path=/tools/lib
This tells the configure script to specify the library
search path during the compilation of Binutils,
resulting in /tools/lib
being passed to the linker. This prevents the linker
from searching through library directories on the host.
--disable-nls
This disables internationalization as i18n is not needed for the cross-compile tools.
--enable-shared
Enable the creation of the shared libraries.
--disable-multilib
This option disables the building of a multilib capable Binutils.
--enable-64-bit-bfd
This adds 64 bit support to Binutils.
Compile the package:
make configure-host make
The meaning of the make options:
configure-host
This checks the host environment and makes sure all the necessary tools are available to compile Binutils.
Install the package:
make install
Copy libiberty.h
to
/tools/include
directory:
cp -v ../binutils-2.18/include/libiberty.h /tools/include
Details on this package are located in Section 10.9.2, “Contents of Binutils.”
The GCC package contains the GNU compiler collection, which includes the C and C++ compilers.
Make a couple of essential adjustments to the specs file to ensure GCC uses our build environment:
patch -Np1 -i ../gcc-4.2.4-pure64_specs-1.patch
To make sure that a couple of tools use the proper syntax, apply the following patch:
patch -Np1 -i ../gcc-4.2.4-posix-1.patch
The following patch ensures that gcc does not search the
/usr
directory for libgcc_s.so
when cross-compiling:
patch -Np1 -i ../gcc-4.2.4-cross_search_paths-1.patch
Change the StartFile Spec to point to the correct library location:
echo " #undef STARTFILE_PREFIX_SPEC #define STARTFILE_PREFIX_SPEC \"/tools/lib/\"" >> gcc/config/sparc/linux.h echo " #undef STARTFILE_PREFIX_SPEC #define STARTFILE_PREFIX_SPEC \"/tools/lib/\"" >> gcc/config/sparc/linux64.h
Now alter gcc's
c preprocessor's default include search path to use
/tools
only:
cp -v gcc/Makefile.in{,.orig} sed -e "s@\(^CROSS_SYSTEM_HEADER_DIR =\).*@\1 /tools/include@g" \ gcc/Makefile.in.orig > gcc/Makefile.in
The GCC documentation recommends building GCC outside of the source directory in a dedicated build directory:
mkdir -v ../gcc-build cd ../gcc-build
Prepare GCC for compilation:
../gcc-4.2.4/configure --prefix=/cross-tools \ --host=${CLFS_HOST} --target=${CLFS_TARGET} --disable-multilib \ --with-local-prefix=/tools --disable-nls --disable-shared \ --disable-threads --enable-languages=c
The meaning of the configure options:
--with-local-prefix=/tools
The purpose of this switch is to remove /usr/local/include
from gcc's include search
path. This is not absolutely essential, however, it
helps to minimize the influence of the host system.
--disable-shared
Disables the creation of the shared libraries.
--disable-threads
This will prevent GCC from looking for the multi-thread include files, since they haven't been created for this architecture yet. GCC will be able to find the multi-thread information after the Glibc headers are created.
--enable-languages=c
This option ensures that only the C compiler is built.
Continue with compiling the package:
make CFLAGS_FOR_TARGET="${GCCTARGET}" all-gcc
Install the package:
make install-gcc
Details on this package are located in Section 10.10.2, “Contents of GCC.”
The Glibc package contains the main C library. This library provides the basic routines for allocating memory, searching directories, opening and closing files, reading and writing files, string handling, pattern matching, arithmetic, and so on.
It should be noted that compiling Glibc in any way other than the method suggested in this book puts the stability of the system at risk.
Disable linking to libgcc_eh
:
patch -Np1 -i ../glibc-2.7-libgcc_eh-1.patch
The following patch fixes an issue that can cause localdef to segfault:
patch -Np1 -i ../glibc-2.7-localedef_segfault-1.patch
The Glibc documentation recommends building Glibc outside of the source directory in a dedicated build directory:
mkdir -v ../glibc-build cd ../glibc-build
The following lines need to be added to config.cache
for Glibc to support NPTL:
echo "libc_cv_forced_unwind=yes" > config.cache echo "libc_cv_c_cleanup=yes" >> config.cache echo "libc_cv_sparc64_tls=yes" >> config.cache
Prepare Glibc for compilation:
BUILD_CC="gcc" CC="${CLFS_TARGET}-gcc ${BUILD64}" \ AR="${CLFS_TARGET}-ar" RANLIB="${CLFS_TARGET}-ranlib" \ ../glibc-2.7/configure --prefix=/tools \ --host=${CLFS_TARGET} --build=${CLFS_HOST} \ --disable-profile --enable-add-ons \ --with-tls --enable-kernel=2.6.0 --with-__thread \ --with-binutils=/cross-tools/bin --with-headers=/tools/include \ --cache-file=config.cache
The meaning of the new configure options:
CC="${CLFS_TARGET}-gcc
${BUILD64}"
Forces Glibc to build using our target architecture GCC utilizing the 64 Bit flags.
--libdir=/tools/lib64
Puts Glibc into /tools/lib64 instead of /tools/lib.
During this stage the following warning might appear:
configure: WARNING: *** These auxiliary programs are missing or *** incompatible versions: msgfmt *** some features will be disabled. *** Check the INSTALL file for required versions.
The missing or incompatible msgfmt program is generally harmless. This msgfmt program is part of the Gettext package which the host distribution should provide.
Compile the package:
make
Install the package:
make install
The stubs.h header installed by glibc looks for stubs-32.h and stubs-64.h. This configuration of glibc only generates stubs-64.h. Fix this with the following:
mv -v /tools/include/gnu/stubs{-64,}.h
Details on this package are located in Section 10.7.5, “Contents of Glibc.”
The GCC package contains the GNU compiler collection, which includes the C and C++ compilers.
The following patch enables fixes compilation errors with the kernel:
patch -Np1 -i ../gcc-4.2.4-PR31490-1.patch
Make a couple of essential adjustments to the specs file to ensure GCC uses our build environment:
patch -Np1 -i ../gcc-4.2.4-pure64_specs-1.patch
To make sure that a couple of tools use the proper syntax, apply the following patch:
patch -Np1 -i ../gcc-4.2.4-posix-1.patch
The following patch ensures that gcc does not search the
/usr
directory for libgcc_s.so
when cross-compiling:
patch -Np1 -i ../gcc-4.2.4-cross_search_paths-1.patch
Change the StartFile Spec to point to the correct library location:
echo " #undef STARTFILE_PREFIX_SPEC #define STARTFILE_PREFIX_SPEC \"/tools/lib/\"" >> gcc/config/sparc/linux.h echo " #undef STARTFILE_PREFIX_SPEC #define STARTFILE_PREFIX_SPEC \"/tools/lib/\"" >> gcc/config/sparc/linux64.h
Now alter gcc's
c preprocessor's default include search path to use
/tools
only:
cp -v gcc/Makefile.in{,.orig} sed -e "s@\(^CROSS_SYSTEM_HEADER_DIR =\).*@\1 /tools/include@g" \ gcc/Makefile.in.orig > gcc/Makefile.in
The GCC documentation recommends building GCC outside of the source directory in a dedicated build directory:
mkdir -v ../gcc-build cd ../gcc-build
Prepare GCC for compilation:
../gcc-4.2.4/configure --prefix=/cross-tools \ --target=${CLFS_TARGET} --host=${CLFS_HOST} --disable-multilib \ --with-local-prefix=/tools --disable-nls --enable-shared \ --enable-languages=c,c++ --enable-__cxa_atexit \ --enable-c99 --enable-long-long --enable-threads=posix
The meaning of the new configure options:
--enable-languages=c,c++
This option ensures that only the C and C++ compilers are built.
--enable-__cxa_atexit
This option allows use of __cxa_atexit, rather than atexit, to register C++ destructors for local statics and global objects and is essential for fully standards-compliant handling of destructors. It also affects the C++ ABI and therefore results in C++ shared libraries and C++ programs that are interoperable with other Linux distributions.
--enable-c99
Enable C99 support for C programs.
--enable-long-long
Enables long long support in the compiler.
--enable-threads=posix
This enables C++ exception handling for multi-threaded code.
Continue with compiling the package:
make AS_FOR_TARGET="${CLFS_TARGET}-as" \ LD_FOR_TARGET="${CLFS_TARGET}-ld"
Install the package:
make install
Details on this package are located in Section 10.10.2, “Contents of GCC.”
This chapter shows how to compile and install a minimal Linux system. This system will contain just enough tools to start constructing the final CLFS system in Installing Basic System Software and allow a working environment with more user convenience than a minimum environment would.
The tools in this chapter are cross-compiled using the
toolchain in /cross-tools
and
will be installed under the ${CLFS}/tools
directory to keep them separate
from the files installed in Installing
Basic System Software and the host production directories.
Since the packages compiled here are temporary, we do not want
them to pollute the soon-to-be CLFS system.
Check one last time that the CLFS
environment variable is set up properly:
echo ${CLFS}
Make sure the output shows the path to the CLFS partition's
mount point, which is /mnt/clfs
,
using our example.
During this section of the build you will see several WARNING messages like the one below. It is safe to ignore these messages.
configure: WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used.
Setup target-specific variables for the compiler and linkers:
export CC="${CLFS_TARGET}-gcc" export CXX="${CLFS_TARGET}-g++" export AR="${CLFS_TARGET}-ar" export AS="${CLFS_TARGET}-as" export RANLIB="${CLFS_TARGET}-ranlib" export LD="${CLFS_TARGET}-ld" export STRIP="${CLFS_TARGET}-strip"
Then add the build variables to ~/.bashrc
to prevent issues if you stop and
come back later:
echo export CC=\""${CC}\"" >> ~/.bashrc echo export CXX=\""${CXX}\"" >> ~/.bashrc echo export AR=\""${AR}\"" >> ~/.bashrc echo export AS=\""${AS}\"" >> ~/.bashrc echo export RANLIB=\""${RANLIB}\"" >> ~/.bashrc echo export LD=\""${LD}\"" >> ~/.bashrc echo export STRIP=\""${STRIP}\"" >> ~/.bashrc
The Binutils package contains a linker, an assembler, and other tools for handling object files.
To make sure that the proper syntax is used for a couple of tools, apply the following patch:
patch -Np1 -i ../binutils-2.18-posix-1.patch
The following patches merges all updates from the 2.18 Branch from the Binutils developers:
patch -Np1 -i ../binutils-2.18-branch_update-3.patch
The Binutils documentation recommends building Binutils outside of the source directory in a dedicated build directory:
mkdir -v ../binutils-build cd ../binutils-build
Prepare Binutils for compilation:
CC="${CC} ${BUILD64}" \ ../binutils-2.18/configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET} --target=${CLFS_TARGET} \ --disable-nls --enable-shared --enable-64-bit-bfd \ --disable-multilib
The meaning of the new configure options:
CC="${CC}
${BUILD64}"
Tells the compiler to use our 64-bit build flags.
Compile the package:
make configure-host make
Install the package:
make install
Details on this package are located in Section 10.9.2, “Contents of Binutils.”
The GCC package contains the GNU compiler collection, which includes the C and C++ compilers.
The following patch enables fixes compilation errors with the kernel:
patch -Np1 -i ../gcc-4.2.4-PR31490-1.patch
Make a couple of essential adjustments to the specs file to ensure GCC uses our build environment:
patch -Np1 -i ../gcc-4.2.4-pure64_specs-1.patch
To make sure that a couple of tools use the proper syntax, apply the following patch:
patch -Np1 -i ../gcc-4.2.4-posix-1.patch
The following patch ensures that gcc does not search the
/usr
directory for libgcc_s.so
when cross-compiling:
patch -Np1 -i ../gcc-4.2.4-cross_search_paths-1.patch
Now we will change cpp's search path so it
won't look in /usr/include
:
cp -v gcc/cppdefault.c{,.orig} sed -e '/#define STANDARD_INCLUDE_DIR/s@"/usr/include"@0@g' \ gcc/cppdefault.c.orig > gcc/cppdefault.c
Also, we need to set the directory searched by the fixincludes process for system headers, so it won't look at the host's headers:
cp -v gcc/Makefile.in{,.orig} sed -e 's@\(^NATIVE_SYSTEM_HEADER_DIR =\).*@\1 /tools/include@g' \ gcc/Makefile.in.orig > gcc/Makefile.in
When searching for the multilibs, force the build to use the
results of --print-multi-lib
from
our cross-compiler, not the native compiler gcc builds now:
cp -v gcc/Makefile.in{,.orig2} sed -e "/MULTILIBS/s@\$(GCC_FOR_TARGET)@/cross-tools/bin/${CC}@g" \ gcc/Makefile.in.orig2 > gcc/Makefile.in
The GCC documentation recommends building GCC outside of the source directory in a dedicated build directory:
mkdir -v ../gcc-build cd ../gcc-build
Before starting to build GCC, remember to unset any environment variables that override the default optimization flags.
Prepare GCC for compilation:
CC="${CC} ${BUILD64}" CXX="${CXX} ${BUILD64}" \ ../gcc-4.2.4/configure --prefix=/tools --disable-multilib \ --build=${CLFS_HOST} --host=${CLFS_TARGET} --target=${CLFS_TARGET} \ --libexecdir=/tools/lib --with-local-prefix=/tools --enable-long-long \ --enable-c99 --enable-shared --enable-threads=posix --disable-nls \ --enable-__cxa_atexit --enable-languages=c,c++ --disable-libstdcxx-pch
The meaning of the new configure options:
CXX="${CXX}
${BUILD64}"
This forces the C++ compiler to use our 64 Bit flags.
--disable-libstdcxx-pch
Do not build the pre-compiled header (PCH) for
libstdc++
. It takes up a
lot of space, and we have no use for it.
Compile the package:
make AS_FOR_TARGET="${AS}" \ LD_FOR_TARGET="${LD}"
Install the package:
make install
Now we copy the files that are placed in /tools/lib64
to /tools/lib
. We also delete the /tools/lib64
directory:
cp -va /tools/lib64/* /tools/lib rm -rvf /tools/lib64
Details on this package are located in Section 10.10.2, “Contents of GCC.”
The Ncurses package contains libraries for terminal-independent handling of character screens.
The following patch fixes an issue with some Bash versions:
patch -Np1 -i ../ncurses-5.6-bash_fix-1.patch
Prepare Ncurses for compilation:
CC="${CC} ${BUILD64}" CXX="${CXX} ${BUILD64}" \ ./configure --prefix=/tools --with-shared --build=${CLFS_HOST} \ --host=${CLFS_TARGET} --without-debug --without-ada \ --enable-overwrite --with-build-cc=gcc
The meaning of the configure options:
--with-shared
This tells Ncurses to create a shared library.
--without-debug
This tells Ncurses not to build with debug information.
--without-ada
This ensures that Ncurses does not build support for the Ada compiler which may be present on the host but will not be available when building the final system.
--enable-overwrite
This tells Ncurses to install its header files into
/tools/include
, instead
of /tools/include/ncurses
, to ensure
that other packages can find the Ncurses headers
successfully.
--with-build-cc=gcc
This tells Ncurses what type of compiler we are using.
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.17.2, “Contents of Ncurses.”
The Bash package contains the Bourne-Again SHell.
The following patch contains updates from the maintainer. The maintainer of Bash only releases these patches to fix serious issues:
patch -Np1 -i ../bash-3.2-fixes-8.patch
When bash is cross-compiled, it cannot test for the presence
of named pipes, amoung other things. If you used su to become an
unprivileged user, this combination will cause Bash to build
without process
substitution, which will break one of the c++
test scripts in glibc
. The
following prevents future problems by skipping tests that can
not run while cross-compiling or that do not run properly:
cat > config.cache << "EOF" ac_cv_func_mmap_fixed_mapped=yes ac_cv_func_strcoll_works=yes ac_cv_func_working_mktime=yes bash_cv_func_sigsetjmp=present bash_cv_getcwd_malloc=yes bash_cv_job_control_missing=present bash_cv_printf_a_format=yes bash_cv_sys_named_pipes=present bash_cv_ulimit_maxfds=yes bash_cv_under_sys_siglist=yes bash_cv_unusable_rtsigs=no gt_cv_int_divbyzero_sigfpe=yes EOF
Prepare Bash for compilation:
CC="${CC} ${BUILD64}" CXX="${CXX} ${BUILD64}" \ ./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET} \ --without-bash-malloc --cache-file=config.cache
The meaning of the configure option:
--without-bash-malloc
This option turns off the use of Bash's memory allocation (malloc) function which is known to cause segmentation faults. By turning this option off, Bash will use the malloc functions from Glibc which are more stable.
Compile the package:
make
Install the package:
make install
Make a link for programs that use sh for a shell:
ln -sv bash /tools/bin/sh
Details on this package are located in Section 10.27.2, “Contents of Bash.”
The Bzip2 package contains programs for compressing and decompressing files. Compressing text files with bzip2 yields a much better compression percentage than with the traditional gzip.
Bzip2's default Makefile target automatically runs the testsuite as well. Disable the tests since they won't work on a multi-architecture build:
cp -v Makefile{,.orig} sed -e 's@^\(all:.*\) test@\1@g' Makefile.orig > Makefile
The Bzip2 package does not contain a configure script. Compile it with:
make CC="${CC} ${BUILD64}" AR="${AR}" RANLIB="${RANLIB}"
Install the package:
make PREFIX=/tools install
Details on this package are located in Section 10.28.2, “Contents of Bzip2.”
The Coreutils package contains utilities for showing and setting the basic system characteristics.
The following command renames the internal implementation of futimens to gl_futimens as newer versions of Glibc provide an incompatible version:
sed -i "s/futimens/gl_&/" $(grep -lr futimens *)
Configure can not properly determine how to get free space
when cross-compiling, Without putting the following entry
into config.cache
the
df program will
not be built.
echo "fu_cv_sys_stat_statfs2_bsize=yes" > config.cache
Prepare Coreutils for compilation:
CC="${CC} ${BUILD64}" ./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET} \ --cache-file=config.cache
When we changed the futimens references, one of the files we
updated was touch.c. That change means the man
Makefile will try to regenerate the man
page for touch, by executing the compiled touch
program. If the target architecture
cannot be executed by the host system, the build will fail.
The following command fixes this by giving the man page a
newer timestamp than its corresponding source file:
touch man/touch.1
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.13.2, “Contents of Coreutils.”
The Diffutils package contains programs that show the differences between files or directories.
Prepare Diffutils for compilation:
CC="${CC} ${BUILD64}" ./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET}
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.29.2, “Contents of Diffutils.”
The Findutils package contains programs to find files. These programs are provided to recursively search through a directory tree and to create, maintain, and search a database (often faster than the recursive find, but unreliable if the database has not been recently updated).
Prepare Findutils for compilation:
CC="${CC} ${BUILD64}" ./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET}
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.31.2, “Contents of Findutils.”
The Zlib package contains compression and decompression routines used by some programs.
Prepare Zlib for compilation:
CC="${CC} ${BUILD64}" \ ./configure --prefix=/tools --shared
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.24.2, “Contents of Zlib.”
The File package contains a utility for determining the type of a given file or files.
Prepare File for compilation:
CC="${CC} ${BUILD64}" ./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET}
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.30.2, “Contents of File.”
The Gawk package contains programs for manipulating text files.
Prepare Gawk for compilation:
CC="${CC} ${BUILD64}" \ ./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET}
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.32.2, “Contents of Gawk.”
The Gettext package contains utilities for internationalization and localization. These allow programs to be compiled with NLS (Native Language Support), enabling them to output messages in the user's native language.
Only the programs in the gettext-tools
directory need to be
installed for the temp-system:
cd gettext-tools
When cross-compiling the Gettext configure script assumes we don't have a working wcwidth when we do. The following will fix possible compilation errors because of this assumption:
echo "gl_cv_func_wcwidth_works=yes" > config.cache
Prepare Gettext for compilation:
CC="${CC} ${BUILD64}" CXX="${CXX} ${BUILD64}" \ ./configure --prefix=/tools --disable-shared \ --build=${CLFS_HOST} --host=${CLFS_TARGET} \ --cache-file=config.cache
The meaning of the configure options:
--disable-shared
This tells Gettext not to create a shared library.
Compile the package:
make -C gnulib-lib make -C src msgfmt
Install the msgfmt binary:
cp -v src/msgfmt /tools/bin
Details on this package are located in Section 10.33.2, “Contents of Gettext.”
The Grep package contains programs for searching through files.
Prepare Grep for compilation:
CC="${CC} ${BUILD64}" ./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET} \ --disable-perl-regexp
The meaning of the configure options:
--disable-perl-regexp
This ensures that the grep program does not get linked against a Perl Compatible Regular Expression (PCRE) library that may be present on the host but will not be available when building the final system.
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.34.2, “Contents of Grep.”
The Gzip package contains programs for compressing and decompressing files.
The following command renames the internal implementation of futimens to gl_futimens as newer versions of Glibc provide an incompatible version:
sed -i "s/futimens/gl_&/" $(grep -lr futimens *)
Prepare Gzip for compilation:
CC="${CC} ${BUILD64}" ./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET}
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.36.2, “Contents of Gzip.”
The Make package contains a program for compiling packages.
Prepare Make for compilation:
CC="${CC} ${BUILD64}" ./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET}
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.40.2, “Contents of Make.”
The Patch package contains a program for modifying or creating files by applying a “patch” file typically created by the diff program.
Prepare Patch for compilation:
CC="${CC} ${BUILD64}" ./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET}
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.44.2, “Contents of Patch.”
The Sed package contains a stream editor.
Prepare Sed for compilation:
CC="${CC} ${BUILD64}" ./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET}
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.11.2, “Contents of Sed.”
The Tar package contains an archiving program.
TAR utilizes UTF-8 capability, without the following command the UTF-8 sections of the build will fail:
echo "gl_cv_func_wcwidth_works=yes" >> config.cache
Prepare Tar for compilation:
CC="${CC} ${BUILD64}" ./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET} \ --cache-file=config.cache
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.49.2, “Contents of Tar.”
The Texinfo package contains programs for reading, writing, and converting info pages.
The following patch fixes a build error due to mbstate being undefined:
patch -Np1 -i ../texinfo-4.11-mbstate_fix-1.patch
Prepare Texinfo for compilation:
CC="${CC} ${BUILD64}" ./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET}
Compile the package:
make -C tools/gnulib/lib make -C tools make
Install the package:
make install
Details on this package are located in Section 10.50.2, “Contents of Texinfo.”
There are two different ways you can proceed from this point to build the final system. You can build a kernel, a bootloader, and a few other utilities, boot into the temporary system, and build the rest there. Alternatively, you can chroot into the temporary system.
The boot method is needed when you are building on a different architecture. For example, if you are building a PowerPC system from an x86, you can't chroot. The chroot method is for when you are building on the same architecture. If you are building on, and for, an x86 system, you can simply chroot. The rule of thumb here is if the architectures match and you are running the same series kernel you can just chroot. If you aren't running the same series kernel, or are wanting to run a different ABI, you will need to use the boot option.
If you are in any doubt about this, you can try the following commands to see if you can chroot:
/tools/lib/libc.so.6 /tools/bin/gcc -v
If either of these commands fail, you will have to follow the boot method.
To chroot, you will also need a Linux Kernel-2.6.x (having been compiled with GCC-3.0 or greater). The reason for the kernel version requirement is that, without it, thread-local storage support in Binutils will not be built and the Native POSIX Threading Library (NPTL) test suite will segfault.
To check your kernel version, run cat /proc/version - if it does not say that you are running a 2.6.2 or later Linux kernel, compiled with GCC 3.0 or later, you cannot chroot.
For the boot method, follow If You Are Going to Boot.
For the chroot method, follow If You Are Going to Chroot.
This chapter shows how to complete the build of temporary tools to create a minimal system that will be used to boot the target machine and to build the final system packages.
There are a few additional packages that will need to be
installed to allow you to boot the minimal system. Some of
these packages will be installed onto root or in /usr on the
CLFS partition (${CLFS}/bin, ${CLFS}/usr/bin, etc...), rather
than /tools, using the "DESTDIR" option with make. This will
require the clfs
user to have
write access to the rest of the CLFS partition, so you will
need to temporarily change the ownership of ${CLFS} to the
clfs
user. Run the following
command as root
:
chown -v clfs ${CLFS}
It is time to create some structure in the CLFS file system. Create a standard directory tree by issuing the following commands:
mkdir -pv ${CLFS}/{bin,boot,dev,{etc/,}opt,home,lib,mnt} mkdir -pv ${CLFS}/{proc,media/{floppy,cdrom},sbin,srv,sys} mkdir -pv ${CLFS}/var/{lock,log,mail,run,spool} mkdir -pv ${CLFS}/var/{opt,cache,lib/{misc,locate},local} install -dv -m 0750 ${CLFS}/root install -dv -m 1777 ${CLFS}{/var,}/tmp mkdir -pv ${CLFS}/usr/{,local/}{bin,include,lib,sbin,src} mkdir -pv ${CLFS}/usr/{,local/}share/{doc,info,locale,man} mkdir -pv ${CLFS}/usr/{,local/}share/{misc,terminfo,zoneinfo} mkdir -pv ${CLFS}/usr/{,local/}share/man/man{1,2,3,4,5,6,7,8} for dir in ${CLFS}/usr{,/local}; do ln -sv share/{man,doc,info} $dir done
Directories are, by default, created with permission mode 755,
but this is not desirable for all directories. In the commands
above, two changes are made—one to the home directory of
user root
, and another to the
directories for temporary files.
The first mode change ensures that not just anybody can enter
the /root
directory—the
same as a normal user would do with his or her home directory.
The second mode change makes sure that any user can write to
the /tmp
and /var/tmp
directories, but cannot remove
another user's files from them. The latter is prohibited by the
so-called “sticky bit,”
the highest bit (1) in the 1777 bit mask.
The directory tree is based on the Filesystem Hierarchy
Standard (FHS) (available at http://www.pathname.com/fhs/).
In addition to the tree created above, this standard
stipulates the existence of /usr/local/games
and /usr/share/games
. The FHS is not precise as
to the structure of the /usr/local/share
subdirectory, so we create
only the directories that are needed. However, feel free to
create these directories if you prefer to conform more
strictly to the FHS.
Some programs use hard-wired paths to programs which do not exist yet. In order to satisfy these programs, create a number of symbolic links which will be replaced by real files throughout the course of the next chapter after the software has been installed.
ln -sv /tools/bin/{bash,cat,echo,grep,pwd,rm,stty} ${CLFS}/bin ln -sv /tools/bin/file ${CLFS}/usr/bin ln -sv /tools/lib/libgcc_s.so{,.1} ${CLFS}/usr/lib ln -sv /tools/lib/libstd*so* ${CLFS}/usr/lib ln -sv bash ${CLFS}/bin/sh
To enable some c++ tests in the glibc and binutils testsuites to link, create a directory and make some symbolic links:
mkdir -pv ${CLFS}/usr/lib64 ln -sv /tools/lib/libstd*so* ${CLFS}/usr/lib64
The E2fsprogs package contains the utilities for handling the
ext2
file system. It also
supports the ext3
journaling
file system.
The E2fsprogs documentation recommends that the package be built in a subdirectory of the source tree:
mkdir -v build cd build
Prepare E2fsprogs for compilation:
CC="${CC} ${BUILD64}" ../configure --prefix=/tools \ --enable-elf-shlibs --disable-evms --with-cc="${CC} ${BUILD64}" \ --with-linker=${LD} --host=${CLFS_TARGET}
The meaning of the configure options:
--enable-elf-shlibs
This creates the shared libraries which some programs in this package use.
--disable-evms
This disables the building of the Enterprise Volume Management System (EVMS) plugin. This plugin is not up-to-date with the latest EVMS internal interfaces and EVMS is not installed as part of a base CLFS system, so the plugin is not required. See the EVMS website at http://evms.sourceforge.net/ for more information regarding EVMS.
Compile the package:
make
Install the binaries, documentation and shared libraries:
make DESTDIR="${CLFS}" install
Install the static libraries and headers:
make install-libs
Create needed symlinks for a bootable system:
ln -sv /tools/sbin/{fsck.ext2,fsck.ext3,e2fsck} ${CLFS}/sbin
Details on this package are located in Section 10.12.2, “Contents of E2fsprogs.”
The Sysvinit package contains programs for controlling the startup, running, and shutdown of the system.
Make some modifications to allow you to boot into the minimal temp-system:
cp -v src/Makefile src/Makefile.orig sed -e 's@root@0@g' \ -e "s@/dev/initctl@${CLFS}&@g" \ -e 's@\(mknod \)-m \([0-9]* \)\(.* \)p@\1\3p; chmod \2\3@g' \ -e "s@/usr/lib@/tools/lib@" \ src/Makefile.orig > src/Makefile
Compile the package:
make -C src clobber make -C src CC="${CC} ${BUILD64}"
Install the package:
make -C src install INSTALL=install ROOT=${CLFS}
Create a new file ${CLFS}/etc/inittab
by running the
following:
cat > ${CLFS}/etc/inittab << "EOF"
# Begin /etc/inittab
id:3:initdefault:
si::sysinit:/etc/rc.d/init.d/rc sysinit
l0:0:wait:/etc/rc.d/init.d/rc 0
l1:S1:wait:/etc/rc.d/init.d/rc 1
l2:2:wait:/etc/rc.d/init.d/rc 2
l3:3:wait:/etc/rc.d/init.d/rc 3
l4:4:wait:/etc/rc.d/init.d/rc 4
l5:5:wait:/etc/rc.d/init.d/rc 5
l6:6:wait:/etc/rc.d/init.d/rc 6
ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now
su:S016:once:/sbin/sulogin
# Remove this section if you System only
# has a console port
1:2345:respawn:/sbin/agetty -I '\033(K' tty1 9600
2:2345:respawn:/sbin/agetty -I '\033(K' tty2 9600
3:2345:respawn:/sbin/agetty -I '\033(K' tty3 9600
4:2345:respawn:/sbin/agetty -I '\033(K' tty4 9600
5:2345:respawn:/sbin/agetty -I '\033(K' tty5 9600
6:2345:respawn:/sbin/agetty -I '\033(K' tty6 9600
# Uncomment this section if your system has a console
# port
#c0:12345:respawn:/sbin/agetty 9600 ttyS0 vt100
# End /etc/inittab
EOF
Details on this package are located in Section 10.48.3, “Contents of Sysvinit.”
The Module-Init-Tools package contains programs for handling kernel modules in Linux kernels greater than or equal to version 2.5.47.
The tarball only contains sgml source for the manual pages. The following patch contains the result of processing this through docbook2man which we do not build as part of a basic clfs install :
patch -Np1 -i ../module-init-tools-3.4-manpages-1.patch
Prepare Module-Init-Tools for compilation:
CC="${CC} ${BUILD64}" ./configure --prefix=/ \ --build=${CLFS_HOST} --host=${CLFS_TARGET}
Compile the package:
make
Install the package:
make DESTDIR=${CLFS} install
Details on this package are located in Section 10.43.2, “Contents of Module-Init-Tools.”
The Util-linux-ng package contains miscellaneous utility programs. Among them are utilities for handling file systems, consoles, partitions, and messages.
Prepare Util-linux-ng for compilation:
CC="${CC} ${BUILD64}" ./configure --build=${CLFS_HOST} \ --host=${CLFS_TARGET} --enable-login-utils \ --disable-makeinstall-chown
Compile the package:
make
Install the package:
make DESTDIR=${CLFS} install
Details on this package are located in Section 10.52.3, “Contents of Util-linux-ng.”
The Udev package contains programs for dynamic creation of device nodes.
Compile the package:
make CROSS_COMPILE="${CLFS_TARGET}-" CC="${CC} ${BUILD64}" \ LD="${CC} ${BUILD64}"
Install the package:
make DESTDIR=${CLFS} install
Details on this package are located in Section 10.51.2, “Contents of Udev.”
The ELFtoaout package contains the Sparc ELF to a.out converter.
The following patch fixes some 64 bit issues with elftoaout:
patch -Np1 -i ../elftoaout-2.3-64bit_fixes-1.patch
Compile the ELFtoaout package:
make
Install the package:
install -v -m 0755 -s elftoaout /cross-tools/bin
Details on this package are located in Section 10.54.2, “Contents of ELFtoaout.”
In order for user root
to be
able to login and for the name “root” to be recognized, there must be
relevant entries in the /etc/passwd
and /etc/group
files.
Create the ${CLFS}/etc/passwd
file by running the following command:
cat > ${CLFS}/etc/passwd << "EOF"
root::0:0:root:/root:/bin/bash
EOF
The actual password for root
(the “::” used here is
just a placeholder and allow you to login with no password)
will be set later.
Additional users you may want to add:
bin:x:1:1:bin:/bin:/bin/false
Can be useful for compatibility with legacy applications.
daemon:x:2:6:daemon:/sbin:/bin/false
It is often recommended to use an unprivileged User ID/Group ID for daemons to run as, in order to limit their access to the system.
adm:x:3:16:adm:/var/adm:/bin/false
Was used for programs that performed administrative tasks.
lp:x:10:9:lp:/var/spool/lp:/bin/false
Used by programs for printing
mail:x:30:30:mail:/var/mail:/bin/false
Often used by email programs
news:x:31:31:news:/var/spool/news:/bin/false
Often used for network news servers
uucp:x:32:32:uucp:/var/spool/uucp:/bin/false
Often used for Unix-to-Unix Copy of files from one server to the next
operator:x:50:0:operator:/root:/bin/bash
Often used to allow system operators to access the system
postmaster:x:51:30:postmaster:/var/spool/mail:/bin/false
Generally used as an account that receives all the information of troubles with the mail server
nobody:x:65534:65534:nobody:/:/bin/false
Used by NFS
Create the ${CLFS}/etc/group
file
by running the following command:
cat > ${CLFS}/etc/group << "EOF"
root:x:0:
bin:x:1:
sys:x:2:
kmem:x:3:
tty:x:4:
tape:x:5:
daemon:x:6:
floppy:x:7:
disk:x:8:
lp:x:9:
dialout:x:10:
audio:x:11:
video:x:12:
utmp:x:13:
usb:x:14:
cdrom:x:15:
EOF
Additional groups you may want to add
adm:x:16:root,adm,daemon
All users in this group are allowed to do administrative tasks
console:x:17:
This group has direct access to the console
cdrw:x:18:
This group is allowed to use the CDRW drive
mail:x:30:mail
Used by MTAs (Mail Transport Agents)
news:x:31:news
Used by Network News Servers
uucp:x:32:uucp
Used by the Unix-to-Unix copy users
users:x:1000:
The default GID used by shadow for new users
nogroup:x:65533:
This is a default group used by some programs that do not require a group
nobody:x:65534:
This is used by NFS
The created groups are not part of any standard—they are groups decided on in part by the requirements of the Udev configuration in the final system, and in part by common convention employed by a number of existing Linux distributions. The Linux Standard Base (LSB, available at http://www.linuxbase.org) recommends only that, besides the group “root” with a Group ID (GID) of 0, a group “bin” with a GID of 1 be present. All other group names and GIDs can be chosen freely by the system administrator since well-written programs do not depend on GID numbers, but rather use the group's name.
The login, agetty, and init programs (and others) use a number of log files to record information such as who was logged into the system and when. However, these programs will not write to the log files if they do not already exist. Initialize the log files and give them proper permissions:
touch ${CLFS}/var/run/utmp ${CLFS}/var/log/{btmp,lastlog,wtmp} chmod -v 664 ${CLFS}/var/run/utmp ${CLFS}/var/log/lastlog chmod -v 600 ${CLFS}/var/log/btmp
The /var/run/utmp
file records
the users that are currently logged in. The /var/log/wtmp
file records all logins and
logouts. The /var/log/lastlog
file records when each user last logged in. The /var/log/btmp
file records the bad login
attempts.
The Linux package contains the Linux kernel.
Here a temporary cross-compiled kernel will be built. When configuring it, select the minimal amount of options required to boot the target machine and build the final system. I.e., no support for sound, printers, etc. will be needed.
Also, try to avoid the use of modules if possible, and don't use the resulting kernel image for production systems.
A number of vulnerabilities have come to light after the stable kernel team stopped supporting 2.6.24. The following patch addresses them:
patch -Np1 -i ../linux-2.6.24.7-security_fixes-1.patch
Building the kernel involves a few steps—configuration,
compilation, and installation. Read the README
file in the kernel source tree for
alternative methods to the way this book configures the
kernel.
The following patch includes spitfire.h outside of kernel space in elf.h. It also adds spitfire.h to the list of headers installed on the system.
patch -Np1 -i ../linux-2.6.24.7-elf_spitfire_fix-1.patch
Prepare for compilation by running the following command:
To ensure that your system boots and you can properly run both 32 bit and 64 bit binaries, please make sure that you enable support for ELF and emulations for 32bit ELF into the kernel.
make mrproper ARCH=sparc64 CROSS_COMPILE=${CLFS_TARGET}-
This ensures that the kernel tree is absolutely clean. The kernel team recommends that this command be issued prior to each kernel compilation. Do not rely on the source tree being clean after un-tarring.
Configure the kernel via a menu-driven interface:
make ARCH=sparc64 CROSS_COMPILE=${CLFS_TARGET}- menuconfig
Compile the kernel image and modules:
make ARCH=sparc64 CROSS_COMPILE=${CLFS_TARGET}-
If the use of kernel modules can't be avoided, an
/etc/modprobe.conf
file may be
needed. Information pertaining to modules and kernel
configuration is located in the kernel documentation in the
Documentation
directory of the
kernel sources tree. The modprobe.conf
man page may also be of
interest.
Be very careful when reading other documentation relating to
kernel modules because it usually applies to 2.4.x kernels
only. As far as we know, kernel configuration issues specific
to Hotplug and Udev are not documented. The problem is that
Udev will create a device node only if Hotplug or a
user-written script inserts the corresponding module into the
kernel, and not all modules are detectable by Hotplug. Note
that statements like the one below in the /etc/modprobe.conf
file do not work with
Udev:
alias char-major-XXX some-module
Install the modules, if the kernel configuration uses them:
make INSTALL_MOD_PATH=${CLFS} ARCH=sparc64 \ CROSS_COMPILE=${CLFS_TARGET}- modules_install
After kernel compilation is complete, additional steps are
required to complete the installation. Some files need to be
copied to the ${CLFS}/boot
directory.
Issue the following command to install the kernel:
cp -v vmlinux ${CLFS}/boot/clfskernel-2.6.24.7
System.map
is a symbol file for
the kernel. It maps the function entry points of every
function in the kernel API, as well as the addresses of the
kernel data structures for the running kernel. Issue the
following command to install the map file:
cp -v System.map ${CLFS}/boot/System.map-2.6.24.7
The kernel configuration file .config
produced by the make menuconfig step above
contains all the configuration selections for the kernel that
was just compiled. It is a good idea to keep this file for
future reference:
cp -v .config ${CLFS}/boot/config-2.6.24.7
Details on this package are located in Section 12.3.2, “Contents of Linux.”
The Silo package contains the Sparc Improved boot LOader.
The following patch fixes compile issues:
patch -Np1 -i ../silo-1.4.13-fixes-3.patch
Compile the Silo package:
make CROSS_COMPILE=${CLFS_TARGET}-
Install the package:
make DESTDIR=${CLFS} install
Details on this package are located in Section 10.55.2, “Contents of Silo.”
The new instance of the shell that will start when the system
is booted is a login
shell, which will read .bash_profile
file. Create the .bash_profile
file now:
cat > ${CLFS}/root/.bash_profile << "EOF"
set +h
PS1='\u:\w\$ '
LC_ALL=POSIX
PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin:/tools/sbin
export LC_ALL PATH PS1
EOF
The LC_ALL
variable controls the
localization of certain programs, making their messages follow
the conventions of a specified country. Setting LC_ALL
to “POSIX” or “C” (the two are equivalent) ensures that
everything will work as expected on your temporary system.
By putting /tools/bin
at the end
of the standard PATH
, all the
programs installed in Constructing
a Temporary System are only picked up by the shell if they
have not yet been built on the target system. This
configuration forces use of the final system binaries as they
are built over the temp-system, minimising the chance of final
system programs being built against the temp-system.
We will need to copy our build variables into our new system:
echo export BUILD64=\""${BUILD64}\"" >> ${CLFS}/root/.bash_profile
The /etc/fstab
file is used by
some programs to determine where file systems are to be mounted
by default, which must be checked, and in which order. Create a
new file systems table like this:
cat > ${CLFS}/etc/fstab << "EOF"
# Begin /etc/fstab
# file system mount-point type options dump fsck
# order
/dev/[xxx]
/ [fff]
defaults 1 1
/dev/[yyy]
swap swap pri=1 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
devpts /dev/pts devpts gid=4,mode=620 0 0
shm /dev/shm tmpfs defaults 0 0
none /proc/openprom openpromfs defaults 0 0
# End /etc/fstab
EOF
Replace [xxx]
,
[yyy]
, and [fff]
with the values
appropriate for the system, for example, hda2
, hda5
, and
ext2
. For details on the six
fields in this file, see man 5
fstab.
The /dev/shm
mount point for
tmpfs
is included to allow
enabling POSIX-shared memory. The kernel must have the required
support built into it for this to work (more about this is in
the next section). Please note that very little software
currently uses POSIX-shared memory. Therefore, consider the
/dev/shm
mount point optional.
For more information, see Documentation/filesystems/tmpfs.txt
in the
kernel source tree.
The CLFS-Bootscripts package contains a set of scripts to start/stop the CLFS system at bootup/shutdown.
Install the package:
make DESTDIR=${CLFS} install-minimal
The setclock
script reads the time from the hardware clock, also known as
the BIOS or the Complementary Metal Oxide Semiconductor
(CMOS) clock. If the hardware clock is set to UTC, this
script will convert the hardware clock's time to the local
time using the /etc/localtime
file (which tells the hwclock program which
timezone the user is in). There is no way to detect whether
or not the hardware clock is set to UTC, so this needs to be
configured manually.
If you do not know whether or not the hardware clock is set
to UTC, you can find out after you have booted the new
machine by running the hwclock --localtime --show
command, and if necessary editing the /etc/sysconfig/clock
script. The worst that
will happen if you make a wrong guess here is that the time
displayed will be wrong.
Change the value of the UTC
variable below to a value of 0
(zero) if the hardware clock is not set to UTC time.
cat > ${CLFS}/etc/sysconfig/clock << "EOF"
# Begin /etc/sysconfig/clock
UTC=1
# End /etc/sysconfig/clock
EOF
Details on this package are located in Section 11.2.2, “Contents of CLFS-Bootscripts.”
The commands in the remainder of the book should be run as
the root
user. Also,
double-check that ${CLFS} is set as root
.
When the kernel boots the system, it requires the presence of
a few device nodes, in particular the console
and null
devices. The device nodes will be
created on the hard disk so that they are available before
udev has been
started, and additionally when Linux is started in single
user mode (hence the restrictive permissions on console
). Create these by running the
following commands:
mknod -m 600 ${CLFS}/dev/console c 5 1 mknod -m 666 ${CLFS}/dev/null c 1 3
Currently, the ${CLFS}
directory
and all of its subdirectories are owned by the user
clfs
, a user that exists only
on the host system. For security reasons, the ${CLFS} root
directory and all of it subdirectories should be owned by
root
. Change the ownership for
${CLFS} and its subdirectories by running this command:
chown -Rv root:root ${CLFS}
This is for the configuration of silo, similar to what is in bootscripts.
cat > ${CLFS}/etc/silo.conf << "EOF"
# Begin /etc/silo.conf
partition = 1 # Boot partition (= root partition)
root = /dev/sda1 # Root partition
timeout = 150 # Wait 15 seconds before booting the default section
image = /boot/clfskernel-2.6.24.7
label = linux
# End /etc/silo.conf
EOF
If you already have Silo installed on your target system, you do not need to reinstall it. Silo is just a chain loader and has no bearing on the system build.
After you get the build copied to when you can boot, you will need to issue the following command:
silo -f
This chapter shows how to prepare a chroot jail to build the final system packages into.
The E2fsprogs package contains the utilities for handling the
ext2
file system. It also
supports the ext3
journaling
file system.
The E2fsprogs documentation recommends that the package be built in a subdirectory of the source tree:
mkdir -v build cd build
Prepare E2fsprogs for compilation:
CC="${CC} ${BUILD64}" ../configure --prefix=/tools \ --enable-elf-shlibs --disable-evms --with-cc="${CC} ${BUILD64}" \ --with-linker=${LD} --host=${CLFS_TARGET}
The meaning of the configure options:
--enable-elf-shlibs
This creates the shared libraries which some programs in this package use.
--disable-evms
This disables the building of the Enterprise Volume Management System (EVMS) plugin. This plugin is not up-to-date with the latest EVMS internal interfaces and EVMS is not installed as part of a base CLFS system, so the plugin is not required. See the EVMS website at http://evms.sourceforge.net/ for more information regarding EVMS.
Compile the package:
make libs
Install the static libraries and headers:
make install-libs
The meaning of the make option:
install-libs
This command will only install the e2fsprogs libraries.
Details on this package are located in Section 10.12.2, “Contents of E2fsprogs.”
The Util-linux-ng package contains miscellaneous utility programs. Among them are utilities for handling file systems, consoles, partitions, and messages.
Prepare Util-linux-ng for compilation:
CC="${CC} ${BUILD64}" ./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET}
Compile the package:
make -C mount mount umount make -C text-utils more
Install the package:
cp -v mount/{,u}mount text-utils/more /tools/bin
Details on this package are located in Section 10.52.3, “Contents of Util-linux-ng.”
The commands in the remainder of the book should be run as
the root
user. Also,
double-check that ${CLFS} is set as root
.
Various file systems exported by the kernel are used to communicate to and from the kernel itself. These file systems are virtual in that no disk space is used for them. The content of the file systems resides in memory.
Begin by creating directories onto which the file systems will be mounted:
mkdir -pv ${CLFS}/{dev,proc,sys}
Now mount the file systems:
mount -vt proc proc ${CLFS}/proc mount -vt sysfs sysfs ${CLFS}/sys
Remember that if for any reason you stop working on the CLFS system and start again later, it is important to check that these file systems are mounted again before entering the chroot environment.
Two device nodes, /dev/console and /dev/null, are required to be present on the filesystem. These are needed by the kernel even before starting Udev early in the boot process, so we create them here:
mknod -m 600 ${CLFS}/dev/console c 5 1 mknod -m 666 ${CLFS}/dev/null c 1 3
Once the system is complete and booting, the rest of our device nodes are created by the Udev package. Since this package is not available to us right now, we must take other steps to provide device nodes under on the CLFS filesystem. We will use the “bind” option in the mount command to make our host system's /dev structure appear in the new CLFS filesystem:
mount -v -o bind /dev ${CLFS}/dev
Additional file systems will soon be mounted from within the chroot environment. To keep the host up to date, perform a “fake mount” for each of these now:
mount -f -vt tmpfs tmpfs ${CLFS}/dev/shm mount -f -vt devpts -o gid=4,mode=620 devpts ${CLFS}/dev/pts
It is time to enter the chroot environment to begin building
and installing the final CLFS system. As user root
, run the following command to enter
the realm that is, at the moment, populated with only the
temporary tools:
chroot "${CLFS}" /tools/bin/env -i \ HOME=/root TERM="${TERM}" PS1='\u:\w\$ ' \ PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \ /tools/bin/bash --login +h
The -i
option given to
the env command
will clear all variables of the chroot environment. After that,
only the HOME
, TERM
, PS1
, and
PATH
variables are set again. The
TERM=${TERM}
construct
will set the TERM
variable inside
chroot to the same value as outside chroot. This variable is
needed for programs like vim and less to operate properly. If
other variables are needed, such as CFLAGS
or CXXFLAGS
,
this is a good place to set them again.
From this point on, there is no need to use the CLFS
variable anymore, because all work will be
restricted to the CLFS file system. This is because the Bash
shell is told that ${CLFS}
is now
the root (/
) directory.
Notice that /tools/bin
comes last
in the PATH
. This means that a
temporary tool will no longer be used once its final version is
installed. This occurs when the shell does not
“remember” the locations
of executed binaries—for this reason, hashing is switched
off by passing the +h
option to bash.
It is important that all the commands throughout the remainder
of this chapter and the following chapters are run from within
the chroot environment. If you leave this environment for any
reason (rebooting for example), remember to first mount the
proc
and devpts
file systems (discussed in the
previous section) and enter chroot again before continuing with
the installations.
Note that the bash prompt will say
I have no name!
This is
normal because the /etc/passwd
file has not been created yet.
Currently, the /tools
and
/cross-tools
directories are
owned by the user clfs,
a user that exists only on the host system. Although the
/tools
and /cross-tools
directories can be deleted once
the CLFS system has been finished, they can be retained to
build additional CLFS systems. If the /tools
and /cross-tools
directories are kept as is, the
files are owned by a user ID without a corresponding account.
This is dangerous because a user account created later could
get this same user ID and would own the /tools
directory and all the files therein,
thus exposing these files to possible malicious manipulation.
To avoid this issue, add the clfs
user to the new CLFS system later when
creating the /etc/passwd
file,
taking care to assign it the same user and group IDs as on the
host system. Alternatively, assign the contents of the
/tools
and /cross-tools
directories to user root
by running the following commands:
chown -Rv 0:0 /tools chown -Rv 0:0 /cross-tools
The commands use 0:0
instead of root:root
,
because chown is
unable to resolve the name “root” until the passwd
file has been created.
It is time to create some structure in the CLFS file system. Create a standard directory tree by issuing the following commands:
mkdir -pv /{bin,boot,dev,{etc/,}opt,home,lib,mnt} mkdir -pv /{proc,media/{floppy,cdrom},sbin,srv,sys} mkdir -pv /var/{lock,log,mail,run,spool} mkdir -pv /var/{opt,cache,lib/{misc,locate},local} install -dv -m 0750 /root install -dv -m 1777 {/var,}/tmp mkdir -pv /usr/{,local/}{bin,include,lib,sbin,src} mkdir -pv /usr/{,local/}share/{doc,info,locale,man} mkdir -pv /usr/{,local/}share/{misc,terminfo,zoneinfo} mkdir -pv /usr/{,local/}share/man/man{1..8} for dir in /usr{,/local}; do ln -sv share/{man,doc,info} $dir done
Directories are, by default, created with permission mode 755,
but this is not desirable for all directories. In the commands
above, two changes are made—one to the home directory of
user root
, and another to the
directories for temporary files.
The first mode change ensures that not just anybody can enter
the /root
directory—the
same as a normal user would do with his or her home directory.
The second mode change makes sure that any user can write to
the /tmp
and /var/tmp
directories, but cannot remove
another user's files from them. The latter is prohibited by the
so-called “sticky bit,”
the highest bit (1) in the 1777 bit mask.
The directory tree is based on the Filesystem Hierarchy
Standard (FHS) (available at http://www.pathname.com/fhs/).
In addition to the tree created above, this standard
stipulates the existence of /usr/local/games
and /usr/share/games
. The FHS is not precise as
to the structure of the /usr/local/share
subdirectory, so we create
only the directories that are needed. However, feel free to
create these directories if you prefer to conform more
strictly to the FHS.
Some programs use hard-wired paths to programs which do not exist yet. In order to satisfy these programs, create a number of symbolic links which will be replaced by real files throughout the course of the next chapter after the software has been installed.
ln -sv /tools/bin/{bash,cat,echo,grep,pwd,rm,stty} /bin ln -sv /tools/bin/file /usr/bin ln -sv /tools/lib/libgcc_s.so{,.1} /usr/lib ln -sv /tools/lib/libstd* /usr/lib ln -sv bash /bin/sh
To enable some c++ tests in the glibc and binutils testsuites to link, create a directory and make some symbolic links:
mkdir -pv /usr/lib64 ln -sv /tools/lib/libstd*so* /usr/lib64
We will need to setup target specific flags for the compiler and linkers.
export BUILD64="[BUILD64 entries]"
To prevent errors when you come back to your build, we will export these variables to prevent any build issues in the future:
echo export BUILD64=\""${BUILD64}\"" >> ~/.bash_profile
The following table gives the entires for different Sparc 64 capable processors. Pick the processor that matches your system. Note: GCC settings are only needed in the early sections of the book, and will not be used in the final-system builds.
Table 8.1. List of architectures, target triplets, and recommended book
Processor | BUILD64 | GCCTARGET |
---|---|---|
Ultrasparc and Ultrasparc2 | -m64 -mcpu=ultrasparc -mtune=ultrasparc | -mcpu=ultrasparc -mtune=ultrasparc |
Ultrasparc3 | -m64 -mcpu=ultrasparc3 -mtune=ultrasparc3 | -mcpu=ultrasparc3 -mtune=ultrasparc3 |
In order for user root
to be
able to login and for the name “root” to be recognized, there must be
relevant entries in the /etc/passwd
and /etc/group
files.
Create the /etc/passwd
file by
running the following command:
cat > /etc/passwd << "EOF"
root:x:0:0:root:/root:/bin/bash
EOF
The actual password for root
(the “x” used here is
just a placeholder) will be set later.
Additional users you may want to add:
bin:x:1:1:bin:/bin:/bin/false
Can be useful for compatibility with legacy applications.
daemon:x:2:6:daemon:/sbin:/bin/false
It is often recommended to use an unprivileged User ID/Group ID for daemons to run as, in order to limit their access to the system.
adm:x:3:16:adm:/var/adm:/bin/false
Was used for programs that performed administrative tasks.
lp:x:10:9:lp:/var/spool/lp:/bin/false
Used by programs for printing
mail:x:30:30:mail:/var/mail:/bin/false
Often used by email programs
news:x:31:31:news:/var/spool/news:/bin/false
Often used for network news servers
uucp:x:32:32:uucp:/var/spool/uucp:/bin/false
Often used for Unix-to-Unix Copy of files from one server to the next
operator:x:50:0:operator:/root:/bin/bash
Often used to allow system operators to access the system
postmaster:x:51:30:postmaster:/var/spool/mail:/bin/false
Generally used as an account that receives all the information of troubles with the mail server
nobody:x:65534:65534:nobody:/:/bin/false
Used by NFS
Create the /etc/group
file by
running the following command:
cat > /etc/group << "EOF"
root:x:0:
bin:x:1:
sys:x:2:
kmem:x:3:
tty:x:4:
tape:x:5:
daemon:x:6:
floppy:x:7:
disk:x:8:
lp:x:9:
dialout:x:10:
audio:x:11:
video:x:12:
utmp:x:13:
usb:x:14:
cdrom:x:15:
EOF
Additional groups you may want to add
adm:x:16:root,adm,daemon
All users in this group are allowed to do administrative tasks
console:x:17:
This group has direct access to the console
cdrw:x:18:
This group is allowed to use the CDRW drive
mail:x:30:mail
Used by MTAs (Mail Transport Agents)
news:x:31:news
Used by Network News Servers
uucp:x:32:uucp
Used by the Unix-to-Unix copy users
users:x:1000:
The default GID used by shadow for new users
nogroup:x:65533:
This is a default group used by some programs that do not require a group
nobody:x:65534:
This is used by NFS
The created groups are not part of any standard—they are groups decided on in part by the requirements of the Udev configuration in the final system, and in part by common convention employed by a number of existing Linux distributions. The Linux Standard Base (LSB, available at http://www.linuxbase.org) recommends only that, besides the group “root” with a Group ID (GID) of 0, a group “bin” with a GID of 1 be present. All other group names and GIDs can be chosen freely by the system administrator since well-written programs do not depend on GID numbers, but rather use the group's name.
To remove the “I have no
name!” prompt, start a new shell. Since a full
Glibc was installed in Constructing
Cross-Compile Tools and the /etc/passwd
and /etc/group
files have been created, user name
and group name resolution will now work.
exec /tools/bin/bash --login +h
Note the use of the +h
directive. This tells bash not to use its internal
path hashing. Without this directive, bash would remember the paths
to binaries it has executed. To ensure the use of the newly
compiled binaries as soon as they are installed, the +h
directive will be used for the
duration of the nexts chapters.
The login, agetty, and init programs (and others) use a number of log files to record information such as who was logged into the system and when. However, these programs will not write to the log files if they do not already exist. Initialize the log files and give them proper permissions:
touch /var/run/utmp /var/log/{btmp,lastlog,wtmp} chgrp -v utmp /var/run/utmp /var/log/lastlog chmod -v 664 /var/run/utmp /var/log/lastlog chmod -v 600 /var/log/btmp
The /var/run/utmp
file records
the users that are currently logged in. The /var/log/wtmp
file records all logins and
logouts. The /var/log/lastlog
file records when each user last logged in. The /var/log/btmp
file records the bad login
attempts.
Mount the proper virtual (kernel) file systems on the newly-created directories:
mount -vt devpts -o gid=4,mode=620 none /dev/pts mount -vt tmpfs none /dev/shm
The mount commands executed above may result in the following warning message:
can't open /etc/fstab: No such file or directory.
This file—/etc/fstab
—has not been created yet
but is also not required for the file systems to be properly
mounted. As such, the warning can be safely ignored.
This chapter builds the tools needed to run the tests that the packages have. I.e., make check. Tcl, Expect, and DejaGNU are needed for the GCC and Binutils testsuites, and Tree is used by the Udev testsuite. Installing four packages for testing purposes may seem excessive, but it is very reassuring, if not essential, to know that the most important tools are working properly.
The Tcl package contains the Tool Command Language.
Prepare Tcl for compilation:
cd unix ./configure --prefix=/tools
Build the package:
make
Install the package:
make install
Tcl's private header files are needed for the next package, Expect. Install them into /tools:
make install-private-headers
Now make a necessary symbolic link:
ln -sv tclsh8.4 /tools/bin/tclsh
The Expect package contains a program for carrying out scripted dialogues with other interactive programs.
The following sed tells configure to look for libraries in ${libdir}, not just in /tools/lib:
sed -i '/EXP_LIB_SPEC=/s@${exec_prefix}/lib@${libdir}@' configure
Fix a bug that can result in false failures during the GCC test suite run:
patch -Np1 -i ../expect-5.43.0-spawn-2.patch
Now prepare Expect for compilation:
./configure --prefix=/tools --with-tcl=/tools/lib \ --with-tclinclude=/tools/include
The meaning of the configure options:
--with-tcl=/tools/lib
This ensures that the configure script finds the Tcl installation in the temporary testsuite-tools location.
--with-tclinclude=/tools/include
This explicitly tells Expect where to find Tcl's internal headers. Using this option avoids conditions where configure fails because it cannot automatically discover the location of the Tcl source directory.
Build the package:
make
Install the package:
make SCRIPTS="" install
The meaning of the make parameter:
SCRIPTS=""
This prevents installation of the supplementary expect scripts, which are not needed.
The DejaGNU package contains a framework for testing other programs.
Prepare DejaGNU for compilation:
./configure --prefix=/tools
Build and install the package:
make install
The Tree package contains a program that lists the directory structure in a graphical "tree" format. It is used by Udev for failures in its testsuite.
Compile the package:
make
Install the package:
make prefix=/tools install
The meaning of the make parameters:
prefix=/tools
This overrides the default prefix of /usr in the Makefile.
In this chapter, we enter the building site and start constructing the CLFS system in earnest. The installation of this software is straightforward. Although in many cases the installation instructions could be made shorter and more generic, we have opted to provide the full instructions for every package to minimize the possibilities for mistakes. The key to learning what makes a Linux system work is to know what each package is used for and why the user (or the system) needs it. For every installed package, a summary of its contents is given, followed by concise descriptions of each program and library the package installed.
If using compiler optimizations, please review the optimization
hint at http://hints.cross-lfs.org/optimization.txt.
Compiler optimizations can make a program run slightly faster,
but they may also cause compilation difficulties and problems
when running the program. If a package refuses to compile when
using optimization, try to compile it without optimization and
see if that fixes the problem. Even if the package does compile
when using optimization, there is the risk it may have been
compiled incorrectly because of the complex interactions
between the code and build tools. Also note that the
-march
and -mtune
options may cause problems with the
toolchain packages (Binutils, GCC and Glibc). The small
potential gains achieved in using compiler optimizations are
often outweighed by the risks. First-time builders of CLFS are
encouraged to build without custom optimizations. The
subsequent system will still run very fast and be stable at the
same time.
The order that packages are installed in this chapter needs to
be strictly followed to ensure that no program accidentally
acquires a path referring to /tools
hard-wired into it. For the same
reason, do not compile packages in parallel. Compiling in
parallel may save time (especially on dual-CPU machines), but
it could result in a program containing a hard-wired path to
/tools
, which will cause the
program to stop working when that directory is removed.
To keep track of which package installs particular files, a package manager can be used. For a general overview of different styles of package managers, please take a look at the next page.
Package Management is an often-requested addition to the CLFS Book. A Package Manager allows tracking the installation of files making it easy to remove and upgrade packages. Before you begin to wonder, NO—this section will not talk about nor recommend any particular package manager. What it provides is a roundup of the more popular techniques and how they work. The perfect package manager for you may be among these techniques or may be a combination of two or more of these techniques. This section briefly mentions issues that may arise when upgrading packages.
Some reasons why no specific package manager is recommended in CLFS or BLFS include:
Dealing with package management takes the focus away from the goals of these books—teaching how a Linux system is built.
There are multiple solutions for package management, each having its strengths and drawbacks. Including one that satisfies all audiences is difficult.
There are some hints written on the topic of package management. Visit the Hints subproject and see if one of them fits your need.
A Package Manager makes it easy to upgrade to newer versions when they are released. Generally the instructions in the CLFS and BLFS Book can be used to upgrade to the newer versions. Here are some points that you should be aware of when upgrading packages, especially on a running system.
If one of the toolchain packages (Glibc, GCC or Binutils) needs to be upgraded to a newer minor version, it is safer to rebuild CLFS. Though you may be able to get by rebuilding all the packages in their dependency order, we do not recommend it. For example, if glibc-2.2.x needs to be updated to glibc-2.3.x, it is safer to rebuild. For micro version updates, a simple reinstallation usually works, but is not guaranteed. For example, upgrading from glibc-2.3.4 to glibc-2.3.5 will not usually cause any problems.
If a package containing a shared library is updated,
and if the name of the library changes, then all the
packages dynamically linked to the library need to be
recompiled to link against the newer library. (Note
that there is no correlation between the package
version and the name of the library.) For example,
consider a package foo-1.2.3 that installs a shared
library with name libfoo.so.1
. Say you upgrade the
package to a newer version foo-1.2.4 that installs a
shared library with name libfoo.so.2
. In this case, all
packages that are dynamically linked to libfoo.so.1
need to be recompiled to
link against libfoo.so.2
.
Note that you should not remove the previous libraries
until the dependent packages are recompiled.
If you are upgrading a running system, be on the lookout for packages that use cp instead of install to install files. The latter command is usually safer if the executable or library is already loaded in memory.
The following are some common package management techniques. Before making a decision on a package manager, do some research on the various techniques, particularly the drawbacks of the particular scheme.
Yes, this is a package management technique. Some folks do not find the need for a package manager because they know the packages intimately and know what files are installed by each package. Some users also do not need any package management because they plan on rebuilding the entire system when a package is changed.
This is a simplistic package management that does not need
any extra package to manage the installations. Each package
is installed in a separate directory. For example, package
foo-1.1 is installed in /usr/pkg/foo-1.1
and a symlink is made
from /usr/pkg/foo
to
/usr/pkg/foo-1.1
. When
installing a new version foo-1.2, it is installed in
/usr/pkg/foo-1.2
and the
previous symlink is replaced by a symlink to the new
version.
Environment variables such as PATH
, LD_LIBRARY_PATH
, MANPATH
, INFOPATH
and CPPFLAGS
need to be expanded
to include /usr/pkg/foo
. For
more than a few packages, this scheme becomes unmanageable.
This is a variation of the previous package management
technique. Each package is installed similar to the
previous scheme. But instead of making the symlink, each
file is symlinked into the /usr
hierarchy. This removes the need to
expand the environment variables. Though the symlinks can
be created by the user to automate the creation, many
package managers have been written using this approach. A
few of the popular ones include Stow, Epkg, Graft, and
Depot.
The installation needs to be faked, so that the package
thinks that it is installed in /usr
though in reality it is installed in
the /usr/pkg
hierarchy.
Installing in this manner is not usually a trivial task.
For example, consider that you are installing a package
libfoo-1.1. The following instructions may not install the
package properly:
./configure --prefix=/usr/pkg/libfoo/1.1 make make install
The installation will work, but the dependent packages may
not link to libfoo as you would expect. If you compile a
package that links against libfoo, you may notice that it
is linked to /usr/pkg/libfoo/1.1/lib/libfoo.so.1
instead of /usr/lib/libfoo.so.1
as you would expect.
The correct approach is to use the DESTDIR
strategy to fake installation of the
package. This approach works as follows:
./configure --prefix=/usr make make DESTDIR=/usr/pkg/libfoo/1.1 install
Most packages support this approach, but there are some
which do not. For the non-compliant packages, you may
either need to manually install the package, or you may
find that it is easier to install some problematic packages
into /opt
.
In this technique, a file is timestamped before the installation of the package. After the installation, a simple use of the find command with the appropriate options can generate a log of all the files installed after the timestamp file was created. A package manager written with this approach is install-log.
Though this scheme has the advantage of being simple, it has two drawbacks. If, during installation, the files are installed with any timestamp other than the current time, those files will not be tracked by the package manager. Also, this scheme can only be used when one package is installed at a time. The logs are not reliable if two packages are being installed on two different consoles.
In this approach, a library is preloaded before installation. During installation, this library tracks the packages that are being installed by attaching itself to various executables such as cp, install, mv and tracking the system calls that modify the filesystem. For this approach to work, all the executables need to be dynamically linked without the suid or sgid bit. Preloading the library may cause some unwanted side-effects during installation. Therefore, it is advised that one performs some tests to ensure that the package manager does not break anything and logs all the appropriate files.
In this scheme, the package installation is faked into a separate tree as described in the Symlink style package management. After the installation, a package archive is created using the installed files. This archive is then used to install the package either on the local machine or can even be used to install the package on other machines.
This approach is used by most of the package managers found in the commercial distributions. Examples of package managers that follow this approach are RPM (which, incidentally, is required by the Linux Standard Base Specification), pkg-utils, Debian's apt, and Gentoo's Portage system. A hint describing how to adopt this style of package management for CLFS systems is located at http://hints.cross-lfs.org//fakeroot.txt.
In the final-system build, you are no longer cross-compiling so it is possible to run package testsuites. Some test suites are more important than others. For example, the test suites for the core toolchain packages—GCC, Binutils, and Glibc—are of the utmost importance due to their central role in a properly functioning system. The test suites for GCC and Glibc can take a very long time to complete, especially on slower hardware, but are strongly recommended.
A common issue with running the test suites for Binutils and
GCC is running out of pseudo terminals (PTYs). This can result
in a high number of failing tests. This may happen for several
reasons, but the most likely cause (if you chrooted) is that
the host system does not have the devpts
file system set up correctly. This
issue is discussed in greater detail at http://trac.cross-lfs.org/wiki/faq#no-ptys.
Sometimes package test suites will fail, but for reasons which the developers are aware of and have deemed non-critical. Consult the logs located at http://cross-lfs.org/testsuite-logs/clfs-1.1.0/ to verify whether or not these failures are expected. This site is valid for all tests throughout this book.
The Perl package contains the Practical Extraction and Report Language.
The following patch causes makedepend.sh to also remove
<command-line>
as well as
<command line>
:
patch -Np1 -i ../perl-5.8.8-gcc42_fix-1.patch
The following patch prevents perl from including asm/page.h which will no longer be available in headers provided by kernel 2.6.25 and forward:
patch -Np1 -i ../perl-5.8.8-no_page_h-1.patch
First adapt some hard-wired paths to the C library by applying the following patch:
patch -Np1 -i ../perl-5.8.8-libc-2.patch
Prepare Perl for compilation (make sure to get the 'Data/Dumper Fcntl IO POSIX' part of the command correct—they are all letters):
./configure.gnu --prefix=/tools \ -Dstatic_ext='Data/Dumper IO Fcntl POSIX' -Dcc="gcc"
The meaning of the configure option:
-Dstatic_ext='Data/Dumper IO Fcntl
POSIX'
This tells Perl to build the minimum set of static extensions needed for installing and testing the Glibc and Coreutils packages later in this chapter.
Now we are ready to make our perl utilities:
make perl utilities
Although Perl comes with a test suite, it is not recommended to run it at this point. Only part of Perl was built and running make test now will cause the rest of Perl to be built as well, which is unnecessary at this point. The test suite can be run later in this chapter if desired.
Install these tools and their libraries:
cp -v perl pod/pod2man /tools/bin install -dv /tools/lib/perl5/5.8.8 cp -Rv lib/* /tools/lib/perl5/5.8.8
Finally, create a necessary symlink:
ln -sv /tools/bin/perl /usr/bin
Details on this package are located in Section 10.22.2, “Contents of Perl.”
The Linux Kernel contains a make target that installs “sanitized” kernel headers.
For this step you will need the kernel tarballs.
The following patch includes spitfire.h outside of kernel space in elf.h. It also adds spitfire.h to the list of headers installed on the system.
patch -Np1 -i ../linux-2.6.24.7-elf_spitfire_fix-1.patch
Install the header files that are common to all architectures:
make mrproper make headers_check make INSTALL_HDR_PATH=dest headers_install cp -rv dest/include/* /usr/include
The Man-pages package contains over 1,200 man pages.
Install Man-pages by running:
make install
This package contains man pages that describe the following: POSIX headers (section 0p), POSIX utilities (section 1p), POSIX functions (section 3p), user commands (section 1), system calls (section 2), libc calls (section 3), device information (section 4), file formats (section 5), games (section 6), conventions and macro packages (section 7), system administration (section 8), and kernel (section 9). |
The Glibc package contains the main C library. This library provides the basic routines for allocating memory, searching directories, opening and closing files, reading and writing files, string handling, pattern matching, arithmetic, and so on.
Some packages outside of CLFS suggest installing GNU
libiconv in order to translate data from one encoding to
another. The project's home page (http://www.gnu.org/software/libiconv/)
says “This library provides an
iconv()
implementation, for
use on systems which don't have one, or whose
implementation cannot convert from/to
Unicode.” Glibc provides an iconv()
implementation and can convert
from/to Unicode, therefore libiconv is not required on a
CLFS system.
The Glibc build system is self-contained and will install
perfectly, even though the compiler specs file and linker are
still pointing at /tools
. The
specs and linker cannot be adjusted before the Glibc install
because the Glibc Autoconf tests would give false results and
defeat the goal of achieving a clean build.
The following patches merges all updates from the 2.7 Branch from the Glibc developers:
patch -Np1 -i ../glibc-2.7-branch_update-1A.patch
The following patch fixes an issue that can cause localdef to segfault:
patch -Np1 -i ../glibc-2.7-localedef_segfault-1.patch
The Glibc documentation recommends building Glibc outside of the source directory in a dedicated build directory:
mkdir -v ../glibc-build cd ../glibc-build
For TLS support on the Sparc64 we will need to add the
following lines to config.cache
:
echo "libc_cv_sparc64_tls=yes" >> config.cache
Tell Glibc to install its libraries into /lib
:
echo "slibdir=/lib" >> configparms
Prepare Glibc for compilation:
CC="gcc ${BUILD64}" ../glibc-2.7/configure --prefix=/usr \ --disable-profile --enable-add-ons --enable-kernel=2.6.0 \ --libexecdir=/usr/lib/glibc --libdir=/usr/lib \ --cache-file=config.cache
The meaning of the new configure option:
--libexecdir=/usr/lib/glibc
This changes the location of the pt_chown program from
its default of /usr/libexec
to /usr/lib/glibc
.
Compile the package:
make
The test suite for Glibc is considered critical. Do not skip it under any circumstance.
Test the results:
make -k check >glibc-check-log 2>&1 ; grep Error glibc-check-log
The Glibc test suite is highly dependent on certain functions
of the host system, in particular the kernel. The
posix/annexc test normally fails and you should see
Error 1 (ignored)
in the output.
Apart from this, the Glibc test suite is always expected to
pass. However, in certain circumstances, some failures are
unavoidable. If a test fails because of a missing program (or
missing symbolic link), or a segfault, you will see an error
code greater than 127 and the details will be in the log.
More commonly, tests will fail with Error 2
- for these, the contents of the
corresponding .out
file, e.g.
posix/annexc.out
may be
informative. Here is a list of the most common issues:
The math tests sometimes fail. Certain optimization settings are known to be a factor here.
If you have mounted the CLFS partition with the
noatime
option,
the atime test
will fail. As mentioned in Section 2.4,
“Mounting the New Partition”, do not
use the noatime
option while building CLFS.
When running on older and slower hardware, some tests can fail because of test timeouts being exceeded.
Though it is a harmless message, the install stage of Glibc
will complain about the absence of /etc/ld.so.conf
. Prevent this warning with:
touch /etc/ld.so.conf
Install the package:
make install
The stubs.h header installed by glibc looks for stubs-32.h and stubs-64.h. This configuration of glibc only generates stubs-64.h. Fix this with the following:
mv -v /usr/include/gnu/stubs{-64,}.h
The locales that can make the system respond in a different language were not installed by the above command. Install them with:
make localedata/install-locales
To save time, an alternative to running the previous command
(which generates and installs every locale listed in the
glibc-2.7/localedata/SUPPORTED file) is to install only those
locales that are wanted and needed. This can be achieved by
using the localedef command.
Information on this command is located in the INSTALL
file in the Glibc source. However,
there are a number of locales that are essential in order for
the tests of future packages to pass, in particular, the
libstdc++ tests from
GCC. The following instructions, instead of the install-locales
target used
above, will install the minimum set of locales necessary for
the tests to run successfully:
mkdir -pv /usr/lib/locale localedef -i cs_CZ -f UTF-8 cs_CZ.UTF-8 localedef -i de_DE -f ISO-8859-1 de_DE localedef -i de_DE@euro -f ISO-8859-15 de_DE@euro localedef -i en_HK -f ISO-8859-1 en_HK localedef -i en_PH -f ISO-8859-1 en_PH localedef -i en_US -f ISO-8859-1 en_US localedef -i es_MX -f ISO-8859-1 es_MX localedef -i fa_IR -f UTF-8 fa_IR localedef -i fr_FR -f ISO-8859-1 fr_FR localedef -i fr_FR@euro -f ISO-8859-15 fr_FR@euro localedef -i it_IT -f ISO-8859-1 it_IT localedef -i ja_JP -f EUC-JP ja_JP
Some locales installed by the make localedata/install-locales command above are not properly supported by some applications that are in the CLFS and BLFS books. Because of the various problems that arise due to application programmers making assumptions that break in such locales, CLFS should not be used in locales that utilize multibyte character sets (including UTF-8) or right-to-left writing order. Numerous unofficial and unstable patches are required to fix these problems, and it has been decided by the CLFS developers not to support such complex locales at this time. This applies to the ja_JP and fa_IR locales as well—they have been installed only for GCC and Gettext tests to pass, and the watch program (part of the Procps package) does not work properly in them. Various attempts to circumvent these restrictions are documented in internationalization-related hints.
The /etc/nsswitch.conf
file
needs to be created because, although Glibc provides defaults
when this file is missing or corrupt, the Glibc defaults do
not work well in a networked environment. The time zone also
needs to be configured.
Create a new file /etc/nsswitch.conf
by running the
following:
cat > /etc/nsswitch.conf << "EOF"
# Begin /etc/nsswitch.conf
passwd: files
group: files
shadow: files
hosts: files dns
networks: files
protocols: files
services: files
ethers: files
rpc: files
# End /etc/nsswitch.conf
EOF
To determine the local time zone, run the following script:
tzselect
After answering a few questions about the location, the
script will output the name of the time zone (e.g.,
EST5EDT or
Canada/Eastern). Then
create the /etc/localtime
file
by running:
cp -v --remove-destination /usr/share/zoneinfo/[xxx]
\
/etc/localtime
Replace [xxx]
with
the name of the time zone that tzselect provided (e.g.,
Canada/Eastern).
The meaning of the cp option:
--remove-destination
This is needed to force removal of the already existing
symbolic link. The reason for copying the file instead
of using a symlink is to cover the situation where
/usr
is on a separate
partition. This could be important when booted into
single user mode.
By default, the dynamic loader (/lib/ld-linux.so.2
) searches through
/lib
and /usr/lib
for dynamic libraries that are
needed by programs as they are run. However, if there are
libraries in directories other than /lib
and /usr/lib
, these need to be added to the
/etc/ld.so.conf
file in order
for the dynamic loader to find them. Two directories that are
commonly known to contain additional libraries are
/usr/local/lib
and /opt/lib
, so add those directories to the
dynamic loader's search path.
Create a new file /etc/ld.so.conf
by running the following:
cat > /etc/ld.so.conf << "EOF"
# Begin /etc/ld.so.conf
/usr/local/lib
/opt/lib
# End /etc/ld.so.conf
EOF
Can be used to create a stack trace when a program terminates with a segmentation fault |
|
Generates message catalogues |
|
Displays the system configuration values for file system specific variables |
|
Gets entries from an administrative database |
|
Performs character set conversion |
|
Creates fastloading iconv module configuration files |
|
Configures the dynamic linker runtime bindings |
|
Reports which shared libraries are required by each given program or shared library |
|
Assists ldd with object files |
|
Tells the compiler to enable or disable the use of POSIX locales for built-in operations |
|
Compiles locale specifications |
|
Reads and interprets a memory trace file and displays a summary in human-readable format |
|
A daemon that provides a cache for the most common name service requests |
|
Dumps information generated by PC profiling |
|
A helper program for grantpt to set the owner, group and access permissions of a slave pseudo terminal |
|
Generates C code to implement the Remote Procecure Call (RPC) protocol |
|
Makes an RPC call to an RPC server |
|
A statically linked program that creates symbolic links |
|
Reads and displays shared object profiling data |
|
Asks the user about the location of the system and reports the corresponding time zone description |
|
Traces the execution of a program by printing the currently executed function |
|
The time zone dumper |
|
The time zone compiler |
|
The helper program for shared library executables |
|
Used by programs, such as Mozilla, to solve broken locales |
|
The segmentation fault signal handler |
|
An asynchronous name lookup library |
|
Provides the portability needed in order to run certain Berkey Software Distribution (BSD) programs under Linux |
|
The main C library |
|
The cryptography library |
|
The dynamic linking interface library |
|
A runtime library for g++ |
|
The Institute of Electrical and Electronic Engineers (IEEE) floating point library |
|
The mathematical library |
|
Contains code run at boot |
|
Used by memusage (included in Glibc, but not built in a base CLFS system as it has additional dependencies) to help collect information about the memory usage of a program |
|
The network services library |
|
The Name Service Switch libraries, containing functions for resolving host names, user names, group names, aliases, services, protocols, etc. |
|
Contains profiling functions used to track the amount of CPU time spent in specific source code lines |
|
The POSIX threads library |
|
Contains functions for creating, sending, and interpreting packets to the Internet domain name servers |
|
Contains functions providing miscellaneous RPC services |
|
Contains functions providing most of the interfaces specified by the POSIX.1b Realtime Extension |
|
Contains functions useful for building debuggers for multi-threaded programs |
|
Contains code for “standard” functions used in many different Unix utilities |
Now we amend the GCC specs file so that it points to the new dynamic linker. A perl command accomplishes this:
gcc -dumpspecs | \ perl -p -e 's@/tools/lib/ld@/lib/ld@g;' \ -e 's@\*startfile_prefix_spec:\n@$_/usr/lib/ @g;' > \ $(dirname $(gcc --print-libgcc-file-name))/specs
It is a good idea to visually inspect the specs file to verify the intended change was actually made.
Note that /lib
is now the prefix
of our dynamic linker.
It is imperative at this point to stop and ensure that the basic functions (compiling and linking) of the adjusted toolchain are working as expected. To do this, perform a sanity check:
echo 'main(){}' > dummy.c gcc dummy.c readelf -l a.out | grep ': /lib'
If everything is working correctly, there should be no errors, and the output of the last command will be:
[Requesting program interpreter: /lib/ld-linux.so.2]
Note that /lib
is now the
prefix of our dynamic linker.
If the output does not appear as shown above or is not received at all, then something is seriously wrong. Investigate and retrace the steps to find out where the problem is and correct it. The most likely reason is that something went wrong with the specs file amendment above. Any issues will need to be resolved before continuing on with the process.
Once everything is working correctly, clean up the test files:
rm -v dummy.c a.out
The Binutils package contains a linker, an assembler, and other tools for handling object files.
Verify that the PTYs are working properly inside the build environment. Check that everything is set up correctly by performing a simple test:
expect -c "spawn ls"
If the following message shows up, the environment is not set up for proper PTY operation:
The system has no more ptys.
Ask your system administrator to create more.
This issue needs to be resolved before running the test suites for Binutils and GCC.
The following patches merges all updates from the 2.18 Branch from the Binutils developers:
patch -Np1 -i ../binutils-2.18-branch_update-3.patch
Libiberty uses gcc
-print-multi-os-directory to determine where
to install libiberty.a. Because our temporary gcc is still
multilib-aware, the command returns ../lib64
which causes the archive to be
installed into /usr/lib64. The following sed will prevent
this:
sed -i 's%\(^MULTIOSDIR = \).*%\1 ../lib%' libiberty/Makefile.in
The Binutils documentation recommends building Binutils outside of the source directory in a dedicated build directory:
mkdir -v ../binutils-build cd ../binutils-build
Prepare Binutils for compilation:
../binutils-2.18/configure --prefix=/usr \ --libdir=/usr/lib --enable-shared \ --disable-multilib --enable-64-bit-bfd
Compile the package:
make configure-host
During make configure-host you may receive the following error message. It is safe to ignore.
WARNING: `flex' is missing on your system. You should only
need it if you modified a `.l' file. You may need the `Flex'
package in order for those modifications to take effect. You
can get `Flex' from any GNU archive site.
make tooldir=/usr
The meaning of the make parameter:
tooldir=/usr
Normally, the tooldir (the directory where the
executables will ultimately be located) is set to
$(exec_prefix)/$(target_alias)
.
Because this is a custom system, this target-specific
directory in /usr
is not
required.
The test suite for Binutils is considered critical. Do not skip it under any circumstance.
Test the results:
make check
Now that the tests have completed, remove the symlinks in /usr/lib64 - they should be the only things in that directory, so we can remove it without force :
rm -v /usr/lib64/libstd*so* rmdir -v /usr/lib64
Install the package:
make tooldir=/usr install
Install the libiberty
header
file that is needed by some packages:
cp -v ../binutils-2.18/include/libiberty.h /usr/include
Translates program addresses to file names and line numbers; given an address and the name of an executable, it uses the debugging information in the executable to determine which source file and line number are associated with the address |
|
Creates, modifies, and extracts from archives |
|
An assembler that assembles the output of gcc into object files |
|
Used by the linker to de-mangle C++ and Java symbols and to keep overloaded functions from clashing |
|
Displays call graph profile data |
|
A linker that combines a number of object and archive files into a single file, relocating their data and tying up symbol references |
|
Lists the symbols occurring in a given object file |
|
Translates one type of object file into another |
|
Displays information about the given object file, with options controlling the particular information to display; the information shown is useful to programmers who are working on the compilation tools |
|
Generates an index of the contents of an archive and stores it in the archive; the index lists all of the symbols defined by archive members that are relocatable object files |
|
Displays information about ELF type binaries |
|
Lists the section sizes and the total size for the given object files |
|
Outputs, for each given file, the sequences of printable characters that are of at least the specified length (defaulting to four); for object files, it prints, by default, only the strings from the initializing and loading sections while for other types of files, it scans the entire file |
|
Discards symbols from object files |
|
Contains routines used by various GNU programs, including getopt, obstack, strerror, strtol, and strtoul |
|
The Binary File Descriptor library |
|
A library for dealing with opcodes—the “readable text” versions of instructions for the processor; it is used for building utilities like objdump. |
The GCC package contains the GNU compiler collection, which includes the C and C++ compilers.
The following patch enables fixes compilation errors with the kernel:
patch -Np1 -i ../gcc-4.2.4-PR31490-1.patch
Apply the following patch so that GCC links to /lib instead of /lib64:
patch -Np1 -i ../gcc-4.2.4-pure64-1.patch
Apply a sed
substitution that will suppress the installation of
libiberty.a
. The version of
libiberty.a
provided by
Binutils will be used instead:
sed -i 's/install_to_$(INSTALL_DEST) //' libiberty/Makefile.in
GCC provides a gccbug script which detects at compile time whether mktemp is present, and hardcodes the result in a test. If mktemp is not found, the script will fall back to using less random names for temporary files. We will be installing mktemp later, so the following sed will simulate its presence:
sed -i 's/@have_mktemp_command@/yes/' gcc/gccbug.in
The GCC documentation recommends building GCC outside of the source directory in a dedicated build directory:
mkdir -v ../gcc-build cd ../gcc-build
Prepare GCC for compilation:
../gcc-4.2.4/configure --prefix=/usr \ --libexecdir=/usr/lib --enable-shared --enable-threads=posix \ --enable-__cxa_atexit --enable-c99 --enable-long-long \ --enable-clocale=gnu --enable-languages=c,c++ \ --disable-multilib --disable-libstdcxx-pch
Compile the package:
make bootstrap
The test suite for GCC is considered critical. Do not skip it under any circumstance.
Test the results, but do not stop at errors:
make -k check
The -k
flag is used
to make the test suite run through to completion and not stop
at the first failure. The GCC test suite is very
comprehensive and is almost guaranteed to generate a few
failures. To receive a summary of the test suite results,
run:
../gcc-4.2.4/contrib/test_summary
For only the summaries, pipe the output through
grep -A7
Summ
.
A few unexpected failures cannot always be avoided. The GCC developers are usually aware of these issues, but have not resolved them yet.
Install the package:
make install
Some packages expect the C preprocessor to be installed in
the /lib
directory. To support
those packages, create this symlink:
ln -sv ../usr/bin/cpp /lib
Many packages use the name cc to call the C compiler. To satisfy those packages, create a symlink:
ln -sv gcc /usr/bin/cc
The C compiler |
|
The C preprocessor; it is used by the compiler to expand the #include, #define, and similar statements in the source files |
|
The C++ compiler |
|
The C++ compiler |
|
The C compiler |
|
A shell script used to help create useful bug reports |
|
A coverage testing tool; it is used to analyze programs to determine where optimizations will have the most effect |
|
Contains run-time support for gcc |
|
The libmudflap libraries are used by GCC for instrumenting pointer and array dereferencing operations. |
|
The standard C++ library |
|
Provides supporting routines for the C++ programming language |
The Sed package contains a stream editor.
Prepare Sed for compilation:
./configure --prefix=/usr --bindir=/bin --enable-html
The meaning of the new configure option:
--enable-html
This option tells Sed to build and install its HTML documentation.
Compile the package:
make
To test the results, issue: make check
.
Install the package:
make install
The E2fsprogs package contains the utilities for handling the
ext2
file system. It also
supports the ext3
journaling
file system.
The E2fsprogs documentation recommends that the package be built in a subdirectory of the source tree:
mkdir -v build cd build
Prepare E2fsprogs for compilation:
../configure --prefix=/usr --with-root-prefix="" \ --enable-elf-shlibs --disable-evms \ --with-cc=gcc
The meaning of the configure options:
--with-root-prefix=""
Certain programs (such as the e2fsck program) are
considered essential programs. When, for example,
/usr
is not mounted,
these programs still need to be available. They belong
in directories like /lib
and /sbin
. If this option
is not passed to E2fsprogs' configure, the programs are
installed into the /usr
directory.
--enable-elf-shlibs
This creates the shared libraries which some programs in this package use.
--disable-evms
This disables the building of the Enterprise Volume Management System (EVMS) plugin. This plugin is not up-to-date with the latest EVMS internal interfaces and EVMS is not installed as part of a base CLFS system, so the plugin is not required. See the EVMS website at http://evms.sourceforge.net/ for more information regarding EVMS.
Compile the package:
make
To test the results, issue: make check
.
Install the binaries, documentation and shared libraries:
make install
Install the static libraries and headers:
make install-libs
Searches a device (usually a disk partition) for bad blocks |
|
A command line utility to locate and print block device attributes |
|
Changes the attributes of files on an |
|
An error table compiler; it converts a table of
error-code names and messages into a C source file
suitable for use with the |
|
A file system debugger; it can be used to examine
and change the state of an |
|
Prints the super block and blocks group information for the file system present on a given device |
|
Is used to check, and optionally repair
|
|
Is used to save critical |
|
Displays or changes the file system label on the
|
|
Reports on how badly fragmented a particular file might be |
|
Finds a file system by label or Universally Unique Identifier (UUID) |
|
Is used to check, and optionally repair, file systems |
|
By default checks |
|
By default checks |
|
Saves the output of a command in a log file |
|
Lists the attributes of files on a second extended file system |
|
Converts a table of command names and help messages
into a C source file suitable for use with the
|
|
Creates an |
|
By default creates |
|
By default creates |
|
Used to create a |
|
Can be used to enlarge or shrink an |
|
Adjusts tunable file system parameters on an
|
|
The uuidd daemon is used by the UUID library to generate universally unique identifiers (UUIDs), especially time-based UUID's in a secure and guaranteed-unique fashion, even in the face of large numbers of threads trying to grab UUID's running on different CPU's. |
|
Creates new UUIDs. Each new UUID can reasonably be considered unique among all UUIDs created, on the local system and on other systems, in the past and in the future |
|
Contains routines for device identification and token extraction |
|
The common error display routine |
|
Used by dumpe2fs, chattr, and lsattr |
|
Contains routines to enable user-level programs to
manipulate an |
|
Used by debugfs |
|
Contains routines for generating unique identifiers for objects that may be accessible beyond the local system |
The Coreutils package contains utilities for showing and setting the basic system characteristics.
Prevent Coreutils from installing binaries that will be installed by other packages:
patch -Np1 -i ../coreutils-6.9-suppress_uptime_kill_su-1.patch
A known issue with the uname program from this
package is that the -p
switch
always returns unknown
.
The following patch fixes this behavior for all
architectures:
patch -Np1 -i ../coreutils-6.9-uname-1.patch
The following command renames the internal implementation of futimens to gl_futimens as newer versions of Glibc provide an incompatible version:
sed -i "s/futimens/gl_&/" $(grep -lr futimens *)
Now prepare Coreutils for compilation:
./configure --prefix=/usr
Compile the package:
make
The test suite of Coreutils makes several assumptions about the presence of system users and groups that are not valid within the minimal environment that exists at the moment. Therefore, additional items need to be set up before running the tests. Skip down to “Install the package” if not running the test suite.
Create two dummy
groups and a
dummy
user:
echo "dummy1:x:1000:" >> /etc/group echo "dummy2:x:1001:dummy" >> /etc/group echo "dummy:x:1000:1000::/root:/bin/bash" >> /etc/passwd
Now the test suite is ready to be run. First, run the tests
that are meant to be run as user root
:
make NON_ROOT_USERNAME=dummy check-root
Then run the remainder of the tests as the dummy
user:
src/su dummy -c "make RUN_EXPENSIVE_TESTS=yes check"
When testing is complete, remove the dummy
user and groups:
sed -i '/dummy/d' /etc/passwd /etc/group
Install the package:
make install
Move programs to the locations specified by the FHS:
mv -v /usr/bin/{cat,chgrp,chmod,chown,cp,date} /bin mv -v /usr/bin/{dd,df,echo,false,hostname,ln,ls,mkdir,mknod} /bin mv -v /usr/bin/{mv,pwd,rm,rmdir,stty,true,uname} /bin mv -v /usr/bin/chroot /usr/sbin
Other Coreutils programs are used by some of the scripts in
the CLFS-Bootscripts package. As /usr
may not be available during the early
stages of booting, those binaries need to be on the root
partition:
mv -v /usr/bin/{[,basename,head,install,nice} /bin mv -v /usr/bin/{readlink,sleep,sync,test,touch} /bin ln -svf ../../bin/install /usr/bin
Base64 encode/decode data and print to standard output |
|
Strips any path and a given suffix from a file name |
|
Concatenates files to standard output |
|
Changes the group ownership of files and directories |
|
Changes the permissions of each file to the given mode; the mode can be either a symbolic representation of the changes to make or an octal number representing the new permissions |
|
Changes the user and/or group ownership of files and directories |
|
Runs a command with the specified directory as the
|
|
Prints the Cyclic Redundancy Check (CRC) checksum and the byte counts of each specified file |
|
Compares two sorted files, outputting in three columns the lines that are unique and the lines that are common |
|
Copies files |
|
Splits a given file into several new files, separating them according to given patterns or line numbers and outputting the byte count of each new file |
|
Prints sections of lines, selecting the parts according to given fields or positions |
|
Displays the current time in the given format, or sets the system date |
|
Copies a file using the given block size and count, while optionally performing conversions on it |
|
Reports the amount of disk space available (and used) on all mounted file systems, or only on the file systems holding the selected files |
|
Lists the contents of each given directory (the same as the ls command) |
|
Outputs commands to set the |
|
Strips the non-directory suffix from a file name |
|
Reports the amount of disk space used by the current directory, by each of the given directories (including all subdirectories) or by each of the given files |
|
Displays the given strings |
|
Runs a command in a modified environment |
|
Converts tabs to spaces |
|
Evaluates expressions |
|
Prints the prime factors of all specified integer numbers |
|
Does nothing, unsuccessfully; it always exits with a status code indicating failure |
|
Reformats the paragraphs in the given files |
|
Wraps the lines in the given files |
|
Reports a user's group memberships |
|
Prints the first ten lines (or the given number of lines) of each given file |
|
Reports the numeric identifier (in hexadecimal) of the host |
|
Reports or sets the name of the host |
|
Reports the effective user ID, group ID, and group memberships of the current user or specified user |
|
Copies files while setting their permission modes and, if possible, their owner and group |
|
Joins the lines that have identical join fields from two separate files |
|
Creates a hard link with the given name to a file |
|
Makes hard links or soft (symbolic) links between files |
|
Reports the current user's login name |
|
Lists the contents of each given directory |
|
Reports or checks Message Digest 5 (MD5) checksums |
|
Creates directories with the given names |
|
Creates First-In, First-Outs (FIFOs), a “named pipe” in UNIX parlance, with the given names |
|
Creates device nodes with the given names; a device node is a character special file, a block special file, or a FIFO |
|
Moves or renames files or directories |
|
Runs a program with modified scheduling priority |
|
Numbers the lines from the given files |
|
Runs a command immune to hangups, with its output redirected to a log file |
|
Dumps files in octal and other formats |
|
Merges the given files, joining sequentially corresponding lines side by side, separated by tab characters |
|
Checks if file names are valid or portable |
|
Is a lightweight finger client; it reports some information about the given users |
|
Paginates and columnates files for printing |
|
Prints the environment |
|
Prints the given arguments according to the given format, much like the C printf function |
|
Produces a permuted index from the contents of the given files, with each keyword in its context |
|
Reports the name of the current working directory |
|
Reports the value of the given symbolic link |
|
Removes files or directories |
|
Removes directories if they are empty |
|
Prints a sequence of numbers within a given range and with a given increment |
|
Prints or checks 160-bit Secure Hash Algorithm 1 (SHA1) checksums |
|
Prints or checks SHA224 checksums |
|
Prints or checks SHA256 checksums |
|
Prints or checks SHA384 checksums |
|
Prints or checks SHA512 checksums |
|
Overwrites the given files repeatedly with complex patterns, making it difficult to recover the data |
|
Write a random permutation of the input lines to standard output or a file |
|
Pauses for the given amount of time |
|
Sorts the lines from the given files |
|
Splits the given file into pieces, by size or by number of lines |
|
Displays file or filesystem status |
|
Sets or reports terminal line settings |
|
Prints checksum and block counts for each given file |
|
Flushes file system buffers; it forces changed blocks to disk and updates the super block |
|
Concatenates the given files in reverse |
|
Prints the last ten lines (or the given number of lines) of each given file |
|
Reads from standard input while writing both to standard output and to the given files |
|
Compares values and checks file types |
|
Changes file timestamps, setting the access and modification times of the given files to the current time; files that do not exist are created with zero length |
|
Translates, squeezes, and deletes the given characters from standard input |
|
Does nothing, successfully; it always exits with a status code indicating success |
|
Performs a topological sort; it writes a completely ordered list according to the partial ordering in a given file |
|
Reports the file name of the terminal connected to standard input |
|
Reports system information |
|
Converts spaces to tabs |
|
Discards all but one of successive identical lines |
|
Removes the given file |
|
Reports the names of the users currently logged on |
|
Is the same as ls -l |
|
Reports the number of lines, words, and bytes for each given file, as well as a total line when more than one file is given |
|
Reports who is logged on |
|
Reports the user name associated with the current effective user ID |
|
Repeatedly outputs “y” or a given string until killed |
The Iana-Etc package provides data for network services and protocols.
The following command converts the raw data provided by IANA
into the correct formats for the /etc/protocols
and /etc/services
data files:
make
This package does not come with a test suite.
Install the package:
make install
The M4 package contains a macro processor.
Prepare M4 for compilation:
./configure --prefix=/usr
Compile the package:
make
To test the results, issue: make check
.
Install the package:
make install
copies the given files while expanding the macros that they contain. These macros are either built-in or user-defined and can take any number of arguments. Besides performing macro expansion, m4 has built-in functions for including named files, running Unix commands, performing integer arithmetic, manipulating text, recursion, etc. The m4 program can be used either as a front-end to a compiler or as a macro processor in its own right. |
The Bison package contains a parser generator.
Prepare Bison for compilation:
./configure --prefix=/usr
The configure system causes bison to be built without support for internationalization of error messages if a bison program is not already in $PATH. The following addition will correct this:
echo '#define YYENABLE_NLS 1' >> config.h
Compile the package:
make
To test the results, issue: make check
.
Install the package:
make install
Generates, from a series of rules, a program for analyzing the structure of text files; Bison is a replacement for Yacc (Yet Another Compiler Compiler) |
|
A wrapper for bison, meant for
programs that still call yacc instead of
bison; it calls
bison
with the |
|
The Yacc library containing implementations of Yacc-compatible yyerror and main functions; this library is normally not very useful, but POSIX requires it |
The Ncurses package contains libraries for terminal-independent handling of character screens.
The following patches merges all updates from the 5.6 Branch from the Ncurses developers:
patch -Np1 -i ../ncurses-5.6-branch_update-3.patch
Prepare Ncurses for compilation:
./configure --prefix=/usr --libdir=/lib \ --with-shared --without-debug
Compile the package:
make
This package does not come with a test suite.
Install the package:
make install
Move the Ncurses static libraries to the proper location:
mv -v /lib/lib{panel,menu,form,ncurses,ncurses++,curses}.a /usr/lib
Create symlinks in /usr/lib:
rm -v /lib/lib{ncurses,menu,panel,form,curses}.so ln -svf ../../lib/libncurses.so.5 /usr/lib/libcurses.so ln -svf ../../lib/libncurses.so.5 /usr/lib/libncurses.so ln -svf ../../lib/libmenu.so.5 /usr/lib/libmenu.so ln -svf ../../lib/libpanel.so.5 /usr/lib/libpanel.so ln -svf ../../lib/libform.so.5 /usr/lib/libform.so
Give the Ncurses dynamic libraries execute permissions:
chmod -v 755 /lib/lib{panel,menu,form,ncurses}.so.5.6
Converts a termcap description into a terminfo description |
|
Clears the screen, if possible |
|
Compares or prints out terminfo descriptions |
|
Converts a terminfo description into a termcap description |
|
Provides configuration information for ncurses |
|
Reinitializes a terminal to its default values |
|
The terminfo action checker; it is mainly used to test the accuracy of an entry in the terminfo database |
|
The terminfo entry-description compiler that translates a terminfo file from source format into the binary format needed for the ncurses library routines. A terminfo file contains information on the capabilities of a certain terminal |
|
Lists all available terminal types, giving the primary name and description for each |
|
Makes the values of terminal-dependent capabilities available to the shell; it can also be used to reset or initialize a terminal or report its long name |
|
Can be used to initialize terminals |
|
A link to |
|
Contains functions to display text in many complex ways on a terminal screen; a good example of the use of these functions is the menu displayed during the kernel's make menuconfig |
|
Contains functions to implement forms |
|
Contains functions to implement menus |
|
Contains functions to implement panels |
The Procps package contains programs for monitoring processes.
Compile the package:
make CC=gcc
This package does not come with a test suite.
Install the package:
make install
Reports the amount of free and used memory (both physical and swap memory) in the system |
|
Sends signals to processes |
|
Looks up processes based on their name and other attributes |
|
Signals processes based on their name and other attributes |
|
Reports the memory map of the given process |
|
Lists the current running processes |
|
Reports the current working directory of a process |
|
Sends signals to processes matching the given criteria |
|
Displays detailed kernel slab cache information in real time |
|
Changes the scheduling priority of processes matching the given criteria |
|
Modifies kernel parameters at run time |
|
Prints a graph of the current system load average |
|
Displays a list of the most CPU intensive processes; it provides an ongoing look at processor activity in real time |
|
Reports how long the system has been running, how many users are logged on, and the system load averages |
|
Reports virtual memory statistics, giving information about processes, memory, paging, block Input/Output (IO), traps, and CPU activity |
|
Shows which users are currently logged on, where, and since when |
|
Runs a given command repeatedly, displaying the first screen-full of its output; this allows a user to watch the output change over time |
|
Contains the functions used by most programs in this package |
The Libtool package contains the GNU generic library support script. It wraps the complexity of using shared libraries in a consistent, portable interface.
Prepare Libtool for compilation:
./configure --prefix=/usr
Compile the package:
make
To test the results, issue: make check
.
Install the package:
make install
The Flex package contains a utility for generating programs that recognize patterns in text.
Prepare Flex for compilation:
./configure --prefix=/usr
Compile the package:
make
To test the results, issue: make check
.
Install the package:
make install
There are some packages that expect to find the lex
library in /usr/lib
. Create a symlink to account for
this:
ln -sv libfl.a /usr/lib/libl.a
A few programs do not know about flex yet and try to run its
predecessor, lex. To support those
programs, create a wrapper script named lex
that calls flex
in lex emulation mode:
cat > /usr/bin/lex << "EOF"
#!/bin/sh
# Begin /usr/bin/lex
exec /usr/bin/flex -l "$@"
# End /usr/bin/lex
EOF
chmod -v 755 /usr/bin/lex
The IPRoute2 package contains programs for basic and advanced IPV4-based networking.
The arpd binary included in this package is dependent on Berkeley DB. Because arpd is not a very common requirement on a base Linux system, remove the dependency on Berkeley DB by applying the sed command below. If the arpd binary is needed, instructions for compiling Berkeley DB can be found in the BLFS Book at http://cblfs.cross-lfs.org/index.php/Berkeley_DB.
sed -i '/^TARGETS/s@arpd@@g' misc/Makefile
Compile the package:
make SBINDIR=/sbin
The meaning of the make option:
SBINDIR=/sbin
This ensures that the IPRoute2 binaries will install
into /sbin
. This is the
correct location according to the FHS, because some of
the IPRoute2 binaries are used by the CLFS-Bootscripts
package.
This package does not come with a test suite.
Install the package:
make SBINDIR=/sbin install
Connection status utility |
|
A shell script wrapper for the ip command |
|
Shows the interface statistics, including the amount of transmitted and received packets by interface |
|
The main executable. It has several different functions:
ip link ip addr allows users to look at addresses and their properties, add new addresses, and delete old ones ip neighbor allows users to look at neighbor bindings and their properties, add new neighbor entries, and delete old ones ip rule allows users to look at the routing policies and change them ip route allows users to look at the routing table and change routing table rules ip tunnel allows users to look at the IP tunnels and their properties, and change them ip maddr allows users to look at the multicast addresses and their properties, and change them ip mroute allows users to set, change, or delete the multicast routing ip monitor allows users to continously monitor the state of devices, addresses and routes |
|
Provides Linux network statistics. It is a generalized and more feature-complete replacement for the old rtstat program |
|
Shows network statistics |
|
A component of ip route. This is for flushing the routing tables |
|
A component of ip route. This is for listing the routing tables |
|
Displays the contents of |
|
Route monitoring utility |
|
Converts the output of ip -o back into a readable form |
|
Route status utility |
|
Similar to the netstat command; shows active connections |
|
Traffic Controlling Executable; this is for Quality Of Service (QOS) and Class Of Service (COS) implementations tc qdisc allows users to setup the queueing discipline tc class allows users to setup classes based on the queuing discipline scheduling tc estimator allows users to estimate the network flow into a network tc filter allows users to setup the QOS/COS packet filtering tc policy allows users to setup the QOS/COS policies |
The Perl package contains the Practical Extraction and Report Language.
The following patch causes makedepend.sh to also remove
<command-line>
as well as
<command line>
:
patch -Np1 -i ../perl-5.8.8-gcc42_fix-1.patch
The following patch prevents perl from including asm/page.h which will no longer be available in headers provided by kernel 2.6.25 and forward:
patch -Np1 -i ../perl-5.8.8-no_page_h-1.patch
The following patch fixes known vulnerabilities in perl:
patch -Np1 -i ../perl-5.8.8-security_fixes-1.patch
The following sed causes DynaLoader.a
to be built with -fPIC so it
can be linked into a shared library later:
sed -i -e "s@pldlflags=''@pldlflags=\"\$cccdlflags\"@g" \ -e "s@static_target='static'@static_target='static_pic'@g" Makefile.SH
If you are following the boot method you will need to enable the loopback device as well as set a hostname for some of the tests:
ip link set lo up hostname clfs
Before starting to configure, create a basic /etc/hosts
file which will be referenced by
one of Perl's configuration files as well as used by the
testsuite:
echo "127.0.0.1 localhost $(hostname)" > /etc/hosts
To have full control over the way Perl is set up, you can run the interactive Configure script and hand-pick the way this package is built. If you prefer instead to use the defaults that Perl auto-detects, prepare Perl for compilation with:
CC=gcc ./configure.gnu --prefix=/usr \ -Dman1dir=/usr/share/man/man1 \ -Dman3dir=/usr/share/man/man3 \ -Dpager="/bin/less -isR" \ -Dusethreads
The meaning of the configure option:
-Dpager="/bin/less
-isR"
This corrects an error in the way that perldoc invokes the less program.
-Dman1dir=/usr/share/man/man1
-Dman3dir=/usr/share/man/man3
Since Groff is not installed yet, configure.gnu thinks that we do not want man pages for Perl. Issuing these parameters overrides this decision.
-Dusethreads
This tells Perl to use threads.
Compile the package:
make
To test the results, issue: make test
.
Install the package:
make install
Translates awk to Perl |
|
Dumps C structures as generated from cc -g -S |
|
Shell script that provides a command interface to CPAN.pm |
|
Displays Perl profile data |
|
Builds a Perl extension for the Encode module from either Unicode Character Mappings or Tcl Encoding Files |
|
Translates find commands to Perl |
|
Converts |
|
Converts |
|
Can be used to configure the |
|
A shell script for examining installed Perl modules, and can even create a tarball from an installed module |
|
Combines some of the best features of C, sed, awk and sh into a single swiss-army-knife language |
|
A hard link to perl |
|
Used to generate bug reports about Perl, or the modules that come with it, and mail them |
|
Generates executables from Perl programs |
|
Displays a piece of documentation in pod format that is embedded in the Perl installation tree or in a Perl script |
|
The Perl Installation Verification Procedure; it can be used to verify that Perl and its libraries have been installed correctly |
|
A Perl version of the character encoding converter iconv |
|
A rough tool for converting Perl4 |
|
Converts files from pod format to HTML format |
|
Converts files from pod format to LaTeX format |
|
Converts pod data to formatted *roff input |
|
Converts pod data to formatted ASCII text |
|
Prints usage messages from embedded pod docs in files |
|
Checks the syntax of pod format documentation files |
|
Displays selected sections of pod documentation |
|
A command-line tool for running tests against Test::Harness |
|
A Perl version of the stream editor sed |
|
Dumps C structures as generated from cc -g -S stabs |
|
Translates sed to Perl |
|
Is used to force verbose warning diagnostics in Perl |
|
Converts Perl XS code into C code |
The Readline package is a set of libraries that offers command-line editing and history capabilities.
The following patch contains updates from the maintainer. The maintainer of Readline only releases these patches to fix serious issues:
patch -Np1 -i ../readline-5.2-fixes-4.patch
Prepare Readline for compilation:
./configure --prefix=/usr --libdir=/lib
Compile the package:
make SHLIB_XLDFLAGS=-lncurses
The meaning of the make option:
SHLIB_XLDFLAGS=-lncurses
This option forces Readline to link against the
libncurses
library.
This package does not come with a test suite.
Install the package:
make install
Give Readline's dynamic libraries more appropriate permissions:
chmod -v 755 /lib/lib{readline,history}.so*
Now move the static libraries to a more appropriate location:
mv -v /lib/lib{readline,history}.a /usr/lib
Next, remove the .so
files in
/lib
and relink them into
/usr/lib
.
rm -v /lib/lib{readline,history}.so ln -svf ../../lib/libreadline.so.5 /usr/lib/libreadline.so ln -svf ../../lib/libhistory.so.5 /usr/lib/libhistory.so
The Zlib package contains compression and decompression routines used by some programs.
This patch will add -fPIC to our build and allow us to build a static and shared library at the same time:
patch -Np1 -i ../zlib-1.2.3-fPIC-1.patch
Prepare Zlib for compilation:
./configure --prefix=/usr --shared
Compile the package:
make
To test the results, issue: make check
.
Install the package:
make install
The previous command installed two .so
files into /usr/lib
. We will move it into /lib
and then relink it to /usr/lib
:
mv -v /usr/lib/libz.so.* /lib ln -svf ../../lib/libz.so.1 /usr/lib/libz.so
Now we fix the permissions on the static library:
chmod -v 644 /usr/lib/libz.a
The Autoconf package contains programs for producing shell scripts that can automatically configure source code.
Prepare Autoconf for compilation:
./configure --prefix=/usr
Compile the package:
make
To test the results, issue: make check
. 6 tests are
skipped that use Automake. For full test coverage, Autoconf
can be re-tested after Automake has been installed.
Install the package:
make install
Produces shell scripts that automatically configure software source code packages to adapt to many kinds of Unix-like systems. The configuration scripts it produces are independent—running them does not require the autoconf program. |
|
A tool for creating template files of C #define statements for configure to use |
|
A wrapper for the M4 macro processor |
|
Automatically runs autoconf, autoheader, aclocal, automake, gettextize, and libtoolize in the correct order to save time when changes are made to autoconf and automake template files |
|
Helps to create a |
|
Modifies a |
|
Helps when writing |
The Automake package contains programs for generating Makefiles for use with Autoconf.
Prepare Automake for compilation:
./configure --prefix=/usr
Compile the package:
make
To test the results, issue: make check
.
Install the package:
make install
A script that installs aclocal-style M4 files |
|
Generates |
|
A hard link to aclocal |
|
A tool for automatically generating |
|
A hard link to automake |
|
A wrapper for compilers |
|
A script that attempts to guess the canonical triplet for the given build, host, or target architecture |
|
A configuration validation subroutine script |
|
A script for compiling a program so that dependency information is generated in addition to the desired output |
|
Byte-compiles Emacs Lisp code |
|
A script that installs a program, script, or data file |
|
A script that prints the modification time of a file or directory |
|
A script acting as a common stub for missing GNU programs during an installation |
|
A script that creates a directory tree |
|
Compiles a Python program |
|
A script to create a symlink tree of a directory tree |
|
A wrapper for lex and yacc |
The Bash package contains the Bourne-Again SHell.
If you downloaded the Bash documentation tarball and wish to install HTML documentation, issue the following commands:
tar -xvf ../bash-doc-3.2.tar.gz
The following patch contains updates from the maintainer. The maintainer of Bash only releases these patches to fix serious issues:
patch -Np1 -i ../bash-3.2-fixes-8.patch
Prepare Bash for compilation:
./configure --prefix=/usr --bindir=/bin \ --without-bash-malloc --with-installed-readline
The meaning of the configure option:
--with-installed-readline
This option tells Bash to use the readline
library that is already
installed on the system rather than using its own
readline version.
Compile the package:
make
To test the results, issue: make tests
.
Install the package:
make htmldir=/usr/share/doc/bash-3.2 install
Run the newly compiled bash program (replacing the one that is currently being executed):
exec /bin/bash --login +h
The parameters used make the bash process an interactive login shell and continue to disable hashing so that new programs are found as they become available.
A widely-used command interpreter; it performs many types of expansions and substitutions on a given command line before executing it, thus making this interpreter a powerful tool |
|
A shell script to help the user compose and mail standard formatted bug reports concerning bash |
|
A symlink to the bash program; when invoked as sh, bash tries to mimic the startup behavior of historical versions of sh as closely as possible, while conforming to the POSIX standard as well |
The Bzip2 package contains programs for compressing and decompressing files. Compressing text files with bzip2 yields a much better compression percentage than with the traditional gzip.
The Bzip2 package does not contain a configure script. Compile it with:
make -f Makefile-libbz2_so make clean
The -f
flag will
cause Bzip2 to be built using a different Makefile
file, in this case the
Makefile-libbz2_so
file, which
creates a dynamic libbz2.so
library and links the Bzip2 utilities against it.
Recompile the package using a non-shared library and test it:
make
Install the programs:
make PREFIX=/usr install
Install the shared bzip2 binary into the
/bin
directory, make some
necessary symbolic links, and clean up:
cp -v bzip2-shared /bin/bzip2 cp -av libbz2.so* /lib ln -sv ../../lib/libbz2.so.1.0 /usr/lib/libbz2.so rm -v /usr/bin/{bunzip2,bzcat,bzip2} ln -sv bzip2 /bin/bunzip2 ln -sv bzip2 /bin/bzcat
Decompresses bzipped files |
|
Decompresses to standard output |
|
Runs cmp on bzipped files |
|
Runs diff on bzipped files |
|
Runs grep on bzipped files |
|
Runs egrep on bzipped files |
|
Runs fgrep on bzipped files |
|
Compresses files using the Burrows-Wheeler block sorting text compression algorithm with Huffman coding; the compression rate is better than that achieved by more conventional compressors using “Lempel-Ziv” algorithms, like gzip |
|
Tries to recover data from damaged bzipped files |
|
Runs less on bzipped files |
|
Runs more on bzipped files |
|
The library implementing lossless, block-sorting data compression, using the Burrows-Wheeler algorithm |
The Diffutils package contains programs that show the differences between files or directories.
Prepare Diffutils for compilation:
./configure --prefix=/usr
Compile the package:
make
This package does not come with a test suite.
Install the package:
make install
The File package contains a utility for determining the type of a given file or files.
Prepare File for compilation:
./configure --prefix=/usr
Compile the package:
make
This package does not come with a test suite.
Install the package:
make install
The Findutils package contains programs to find files. These programs are provided to recursively search through a directory tree and to create, maintain, and search a database (often faster than the recursive find, but unreliable if the database has not been recently updated).
Prepare Findutils for compilation:
./configure --prefix=/usr --libexecdir=/usr/lib/locate \ --localstatedir=/var/lib/locate
The meaning of the configure options:
--localstatedir
This option changes the location of the locate database to be
in /var/lib/locate
, which
is FHS-compliant.
Compile the package:
make
To test the results, issue: make check
.
Install the package:
make install
The find
program is used by some of the scripts in the
CLFS-Bootscripts package. As /usr
may not be available during the early
stages of booting, the find binary needs to be on
the root partition:
mv -v /usr/bin/find /bin
The updatedb script needs to be modified to point to the new location for find:
sed -i 's@find:=${BINDIR}@find:=/bin@' /usr/bin/updatedb
Was formerly used to produce locate databases |
|
Was formerly used to produce locate databases; it is the ancestor of frcode. |
|
Searches given directory trees for files matching the specified criteria |
|
Is called by updatedb to compress the list of file names; it uses front-compression, reducing the database size by a factor of four to five. |
|
Searches through a database of file names and reports the names that contain a given string or match a given pattern |
|
Updates the locate database; it scans the entire file system (including other file systems that are currently mounted, unless told not to) and puts every file name it finds into the database |
|
Can be used to apply a given command to a list of files |
The Gawk package contains programs for manipulating text files.
Prepare Gawk for compilation:
./configure --prefix=/usr --libexecdir=/usr/lib
Now fix an issue that will cause the Gettext testsuite to fail:
echo '#define HAVE_LC_MESSAGES 1' >> config.h
Compile the package:
make
To test the results, issue: make check
.
Install the package:
make install
The Gettext package contains utilities for internationalization and localization. These allow programs to be compiled with NLS (Native Language Support), enabling them to output messages in the user's native language.
Prepare Gettext for compilation:
./configure --prefix=/usr
Compile the package:
make
To test the results, issue: make check
.
Install the package:
make install
Copies standard Gettext infrastructure files into a source package |
|
Substitutes environment variables in shell format strings |
|
Translates a natural language message into the user's language by looking up the translation in a message catalog |
|
Primarily serves as a shell function library for gettext |
|
Copies all standard Gettext files into the given top-level directory of a package to begin internationalizing it |
|
Displays a network hostname in various forms |
|
Filters the messages of a translation catalog according to their attributes and manipulates the attributes |
|
Concatenates and merges the given |
|
Compares two |
|
Finds the messages that are common to to the given
|
|
Converts a translation catalog to a different character encoding |
|
Creates an English translation catalog |
|
Applies a command to all translations of a translation catalog |
|
Applies a filter to all translations of a translation catalog |
|
Generates a binary message catalog from a translation catalog |
|
Extracts all messages of a translation catalog that match a given pattern or belong to some given source files |
|
Creates a new |
|
Combines two raw translations into a single file |
|
Decompiles a binary message catalog into raw translation text |
|
Unifies duplicate translations in a translation catalog |
|
Displays native language translations of a textual message whose grammatical form depends on a number |
|
Recode Serbian text from Cyrillic to Latin script. |
|
Extracts the translatable message lines from the given source files to make the first translation template |
|
defines the autosprintf class, which makes C formatted output routines usable in C++ programs, for use with the <string> strings and the <iostream> streams |
|
a private library containing common routines used by the various Gettext programs; these are not intended for general use |
|
Used to write specialized programs that process
|
|
A private library containing common routines used by the various Gettext programs; these are not intended for general use |
The Grep package contains programs for searching through files.
Prepare Grep for compilation:
./configure --prefix=/usr --bindir=/bin
Compile the package:
make
To test the results, issue: make check
.
Install the package:
make install
The Groff package contains programs for processing and formatting text.
Groff expects the environment variable PAGE
to contain the default paper size. For
users in the United States, PAGE=letter
is appropriate.
Elsewhere, PAGE=A4
may be more suitable.
Prepare Groff for compilation:
PAGE=[paper_size]
./configure --prefix=/usr
Compile the package:
make
This package does not come with a test suite.
Install the package:
make install
Some documentation programs, such as xman, will not work properly without the following symlinks:
ln -sv soelim /usr/bin/zsoelim ln -sv eqn /usr/bin/geqn ln -sv tbl /usr/bin/gtbl
Reads a troff font file and adds some additional font-metric information that is used by the groff system |
|
Creates a font file for use with groff and grops |
|
Compiles descriptions of equations embedded within troff input files into commands that are understood by troff |
|
Converts a troff EQN (equation) into a cropped image |
|
Marks differences between groff/nroff/troff files |
|
A link to eqn |
|
Converts a grap diagram into a cropped bitmap image |
|
A groff preprocessor for gremlin files |
|
A driver for groff that produces TeX dvi format |
|
A front-end to the groff document formatting system; normally, it runs the troff program and a post-processor appropriate for the selected device |
|
Displays groff files and man pages on X and tty terminals |
|
Reads files and guesses which of the groff options
|
|
Is a groff driver for Canon CAPSL printers (LBP-4 and LBP-8 series laser printers) |
|
Is a driver for groff that produces output in PCL5 format suitable for an HP LaserJet 4 printer |
|
Translates the output of GNU troff to PostScript |
|
Translates the output of GNU troff into a form suitable for typewriter-like devices |
|
A link to tbl |
|
Creates a font file for use with groff -Tlj4 from an HP-tagged font metric file |
|
Creates an inverted index for the bibliographic databases with a specified file for use with refer, lookbib, and lkbib |
|
Searches bibliographic databases for references that contain specified keys and reports any references found |
|
Prints a prompt on the standard error (unless the standard input is not a terminal), reads a line containing a set of keywords from the standard input, searches the bibliographic databases in a specified file for references containing those keywords, prints any references found on the standard output, and repeats this process until the end of input |
|
A simple preprocessor for groff |
|
Formats equations for American Standard Code for Information Interchange (ASCII) output |
|
A script that emulates the nroff command using groff |
|
Creates pdf documents using groff |
|
Translates a PostScript font in |
|
Compiles descriptions of pictures embedded within troff or TeX input files into commands understood by TeX or troff |
|
Converts a PIC diagram into a cropped image |
|
Translates the output of GNU troff to HTML |
|
Translates the output of GNU troff to HTML |
|
Copies the contents of a file to the standard output, except that lines between .[ and .] are interpreted as citations, and lines between .R1 and .R2 are interpreted as commands for how citations are to be processed |
|
Reads files and replaces lines of the form .so file by the contents of the mentioned file |
|
Compiles descriptions of tables embedded within troff input files into commands that are understood by troff |
|
Creates a font file for use with groff -Tdvi |
|
Is highly compatible with Unix troff; it should usually be invoked using the groff command, which will also run preprocessors and post-processors in the appropriate order and with the appropriate options |
|
A link to soelim |
The Gzip package contains programs for compressing and decompressing files.
The following command renames the internal implementation of futimens to gl_futimens as newer versions of Glibc provide an incompatible version:
sed -i "s/futimens/gl_&/" $(grep -lr futimens *)
Prepare Gzip for compilation:
./configure --prefix=/usr --bindir=/bin
Compile the package:
make
To test the results, issue: make check.
Install the package:
make install
Now we will move some of utilities to /usr/bin to meet FHS compliance:
mv -v /bin/z{egrep,cmp,diff,fgrep,force,grep,less,more,new} /usr/bin
Decompresses gzipped files |
|
Creates self-decompressing executable files |
|
Compresses the given files using Lempel-Ziv (LZ77) coding |
|
Decompresses compressed files |
|
Decompresses the given gzipped files to standard output |
|
Runs cmp on gzipped files |
|
Runs diff on gzipped files |
|
Runs egrep on gzipped files |
|
Runs fgrep on gzipped files |
|
Forces a |
|
Runs grep on gzipped files |
|
Runs less on gzipped files |
|
Runs more on gzipped files |
|
Re-compresses files from compress format
to gzip
format— |
The Inetutils package contains programs for basic networking.
Not all programs that come with Inetutils will be installed. However, the Inetutils build system will insist on installing all the man pages anyway. The following patch will correct this situation:
patch -Np1 -i ../inetutils-1.5-no_server_man_pages-2.patch
The follow patches fixes Bus Errors when you attempt to use ping on sparc:
patch -Np1 -i ../inetutils-1.5-memcpy_sparc64-1.patch
Prepare Inetutils for compilation:
./configure --prefix=/usr --libexecdir=/usr/sbin \ --sysconfdir=/etc --localstatedir=/var \ --disable-logger --disable-syslogd \ --disable-whois --disable-servers
The meaning of the configure options:
--disable-logger
This option prevents Inetutils from installing the logger program, which is used by scripts to pass messages to the System Log Daemon. Do not install it because Util-linux-ng installs a better version later.
--disable-syslogd
This option prevents Inetutils from installing the System Log Daemon, which is installed with the Sysklogd package.
--disable-whois
This option disables the building of the Inetutils whois client, which is out of date. Instructions for a better whois client are in the CBLFS book.
--disable-servers
This disables the installation of the various network servers included as part of the Inetutils package. These servers are deemed not appropriate in a basic CLFS system.
Compile the package:
make
This package does not come with a test suite.
Install the package:
make install
Move the ping and ping6 programs to their FHS-compliant place:
mv -v /usr/bin/ping{,6} /bin
Is the file transfer protocol program |
|
Utility for configuring network interfaces |
|
Sends echo-request packets and reports how long the replies take. This is the IPV4 version |
|
Sends echo-request packets and reports how long the replies take. This is the IPV6 version |
|
Performs remote file copy |
|
Performs remote login |
|
Runs a remote shell |
|
Is used to chat with another user |
|
An interface to the TELNET protocol |
|
A trivial file transfer program |
The Kbd package contains key-table files and keyboard utilities.
Prepare Kbd for compilation:
./configure --datadir=/lib/kbd
The meaning of the configure options:
--datadir
This option places the Kbd data and keymap files into /lib/kbd, as they are used by some of the scripts in the CLFS-Bootscripts package and must be on the root partition.
Compile the package:
make
This package does not come with a test suite.
Install the package:
make install
Some of the programs from Kbd are used by scripts in the
CLFS-Bootscripts package. As /usr
may not be available during the early
stages of booting, those binaries need to be on the root
partition:
mv -v /usr/bin/{kbd_mode,openvt,setfont} /bin
Changes the foreground virtual terminal |
|
Deallocates unused virtual terminals |
|
Dumps the keyboard translation tables |
|
Prints the number of the active virtual terminal |
|
Prints the kernel scancode-to-keycode mapping table |
|
Reports or sets the keyboard mode |
|
Sets the keyboard repeat and delay rates |
|
Loads the keyboard translation tables |
|
Loads the kernel unicode-to-font mapping table |
|
An obsolete program that used to load a user-defined output character mapping table into the console driver; this is now done by setfont |
|
Starts a program on a new virtual terminal (VT) |
|
A link to psfxtable |
|
A link to psfxtable |
|
A link to psfxtable |
|
Handle Unicode character tables for console fonts |
|
Changes the kernel idea of the console size |
|
Changes the Enhanced Graphic Adapter (EGA) and Video Graphics Array (VGA) fonts on the console |
|
Loads kernel scancode-to-keycode mapping table entries; this is useful if there are unusual keys on the keyboard |
|
Sets the keyboard flags and Light Emitting Diodes (LEDs) |
|
Defines the keyboard meta-key handling |
|
Shows the current EGA/VGA console screen font |
|
Reports the scancodes, keycodes, and ASCII codes of the keys pressed on the keyboard |
|
Puts the keyboard and console in UNICODE mode. Never use it on CLFS, because applications are not configured to support UNICODE. |
|
Reverts keyboard and console from UNICODE mode |
The Less package contains a text file viewer.
Prepare Less for compilation:
./configure --prefix=/usr --sysconfdir=/etc
The meaning of the configure option:
--sysconfdir=/etc
This option tells the programs created by the package
to look in /etc
for the
configuration files.
Compile the package:
make
This package does not come with a test suite.
Install the package:
make install
Move less to /bin:
mv -v /usr/bin/less /bin
The Make package contains a program for compiling packages.
Prepare Make for compilation:
./configure --prefix=/usr
Compile the package:
make
To test the results, issue: make check
.
Install the package:
make install
The Man package contains programs for finding and viewing man pages.
A few adjustments need to be made to the sources of Man.
First, a sed
substitution is needed to add the -R
switch to the PAGER
variable so that escape sequences are
properly handled by Less:
sed -i 's@-is@&R@g' configure
Another couple of sed substitutions comment
out the “MANPATH
/usr/man” and “MANPATH
/usr/local/man” lines in the man.conf
file to prevent redundant results
when using programs such as whatis:
sed -i 's@MANPATH./usr/man@#&@g' src/man.conf.in sed -i 's@MANPATH./usr/local/man@#&@g' src/man.conf.in
Prepare Man for compilation:
./configure -confdir=/etc
The meaning of the configure options:
-confdir=/etc
This tells the man program to look
for the man.conf
configuration file in the /etc
directory.
Compile the package:
make
This package does not come with a test suite.
Install the package:
make install
If you will be working on a terminal that does not support
text attributes such as color and bold, you can disable
Select Graphic Rendition (SGR) escape sequences by editing
the man.conf
file and adding
the -c
option to the
NROFF
variable. If you use
multiple terminal types for one computer it may be better
to selectively add the GROFF_NO_SGR
environment variable for the
terminals that do not support SGR.
If the character set of the locale uses 8-bit characters,
search for the line beginning with “NROFF” in /etc/man.conf
, and verify that it matches
the following:
NROFF /usr/bin/nroff -Tlatin1 -mandoc
Note that “latin1”
should be used even if it is not the character set of the
locale. The reason is that, according to the specification,
groff has no
means of typesetting characters outside International
Organization for Standards (ISO) 8859-1 without some strange
escape codes. When formatting man pages, groff thinks that they are
in the ISO 8859-1 encoding and this -Tlatin1
switch tells
groff to use
the same encoding for output. Since groff does no recoding of
input characters, the f ormatted result is really in the same
encoding as input, and therefore it is usable as the input
for a pager.
This does not solve the problem of a non-working man2dvi program for localized man pages in non-ISO 8859-1 locales. Also, it does not work with multibyte character sets. The first problem does not currently have a solution. The second issue is not of concern because the CLFS installation does not support multibyte character sets.
Searches the whatis database and displays the short descriptions of system commands that contain a given string |
|
Builds the whatis database;
it reads all the man pages in the |
|
Formats and displays the requested on-line man page |
|
Converts a man page into dvi format |
|
Converts a man page into HTML |
|
Searches the whatis database and displays the short descriptions of system commands that contain the given keyword as a separate word |
The Mktemp package contains programs used to create secure temporary files in shell scripts.
Many scripts still use the deprecated tempfile program, which has functionality similar to mktemp. Patch Mktemp to include a tempfile wrapper:
patch -Np1 -i ../mktemp-1.5-add_tempfile-3.patch
Prepare Mktemp for compilation:
./configure --prefix=/usr --with-libc
The meaning of the configure option:
--with-libc
This causes the mktemp program to use the mkstemp and mkdtemp functions from the system C library.
Compile the package:
make
This package does not come with a test suite.
Install the package:
make install make install-tempfile
The Module-Init-Tools package contains programs for handling kernel modules in Linux kernels greater than or equal to version 2.5.47.
The tarball only contains sgml source for the manual pages. The following patch contains the result of processing this through docbook2man which we do not build as part of a basic clfs install :
patch -Np1 -i ../module-init-tools-3.4-manpages-1.patch
Issue the following commands to perform the tests
note that the make clean command is required to clean up the source tree, otherwise the code built for testing will be installed, and the test version of modprobe does not function outside the test environment.
./configure && make check && make clean
Prepare Module-Init-Tools for compilation:
./configure --prefix=/ --enable-zlib
The meaning of the configure options:
--enable-zlib
This allows the Module-Init-Tools package to handle compressed kernel modules.
Compile the package:
make
Install the package:
make INSTALL=install install
The meaning of the make install parameter:
INSTALL=install
Normally, make install will not install the binaries if they already exist. This option overrides that behavior by calling install instead of using the default wrapper script.
Creates a dependency file based on the symbols it finds in the existing set of modules; this dependency file is used by modprobe to automatically load the required modules |
|
Creates a modprobe.conf file from an existing 2.2 or 2.4 module setup |
|
Installs a loadable module in the running kernel |
|
A statically compiled version of insmod |
|
Lists currently loaded modules |
|
Examines an object file associated with a kernel module and displays any information that it can glean |
|
Uses a dependency file, created by depmod, to automatically load relevant modules |
|
Unloads modules from the running kernel |
The Patch package contains a program for modifying or creating files by applying a “patch” file typically created by the diff program.
Prepare Patch for compilation:
./configure --prefix=/usr
Compile the package:
make
This package does not come with a test suite.
Install the package:
make install
The Psmisc package contains programs for displaying information about running processes.
Prepare Psmisc for compilation:
./configure --prefix=/usr --exec-prefix=""
The meaning of the configure option:
--exec-prefix=""
This ensures that the Psmisc binaries will install into
/bin
instead of
/usr/bin
. This is the
correct location according to the FHS, because some of
the Psmisc binaries are used by the CLFS-Bootscripts
package.
Compile the package:
make
This package does not come with a test suite.
Install the package:
make install
There is no reason for the pstree and pstree.x11 programs to
reside in /bin
. Therefore, move
them to /usr/bin
:
mv -v /bin/pstree* /usr/bin
By default, Psmisc's pidof program is not installed. This usually is not a problem because it is installed later in the Sysvinit package, which provides a better pidof program. If Sysvinit will not be used for a particular system, complete the installation of Psmisc by creating the following symlink:
ln -sv killall /bin/pidof
Reports the Process IDs (PIDs) of processes that use the given files or file systems |
|
Kills processes by name; it sends a signal to all processes running any of the given commands |
|
Reports the Process IDs (PIDs) of processes that use the given files or file systems |
|
Displays running processes as a tree |
|
Same as pstree, except that it waits for confirmation before exiting |
The Shadow package contains programs for handling passwords in a secure way.
If you would like to enforce the use of strong passwords,
refer to http://cblfs.cross-lfs.org/index.php/Cracklib
for installing Cracklib prior to building Shadow. Then add
--with-libcrack
to
the configure
command below.
Prepare Shadow for compilation:
./configure --libdir=/lib --sysconfdir=/etc --enable-shared \ --without-libpam --without-audit --without-selinux
The meaning of the configure options:
--sysconfdir=/etc
Tells Shadow to install its configuration files into /etc, rather than /usr/etc.
--without-libpam
Support for Linux-PAM is enabled by default in Shadow, however PAM is not installed on a base CLFS system, so this switch disables PAM support in Shadow. For instructions to install PAM and link Shadow to it, you can look at http://cblfs.cross-lfs.org/index.php/Linux-PAM.
--without-audit
Support for auditing is enabled by default, but a library that it needs is not installed in a base CLFS system. This switch disables auditing support.
--without-selinux
Support for selinux is enabled by default, but selinux is not built in a base CLFS system and configure will fail without this switch.
Disable the installation of the groups program and its man pages, as Coreutils provides a better version:
sed -i 's/groups$(EXEEXT) //' src/Makefile find man -name Makefile -exec sed -i '/groups.1.xml/d' '{}' \; find man -name Makefile -exec sed -i 's/groups.1 //' '{}' \;
Compile the package:
make
This package does not come with a test suite.
Install the package:
make install
Instead of using the default
crypt method, use the
more secure MD5 method
of password encryption, which also allows passwords longer
than 8 characters. It is also necessary to change the
obsolete /var/spool/mail
location for user mailboxes that Shadow uses by default to
the /var/mail
location used
currently. Use the following sed command to make these
changes to the appropriate configuration file:
sed -i /etc/login.defs \ -e 's@#MD5_CRYPT_ENAB.no@MD5_CRYPT_ENAB yes@' \ -e 's@/var/spool/mail@/var/mail@'
If you built Shadow with Cracklib support, execute this sed to correct the path to the Cracklib dictionary:
sed -i 's@DICTPATH.*@DICTPATH\t/lib/cracklib/pw_dict@' /etc/login.defs
Move a misplaced program to its proper location:
mv -v /usr/bin/passwd /bin
This package contains utilities to add, modify, and delete
users and groups; set and change their passwords; and perform
other administrative tasks. For a full explanation of what
password shadowing
means, see the doc/HOWTO
file
within the unpacked source tree. If using Shadow support,
keep in mind that programs which need to verify passwords
(display managers, FTP programs, pop3 daemons, etc.) must be
Shadow-compliant. That is, they need to be able to work with
shadowed passwords.
To enable shadowed passwords, run the following command:
pwconv
To enable shadowed group passwords, run:
grpconv
To view or change the default settings for new user accounts
that you create, you can edit /etc/default/useradd
. See man useradd or
http://cblfs.cross-lfs.org/index.php/Configuring_for_Adding_Users
for more information.
Choose a password for user root
and set it by running:
passwd root
Used to change the maximum number of days between obligatory password changes |
|
Used to change a user's full name and other information |
|
Used to update group passwords in batch mode |
|
Used to update the passwords of an entire series of user accounts |
|
Used to change a user's default login shell |
|
Checks and enforces the current password expiration policy |
|
Is used to examine the log of login failures, to set a maximum number of failures before an account is blocked, or to reset the failure count |
|
Is used to add and delete members and administrators to groups |
|
Creates a group with the given name |
|
Deletes the group with the given name |
|
Is used to modify the given group's name or GID |
|
Verifies the integrity of the group files
|
|
Creates or updates the shadow group file from the normal group file |
|
Updates |
|
Reports the most recent login of all users or of a given user |
|
Is used by the system to let users sign on |
|
Is a daemon used to enforce restrictions on log-on time and ports |
|
Is used to change the current GID during a login session |
|
Is used to create or update an entire series of user accounts |
|
Displays a message that an account is not available. Designed to be used as the default shell for accounts that have been disabled |
|
Is used to change the password for a user or group account |
|
Verifies the integrity of the password files
|
|
Creates or updates the shadow password file from the normal password file |
|
Updates |
|
Executes a given command while the user's GID is set to that of the given group |
|
Runs a shell with substitute user and group IDs |
|
Creates a new user with the given name, or updates the default new-user information |
|
Deletes the given user account |
|
Is used to modify the given user's login name, User Identification (UID), shell, initial group, home directory, etc. |
|
Edits the |
|
Edits the |
The Sysklogd package contains programs for logging system messages, such as those given by the kernel when unusual things happen.
Compile the package:
make
This package does not come with a test suite.
Install the package:
make install
Create a new /etc/syslog.conf
file by running the following:
cat > /etc/syslog.conf << "EOF"
# Begin /etc/syslog.conf
auth,authpriv.* -/var/log/auth.log
*.*;auth,authpriv.none -/var/log/sys.log
daemon.* -/var/log/daemon.log
kern.* -/var/log/kern.log
mail.* -/var/log/mail.log
user.* -/var/log/user.log
*.info;mail.none;authpriv.none;cron.none -/var/log/messages
*.emerg *
# log the bootscript output:
local2.* -/var/log/boot.log
# End /etc/syslog.conf
EOF
A system daemon for intercepting and logging kernel messages |
|
Logs the messages that system programs offer for logging. Every logged message contains at least a date stamp and a hostname, and normally the program's name too, but that depends on how trusting the logging daemon is told to be. |
The Sysvinit package contains programs for controlling the startup, running, and shutdown of the system.
When run-levels are changed (for example, when halting the system), init sends termination signals to those processes that init itself started and that should not be running in the new run-level. While doing this, init outputs messages like “Sending processes the TERM signal” which seem to imply that it is sending these signals to all currently running processes. To avoid this misinterpretation, modify the source so that these messages read like “Sending processes started by init the TERM signal” instead:
sed -i 's@Sending processes@& started by init@g' \ src/init.c
Compile the package:
make -C src clobber make -C src
Install the package:
make -C src install
Create a new file /etc/inittab
by running the following:
cat > /etc/inittab << "EOF"
# Begin /etc/inittab
id:3:initdefault:
si::sysinit:/etc/rc.d/init.d/rc sysinit
l0:0:wait:/etc/rc.d/init.d/rc 0
l1:S1:wait:/etc/rc.d/init.d/rc 1
l2:2:wait:/etc/rc.d/init.d/rc 2
l3:3:wait:/etc/rc.d/init.d/rc 3
l4:4:wait:/etc/rc.d/init.d/rc 4
l5:5:wait:/etc/rc.d/init.d/rc 5
l6:6:wait:/etc/rc.d/init.d/rc 6
ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now
su:S016:once:/sbin/sulogin
# Remove this section if you System only
# has a console port
1:2345:respawn:/sbin/agetty -I '\033(K' tty1 9600
2:2345:respawn:/sbin/agetty -I '\033(K' tty2 9600
3:2345:respawn:/sbin/agetty -I '\033(K' tty3 9600
4:2345:respawn:/sbin/agetty -I '\033(K' tty4 9600
5:2345:respawn:/sbin/agetty -I '\033(K' tty5 9600
6:2345:respawn:/sbin/agetty -I '\033(K' tty6 9600
# Uncomment this section if your system has a console
# port
#c0:12345:respawn:/sbin/agetty 9600 ttyS0 vt100
# End /etc/inittab
EOF
Logs boot messages to a log file |
|
Normally invokes shutdown with the
|
|
The first process to be started when the kernel has initialized the hardware which takes over the boot process and starts all the proceses it is instructed to |
|
Sends a signal to all processes, except the processes in its own session so it will not kill the shell running the script that called it |
|
Shows which users last logged in (and out),
searching back through the |
|
Shows the failed login attempts, as logged in
|
|
Controls whether other users can send messages to the current user's terminal |
|
Tells you whether or not a directory is a mount point. |
|
Reports the PIDs of the given programs |
|
Tells the kernel to halt the system and switch off the computer (see halt) |
|
Tells the kernel to reboot the system (see halt) |
|
Reports the previous and the current run-level, as
noted in the last run-level record in |
|
Brings the system down in a secure way, signaling all processes and notifying all logged-in users |
|
Allows root to log in; it is normally invoked by init when the system goes into single user mode |
|
Tells init which run-level to change to |
|
Displays the content of the given login file in a more user-friendly format |
|
Writes a message to all logged-in users |
The Tar package contains an archiving program.
Prepare Tar for compilation:
./configure --prefix=/usr --bindir=/bin --libexecdir=/usr/sbin
Compile the package:
make
To test the results, issue: make check
.
Install the package:
make install
The Texinfo package contains programs for reading, writing, and converting info pages.
Prepare Texinfo for compilation:
./configure --prefix=/usr
Compile the package:
make
To test the results, issue: make check
.
Install the package:
make install
The Info documentation system uses a plain text file to hold
its list of menu entries. The file is located at /usr/share/info/dir
. Unfortunately, due to
occasional problems in the Makefiles of various packages, it
can sometimes get out of sync with the info pages installed
on the system. If the /usr/share/info/dir
file ever needs to be
recreated, the following optional commands will accomplish
the task:
cd /usr/share/info rm dir for f in * do install-info $f dir 2>/dev/null done
Used to read info pages which are similar to man pages, but often go much deeper than just explaining all the command line options. For example, compare man bison and info bison. |
|
Compiles a source file containing Info customizations into a binary format |
|
Used to install info pages; it updates entries in the info index file |
|
Translates the given Texinfo source documents into info pages, plain text, or HTML |
|
Used to format the given Texinfo document into a device-independent file that can be printed |
|
Used to format the given Texinfo document into a Portable Document Format (PDF) file |
|
Used to sort Texinfo index files |
The Udev package contains programs for dynamic creation of device nodes.
Compile the package:
make EXTRAS="extras/ata_id extras/cdrom_id extras/collect \ extras/edd_id extras/firmware extras/floppy extras/path_id extras/rule_generator \ extras/scsi_id extras/usb_id extras/volume_id" udevdir=/dev
The meaning of the make parameter:
EXTRAS="extras/ata_id extras/cdrom_id
extras/collect extras/edd_id extras/firmware
extras/floppy extras/path_id extras/rule_generator
extras/scsi_id extras/usb_id
extras/volume_id"
This builds the helper applications that are used with udev. The helper programs assist in correct handling of devices.
If you want to run the testsuite, you need to change a hardcoded reference to the test program:
sed -i 's@/usr/bin/test@/bin/test@' test/udev-test.pl
To test the results, issue: make test
.
Install the package:
make EXTRAS="extras/ata_id extras/cdrom_id extras/collect \ extras/edd_id extras/firmware extras/floppy extras/path_id extras/rule_generator \ extras/scsi_id extras/usb_id extras/volume_id" DESTDIR=/ udevdir=/dev install
The meaning of the make parameter:
DESTDIR=/
This prevents the Udev build process from killing any udevd processes that may be running on the system.
Install documentation:
install -v -m644 -D docs/writing_udev_rules/index.html \ /usr/share/doc/udev-124/index.html
Create a directory for storing firmware that can be loaded by udev:
install -dv /lib/firmware
This program combines udevinfo, udevtrigger, udevsettle, udevcontrol, udevmonitor, and udevtest into one command. |
|
Configures a number of options for the running udevd daemon, such as the log level. (Symlink to udevadm) |
|
A daemon that reorders hotplug events before submitting them to udev, thus avoiding various race conditions |
|
Allows users to query the udev database for
information on any device currently present on the
system; it also provides a way to query any device
in the |
|
Prints the event received from the kernel and the event which udev sends out after rule processing |
|
Watches the Udev event queue and exits if all current uevents have been handled. (Symlink to udevadm) |
|
Simulates a udev run for the given device, and prints out the name of the node the real udev would have created or the name of the renamed network interface |
|
Walks the sysfs tree for devices that need to be added to the system. |
|
Provides Udev with a unique string and additional information (uuid, label) for an ATA drive |
|
Print the capabilities of a CDROM or DVDROM drive. |
|
Creates all possible floppy devices based on the CMOS type |
|
Read the label from an s390 block device. |
|
Identify x86 disk drives from Enhanced Disk Drive calls. |
|
Script to load firmware for a device |
|
Provide the shortest possible unique hardware path to a device |
|
Retrieve or generate a unique SCSI identifier. |
|
Identify a USB block device. |
|
Probe filesystem type and read label and uuid. |
|
This library provides programs such as vol_id with a filesystems type, abel, and uuid from a device node or a image. |
|
Contains udev configuration files, device permissions, and rules for device naming |
|
Contains udev helper programs and static devices which get copied to /dev when booted. |
The Util-linux-ng package contains miscellaneous utility programs. Among them are utilities for handling file systems, consoles, partitions, and messages.
The FHS recommends using the /var/lib/hwclock
directory instead of the
usual /etc
directory as the
location for the adjtime
file.
To make the hwclock program
FHS-compliant, run the following:
sed -i 's@etc/adjtime@var/lib/hwclock/adjtime@g' \ hwclock/hwclock.c mkdir -pv /var/lib/hwclock
Prepare Util-linux-ng for compilation:
./configure --enable-partx \ --disable-wall --enable-write
Compile the package:
make
This package does not come with a test suite.
Install the package:
make install
Move the logger
binary to /bin
as it is needed
by the CLFS-Bootscripts package:
mv -v /usr/bin/logger /bin
Informs the kernel of a new partition |
|
Opens a tty port, prompts for a login name, and then invokes the login program |
|
Allows users to call block device ioctls from the command line |
|
Displays a simple calendar |
|
Manipulates the partition table of the given device |
|
Finds duplicate executables |
|
Filters out reverse line feeds |
|
Filters nroff output for terminals that lack some capabilities, such as overstriking and half-lines |
|
Filters out the given columns |
|
Formats a given file into multiple columns |
|
Sets the function of the Ctrl+Alt+Del key combination to a hard or a soft reset |
|
Tunes the parameters of the serial line drivers for Cyclades cards |
|
Gives the Discordian date or converts the given Gregorian date to a Discordian one |
|
Asks the kernel to remove a partition |
|
Dumps the kernel boot messages |
|
Low-level formats a floppy disk |
|
Manipulates the partition table of the given device |
|
Acquires a file lock and then executes a command with the lock held |
|
Performs a consistency check on the Cramfs file system on the given device |
|
Performs a consistency check on the Minix file system on the given device |
|
Parses options in the given command line |
|
Dumps the given file in hexadecimal or in another given format |
|
Reads or sets the system's hardware clock, also called the Real-Time Clock (RTC) or Basic Input-Output System (BIOS) clock |
|
Gives and sets program I/O scheduling class and priority |
|
Removes the given Inter-Process Communication (IPC) resource |
|
Provides IPC status information |
|
Reports the size of an iso9660 file system |
|
Copies a single line |
|
Enters the given message into the system log |
|
Displays lines that begin with the given string |
|
Sets up and controls loop devices |
|
Generates magic cookies (128-bit random hexadecimal numbers) for xauth |
|
Builds a file system on a device (usually a hard disk partition) |
|
Creates a Santa Cruz Operations (SCO) bfs file system |
|
Creates a cramfs file system |
|
Creates a Minix file system |
|
Initializes the given device or file to be used as a swap area |
|
A filter for paging through text one screen at a time |
|
Attaches the file system on the given device to a specified directory in the file-system tree |
|
Shows the symbolic links in the given pathnames |
|
Tells the kernel about the presence and numbering of on-disk partitions |
|
Displays a text file one screen full at a time |
|
Makes the given file system the new root file system of the current process |
|
Reads kernel profiling information |
|
Renames the given files, replacing a given string with another |
|
Alters the priority of running processes |
|
Reverses the lines of a given file |
|
Enters a system sleep state until a specified wakeup time |
|
Makes a typescript of a terminal session |
|
Plays back typescripts created by script |
|
Changes reported architecture in new program environment and sets personality flags |
|
Runs the given program in a new session |
|
Sets terminal attributes |
|
A disk partition table manipulator |
|
Disables devices and files for paging and swapping |
|
Enables devices and files for paging and swapping and lists the devices and files currently in use |
|
Tracks the growth of a log file. Displays the last 10 lines of a log file, then continues displaying any new entries in the log file as they are created |
|
Retrieves or sets a process's CPU affinity |
|
Tunes the parameters of the line printer |
|
A filter for translating underscores into escape sequences indicating underlining for the terminal in use |
|
Disconnects a file system from the system's file tree |
|
Reports the location of the binary, source, and man page for the given command |
|
Sends a message to the given user if that user has not disabled receipt of such messages |
The Vim package contains a powerful text editor.
If you prefer another editor—such as Emacs, Joe, or Nano—please refer to http://cblfs.cross-lfs.org/index.php/Category:Text_Editors for suggested installation instructions.
First, unpack both vim-7.1.tar.bz2
and (optionally)
vim-7.1-lang.tar.gz
archives
into the same directory.
The following patches merges all updates from the 7.1 Branch from the Vim developers:
patch -Np1 -i ../vim-7.1-branch_update-2.patch
Change the default location of the vimrc
configuration file to /etc
:
echo '#define SYS_VIMRC_FILE "/etc/vimrc"' >> src/feature.h
Prepare Vim for compilation:
./configure --prefix=/usr --enable-multibyte
The meaning of the configure options:
--enable-multibyte
This optional but highly recommended switch enables support for editing files in multibyte character encodings. This is needed if using a locale with a multibyte character set. This switch is also helpful to be able to edit text files initially created in Linux distributions like Fedora Core that use UTF-8 as a default character set.
Compile the package:
make
To test the results, issue: make test
. However, this
test suite outputs a lot of binary data to the screen, which
can cause issues with the settings of the current terminal.
This can be resolved by redirecting the output to a log file.
Install the package:
make install
Many users are accustomed to using vi instead of vim. Some programs, such as vigr and vipw, also use vi. Create a symlink to permit execution of vim when users habitually enter vi and allow programs that use vi to work:
ln -sv vim /usr/bin/vi
By default, Vim's documentation is installed in /usr/share/vim
. The following symlink
allows the documentation to be accessed via /usr/share/doc/vim-7.1
, making it
consistent with the location of documentation for other
packages:
ln -sv ../vim/vim71/doc /usr/share/doc/vim-7.1
If an X Window System is going to be installed on the CLFS system, you may want to recompile Vim after installing X. Vim comes with a GUI version of the editor that requires X and some additional libraries to be installed. For more information, refer to the Vim documentation and the Vim installation page in the CBLFS book at http://cblfs.cross-lfs.org/index.php/Vim.
By default, vim runs in vi-incompatible mode. This may be new to users who have used other editors in the past. The “nocompatible” setting is included below to highlight the fact that a new behavior is being used. It also reminds those who would change to “compatible” mode that it should be the first setting in the configuration file. This is necessary because it changes other settings, and overrides must come after this setting. Create a default vim configuration file by running the following:
cat > /etc/vimrc << "EOF"
" Begin /etc/vimrc
set nocompatible
set backspace=2
syntax on
if (&term == "iterm") || (&term == "putty")
set background=dark
endif
" End /etc/vimrc
EOF
The set nocompatible
makes vim
behave in a more useful way (the default) than the
vi-compatible manner. Remove the “no” to keep the old vi behavior. The set backspace=2
allows
backspacing over line breaks, autoindents, and the start of
insert. The syntax on
enables vim's syntax highlighting. Finally, the if statement with the set background=dark
corrects
vim's guess
about the background color of some terminal emulators. This
gives the highlighting a better color scheme for use on the
black background of these programs.
Documentation for other available options can be obtained by running the following command:
vim -c ':options'
A filter for creating an error file that can be read by vim |
|
Reformats the error messages of the Perl interpreter for use with the “quickfix” mode of vim |
|
Starts vim in ex mode |
|
A script that starts vim with less.vim |
|
Processes vim errors |
|
Creates a tags file for Perl code for use by vim |
|
Checks the spelling of arguments |
|
Is a restricted version of view; no shell commands can be started and view cannot be suspended |
|
Is a restricted version of vim; no shell commands can be started and vim cannot be suspended |
|
Generates a tags file for Perl scripts |
|
Generates a tags file for TCL code |
|
Starts vim in read-only mode |
|
Link to vim |
|
Is the editor |
|
Starts vim with the terminal in 132-column mode |
|
Converts Vim documentation to HypterText Markup Language (HTML) |
|
Edits two or three versions of a file with vim and show differences |
|
Enables the DEC locator input model on a remote terminal |
|
Spell checks a file and generates the syntax statements necessary to highlight in vim. This script requires the old Unix spell command, which is provided neither in CLFS nor in CBLFS |
|
Teaches the basic keys and commands of vim |
|
Creates a hex dump of the given file; it can also do the reverse, so it can be used for binary patching |
The ELFtoaout package contains the Sparc ELF to a.out converter.
The following patch fixes some 64 bit issues with elftoaout:
patch -Np1 -i ../elftoaout-2.3-64bit_fixes-1.patch
Compile the ELFtoaout package:
make CC="gcc ${BUILD64}"
Install the package:
make install
The Silo package contains the Sparc Improved boot LOader.
The following patch fixes compile issues:
patch -Np1 -i ../silo-1.4.13-fixes-3.patch
Compile the Silo package:
make
Install the package:
make install
Silo bootloader installer. This program installs the first stage into the bootblock. |
|
Checks to see whether a file is readable by silo (very handy if you have larger disks). |
|
Is a file that is called by the tilo command to build a TFTP boot image. |
|
Tilo is a tool for building a simple TFTP boot loader which embodies several kernel images for different Sun architectures and a ramdisk root image. |
Most programs and libraries are, by default, compiled with
debugging symbols included (with gcc's -g
option). This means that when debugging a
program or library that was compiled with debugging information
included, the debugger can provide not only memory addresses,
but also the names of the routines and variables.
However, the inclusion of these debugging symbols enlarges a program or library significantly. The following is an example of the amount of space these symbols occupy:
a bash binary with debugging symbols: 1200 KB
a bash binary without debugging symbols: 480 KB
Glibc and GCC files (/lib
and /usr/lib
) with
debugging symbols: 87 MB
Glibc and GCC files without debugging symbols: 16 MB
Sizes may vary depending on which compiler and C library were used, but when comparing programs with and without debugging symbols, the difference will usually be a factor between two and five.
Because most users will never use a debugger on their system software, a lot of disk space can be regained by removing these symbols. The next section shows how to strip all debugging symbols from the programs and libraries.
If the intended user is not a programmer and does not plan to do any debugging on the system software, the system size can be decreased by about 200 MB by removing the debugging symbols from binaries and libraries. This causes no inconvenience other than not being able to debug the software fully anymore.
Most people who use the command mentioned below do not experience any difficulties. However, it is easy to make a typo and render the new system unusable, so before running the strip command, it is a good idea to make a backup of the current situation.
Before performing the stripping, take special care to ensure that none of the binaries that are about to be stripped are running. If unsure whether the user entered chroot with the command given in If You Are Going to Chroot first exit from chroot:
logout
Then reenter it with:
chroot ${CLFS} /tools/bin/env -i \ HOME=/root TERM=${TERM} PS1='\u:\w\$ ' \ PATH=/bin:/usr/bin:/sbin:/usr/sbin \ /tools/bin/bash --login
Now the binaries and libraries can be safely stripped:
/tools/bin/find /{,usr/}{bin,lib,sbin} -type f \ -exec /tools/bin/strip --strip-debug '{}' ';'
A large number of files will be reported as having their file format not recognized. These warnings can be safely ignored. These warnings indicate that those files are scripts instead of binaries.
If disk space is very tight, the --strip-all
option can be used on the binaries
in /{,usr/}{bin,sbin}
to gain
several more megabytes. Do not use this option on
libraries—they will be destroyed.
This chapter details how to install and configure the CLFS-Bootscripts package. Most of these scripts will work without modification, but a few require additional configuration files because they deal with hardware-dependent information.
System-V style init scripts are employed in this book because they are widely used. For additional options, a hint detailing the BSD style init setup is available at http://hints.cross-lfs.org/bsd-init.txt. Searching the LFS mailing lists for “depinit” will also offer additional choices.
If using an alternative style of init scripts, skip this chapter and move on to Making the CLFS System Bootable.
The CLFS-Bootscripts package contains a set of scripts to start/stop the CLFS system at bootup/shutdown.
Install the package:
make install-bootscripts
Checks the integrity of the file systems before they are mounted (with the exception of journal and network based file systems) |
|
Removes files that should not be preserved between
reboots, such as those in |
|
Loads the correct keymap table for the desired keyboard layout; it also sets the screen font |
|
Contains common functions, such as error and status checking, that are used by several bootscripts |
|
Halts the system |
|
Assists the network script with stopping network devices |
|
Assists the network script with starting network devices |
|
Sets up the system's hostname and local loopback device |
|
Mounts all file systems, except ones that are marked noauto or are network based |
|
Mounts virtual kernel file systems, such as
|
|
Sets up network interfaces, such as network cards, and sets up the default gateway (where applicable) |
|
The master run-level control script; it is responsible for running all the other bootscripts one-by-one, in a sequence determined by the name of the symbolic links being processed |
|
Reboots the system |
|
Makes sure every process is terminated before the system reboots or halts |
|
Resets the kernel clock to local time in case the hardware clock is not set to UTC time |
|
Provides the functionality needed to assign a static Internet Protocol (IP) address to a network interface |
|
Enables and disables swap files and partitions |
|
Starts and stops the system and kernel log daemons |
|
A template to create custom bootscripts for other daemons |
Linux uses a special booting facility named SysVinit that is based on a concept of run-levels. It can be quite different from one system to another, so it cannot be assumed that because things worked in one particular Linux distribution, they should work the same in CLFS too. CLFS has its own way of doing things, but it respects generally accepted standards.
SysVinit (which will be referred to as “init” from now on) works using a
run-levels scheme. There are seven (numbered 0 to 6) run-levels
(actually, there are more run-levels, but they are for special
cases and are generally not used. See init(8)
for more details), and each one of
those corresponds to the actions the computer is supposed to
perform when it starts up. The default run-level is 3. Here are
the descriptions of the different run-levels as they are
implemented:
0: halt the computer
1: single-user mode
2: multi-user mode without networking
3: multi-user mode with networking
4: reserved for customization, otherwise does the same as 3
5: same as 4, it is usually used for GUI login (like X's xdm or KDE's kdm)
6: reboot the computer
The command used to change run-levels is init [runlevel]
,
where [runlevel]
is
the target run-level. For example, to reboot the computer, a
user could issue the init
6 command, which is an alias for the
reboot command.
Likewise, init 0
is an alias for the halt command.
There are a number of directories under /etc/rc.d
that look like rc?.d
(where ? is the number of the
run-level) and rcsysinit.d
, all
containing a number of symbolic links. Some begin with a
K, the others begin with
an S, and all of them
have two numbers following the initial letter. The K means to
stop (kill) a service and the S means to start a service. The
numbers determine the order in which the scripts are run, from
00 to 99—the lower the number the earlier it gets
executed. When init switches to another
run-level, the appropriate services are either started or
stopped, depending on the runlevel chosen.
The real scripts are in /etc/rc.d/init.d
. They do the actual work,
and the symlinks all point to them. Killing links and starting
links point to the same script in /etc/rc.d/init.d
. This is because the scripts
can be called with different parameters like start
, stop
,
restart
, reload
, and status
.
When a K link is encountered, the appropriate script is run
with the stop
argument. When an S
link is encountered, the appropriate script is run with the
start
argument.
There is one exception to this explanation. Links that start
with an S in the
rc0.d
and rc6.d
directories will not cause anything to
be started. They will be called with the parameter stop
to stop something. The logic behind this
is that when a user is going to reboot or halt the system,
nothing needs to be started. The system only needs to be
stopped.
These are descriptions of what the arguments make the scripts do:
start
The service is started.
stop
The service is stopped.
restart
The service is stopped and then started again.
reload
The configuration of the service is updated. This is used after the configuration file of a service was modified, when the service does not need to be restarted.
status
Tells if the service is running and with which PIDs.
Feel free to modify the way the boot process works (after all, it is your own CLFS system). The files given here are an example of how it can be done.
In Installing Basic System Software, we installed the Udev package. Before we go into the details regarding how this works, a brief history of previous methods of handling devices is in order.
Linux systems in general traditionally use a static device
creation method, whereby a great many device nodes are created
under /dev
(sometimes literally
thousands of nodes), regardless of whether the corresponding
hardware devices actually exist. This is typically done via a
MAKEDEV script,
which contains a number of calls to the mknod program with the
relevant major and minor device numbers for every possible
device that might exist in the world.
Using the Udev method, only those devices which are detected by
the kernel get device nodes created for them. Because these
device nodes will be created each time the system boots, they
will be stored on a tmpfs
file
system (a virtual file system that resides entirely in system
memory). Device nodes do not require much space, so the memory
that is used is negligible.
In February 2000, a new filesystem called devfs
was merged into the 2.3.46 kernel
and was made available during the 2.4 series of stable
kernels. Although it was present in the kernel source itself,
this method of creating devices dynamically never received
overwhelming support from the core kernel developers.
The main problem with the approach adopted by devfs
was the way it handled device
detection, creation, and naming. The latter issue, that of
device node naming, was perhaps the most critical. It is
generally accepted that if device names are allowed to be
configurable, then the device naming policy should be up to a
system administrator, not imposed on them by any particular
developer(s). The devfs
file
system also suffers from race conditions that are inherent in
its design and cannot be fixed without a substantial revision
to the kernel. It has also been marked as deprecated due to a
lack of recent maintenance.
With the development of the unstable 2.5 kernel tree, later
released as the 2.6 series of stable kernels, a new virtual
filesystem called sysfs
came
to be. The job of sysfs
is to
export a view of the system's hardware configuration to
userspace processes. With this userspace-visible
representation, the possibility of seeing a userspace
replacement for devfs
became
much more realistic.
The sysfs
filesystem was
mentioned briefly above. One may wonder how sysfs
knows about the devices present
on a system and what device numbers should be used for
them. Drivers that have been compiled into the kernel
directly register their objects with sysfs
as they are detected by the
kernel. For drivers compiled as modules, this registration
will happen when the module is loaded. Once the
sysfs
filesystem is mounted
(on /sys
), data which the
built-in drivers registered with sysfs
are available to userspace
processes and to udevd for device node
creation.
The S10udev
initscript takes care of creating device nodes when Linux
is booted. The script unsets the uevent handler from the
default of /sbin/hotplug. This is
done because the kernel no longer needs to call out to an
external binary. Instead udevd will listen on a
netlink socket for uevents that the kernel raises. Next,
the bootscript copies any static device nodes that exist in
/lib/udev/devices
to
/dev
. This is necessary
because some devices, directories, and symlinks are needed
before the dynamic device handling processes are available
during the early stages of booting a system. Creating
static device nodes in /lib/udev/devices
also provides an easy
workaround for devices that are not supported by the
dynamic device handling infrastructure. The bootscript then
starts the Udev daemon, udevd, which will act on
any uevents it receives. Finally, the bootscript forces the
kernel to replay uevents for any devices that have already
been registered and then waits for udevd to handle them.
To obtain the right major and minor number for a device,
Udev relies on the information provided by sysfs
in /sys
. For example, /sys/class/tty/vcs/dev
contains the
string “7:0”. This
string is used by udevd to create a device
node with major number 7 and minor 0. The names and permissions of
the nodes created under the /dev
directory are determined by rules
specified in the files within the /etc/udev/rules.d/
directory. These are
numbered in a similar fashion to the CLFS-Bootscripts
package. If udevd can't find a rule
for the device it is creating, it will default permissions
to 660 and ownership
to root:root.
Documentation on the syntax of the Udev rules configuration
files are available in /usr/share/doc/udev-124/index.html
Device drivers compiled as modules may have aliases built
into them. Aliases are visible in the output of the
modinfo
program and are usually related to the bus-specific
identifiers of devices supported by a module. For example,
the snd-fm801 driver
supports PCI devices with vendor ID 0x1319 and device ID
0x0801, and has an alias of “pci:v00001319d00000801sv*sd*bc04sc01i*”.
For most devices, the bus driver exports the alias of the
driver that would handle the device via sysfs
. E.g., the /sys/bus/pci/devices/0000:00:0d.0/modalias
file might contain the string “pci:v00001319d00000801sv00001319sd00001319bc04sc01i00”.
The rules that CLFS installs will cause udevd to call out to
/sbin/modprobe with the
contents of the MODALIAS
uevent
environment variable (that should be the same as the
contents of the modalias
file
in sysfs), thus loading all modules whose aliases match
this string after wildcard expansion.
In this example, this means that, in addition to snd-fm801, the obsolete (and unwanted) forte driver will be loaded if it is available. See below for ways in which the loading of unwanted drivers can be prevented.
The kernel itself is also able to load modules for network protocols, filesystems and NLS support on demand.
There are a few possible problems when it comes to automatically creating device nodes.
Udev will only load a module if it has a bus-specific alias
and the bus driver properly exports the necessary aliases
to sysfs
. In other cases,
one should arrange module loading by other means. With
Linux-2.6.24.7, Udev is known to load properly-written
drivers for INPUT, IDE, PCI, USB, SCSI, SERIO and FireWire
devices.
To determine if the device driver you require has the
necessary support for Udev, run modinfo with the module
name as the argument. Now try locating the device directory
under /sys/bus
and check
whether there is a modalias
file there.
If the modalias
file exists
in sysfs
, the driver
supports the device and can talk to it directly, but
doesn't have the alias, it is a bug in the driver. Load the
driver without the help from Udev and expect the issue to
be fixed later.
If there is no modalias
file
in the relevant directory under /sys/bus
, this means that the kernel
developers have not yet added modalias support to this bus
type. With Linux-2.6.24.7, this is the case with ISA
busses. Expect this issue to be fixed in later kernel
versions.
Udev is not intended to load “wrapper” drivers such as snd-pcm-oss and non-hardware drivers such as loop at all.
If the “wrapper”
module only enhances the functionality provided by some
other module (e.g., snd-pcm-oss enhances the
functionality of snd-pcm by making the sound
cards available to OSS applications), configure
modprobe to
load the wrapper after Udev loads the wrapped module. To do
this, add an “install” line in /etc/modprobe.conf
. For example:
install snd-pcm /sbin/modprobe -i snd-pcm ; \
/sbin/modprobe snd-pcm-oss ; true
If the module in question is not a wrapper and is useful by
itself, configure the S05modules bootscript to
load this module on system boot. To do this, add the module
name to the /etc/sysconfig/modules
file on a separate
line. This works for wrapper modules too, but is suboptimal
in that case.
Either don't build the module, or blacklist it in
/etc/modprobe.conf
file as
done with the forte
module in the example below:
blacklist forte
Blacklisted modules can still be loaded manually with the explicit modprobe command.
This usually happens if a rule unexpectedly matches a device. For example, a poorly-writen rule can match both a SCSI disk (as desired) and the corresponding SCSI generic device (incorrectly) by vendor. Find the offending rule and make it more specific.
This may be another manifestation of the previous problem.
If not, and your rule uses sysfs
attributes, it may be a kernel
timing issue, to be fixed in later kernels. For now, you
can work around it by creating a rule that waits for the
used sysfs
attribute and
appending it to the /etc/udev/rules.d/10-wait_for_sysfs.rules
file. Please notify the CLFS Development list if you do so
and it helps.
Further text assumes that the driver is built statically into the kernel or already loaded as a module, and that you have already checked that Udev doesn't create a misnamed device.
Udev has no information needed to create a device node if a
kernel driver does not export its data to sysfs
. This is most common with third
party drivers from outside the kernel tree. Create a static
device node in /lib/udev/devices
with the appropriate
major/minor numbers (see the file devices.txt
inside the kernel
documentation or the documentation provided by the third
party driver vendor). The static device node will be copied
to /dev
by the S10udev bootscript.
This is due to the fact that Udev, by design, handles uevents and loads modules in parallel, and thus in an unpredictable order. This will never be “fixed”. You should not rely upon the kernel device names being stable. Instead, create your own rules that make symlinks with stable names based on some stable attributes of the device, such as a serial number or the output of various *_id utilities installed by Udev. See Section 11.12, “Creating custom symlinks to devices” and Section 11.13, “Configuring the network Script” for examples.
Additional helpful documentation is available at the following sites:
A Userspace Implementation of devfs
http://www.kroah.com/linux/talks/ols_2003_udev_paper/Reprint-Kroah-Hartman-OLS2003.pdf
udev FAQ http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev-FAQ
The sysfs
Filesystem
http://www.kernel.org/pub/linux/kernel/people/mochel/doc/papers/ols-2005/mochel.pdf
The setclock
script reads the time from the hardware clock, also known as
the BIOS or the Complementary Metal Oxide Semiconductor (CMOS)
clock. If the hardware clock is set to UTC, this script will
convert the hardware clock's time to the local time using the
/etc/localtime
file (which tells
the hwclock
program which timezone the user is in). There is no way to
detect whether or not the hardware clock is set to UTC, so this
needs to be configured manually.
If you cannot remember whether or not the hardware clock is set
to UTC, find out by running the hwclock --localtime --show
command. This will display what the current time is according
to the hardware clock. If this time matches whatever your watch
says, then the hardware clock is set to local time. If the
output from hwclock is not local time,
chances are it is set to UTC time. Verify this by adding or
subtracting the proper amount of hours for the timezone to the
time shown by hwclock. For example, if you
are currently in the MST timezone, which is also known as GMT
-0700, add seven hours to the local time.
Change the value of the UTC
variable
below to a value of 0
(zero) if the
hardware clock is not
set to UTC time.
Create a new file /etc/sysconfig/clock
by running the
following:
cat > /etc/sysconfig/clock << "EOF"
# Begin /etc/sysconfig/clock
UTC=1
# End /etc/sysconfig/clock
EOF
A good hint explaining how to deal with time on CLFS is
available at http://hints.cross-lfs.org/time.txt.
It explains issues such as time zones, UTC, and the
TZ
environment variable.
This section discusses how to configure the console bootscript that sets up the keyboard map and the console font. If non-ASCII characters (e.g., the British pound sign and Euro character) will not be used and the keyboard is a U.S. one, skip this section. Without the configuration file, the console bootscript will do nothing.
The console
script reads the /etc/sysconfig/console
file for configuration
information. Decide which keymap and screen font will be used.
Various language-specific HOWTO's can also help with this (see
http://www.tldp.org/HOWTO/HOWTO-INDEX/other-lang.html.
A pre-made /etc/sysconfig/console
file with known settings for several countries was installed
with the CLFS-Bootscripts package, so the relevant section can
be uncommented if the country is supported. If still in doubt,
look in the /lib/kbd
directory
for valid keymaps and screen fonts. Read loadkeys(1)
and setfont(8)
to determine the correct arguments
for these programs. Once decided, create the configuration file
with the following command:
cat >/etc/sysconfig/console <<"EOF"
KEYMAP="[arguments for loadkeys]
"
FONT="[arguments for setfont]
"
EOF
For example, for Spanish users who also want to use the Euro character (accessible by pressing AltGr+E), the following settings are correct:
cat >/etc/sysconfig/console <<"EOF"
KEYMAP="es euro2"
FONT="lat9-16 -u iso01"
EOF
The FONT
line above is correct
only for the ISO 8859-15 character set. If using ISO 8859-1
and, therefore, a pound sign instead of Euro, the correct
FONT
line would be:
FONT="lat1-16"
If the KEYMAP
or FONT
variable is not set, the console initscript will not
run the corresponding program.
In some keymaps, the Backspace and Delete keys send characters different from ones in the default keymap built into the kernel. This confuses some applications. For example, Emacs displays its help (instead of erasing the character before the cursor) when Backspace is pressed. To check if the keymap in use is affected (this works only for i386 keymaps):
zgrep '\W14\W' [/path/to/your/keymap]
If the keycode 14 is Backspace instead of Delete, create the following keymap snippet to fix this issue:
mkdir -pv /etc/kbd && cat > /etc/kbd/bs-sends-del <<"EOF"
keycode 14 = Delete Delete Delete Delete
alt keycode 14 = Meta_Delete
altgr alt keycode 14 = Meta_Delete
keycode 111 = Remove
altgr control keycode 111 = Boot
control alt keycode 111 = Boot
altgr control alt keycode 111 = Boot
EOF
Tell the console script to load this snippet after the main keymap:
cat >>/etc/sysconfig/console <<"EOF"
KEYMAP_CORRECTIONS="/etc/kbd/bs-sends-del"
EOF
The sysklogd
script invokes the
syslogd program
with the -m 0
option. This option
turns off the periodic timestamp mark that syslogd writes to the log
files every 20 minutes by default. If you want to turn on this
periodic timestamp mark, edit the sysklogd
script and make the changes
accordingly. See man
syslogd
for more information.
The /etc/inputrc
file deals with
mapping the keyboard for specific situations. This file is the
start-up file used by Readline — the input-related
library — used by Bash and most other shells.
Most people do not need user-specific keyboard mappings so the
command below creates a global /etc/inputrc
used by everyone who logs in. If
you later decide you need to override the defaults on a
per-user basis, you can create a .inputrc
file in the user's home directory
with the modified mappings.
For more information on how to edit the inputrc
file, see info bash under the
Readline Init File
section. info
readline is also a good source of information.
Below is a generic global inputrc
along with comments to explain what the various options do.
Note that comments cannot be on the same line as commands.
Create the file using the following command:
cat > /etc/inputrc << "EOF"
# Begin /etc/inputrc
# Modified by Chris Lynn <roryo@roryo.dynup.net>
# Allow the command prompt to wrap to the next line
set horizontal-scroll-mode Off
# Enable 8bit input
set meta-flag On
set input-meta On
# Turns off 8th bit stripping
set convert-meta Off
# Keep the 8th bit for display
set output-meta On
# none, visible or audible
set bell-style none
# All of the following map the escape sequence of the
# value contained inside the 1st argument to the
# readline specific functions
"\eOd": backward-word
"\eOc": forward-word
# for linux console
"\e[1~": beginning-of-line
"\e[4~": end-of-line
"\e[5~": beginning-of-history
"\e[6~": end-of-history
"\e[3~": delete-char
"\e[2~": quoted-insert
# for xterm
"\eOH": beginning-of-line
"\eOF": end-of-line
# for Konsole
"\e[H": beginning-of-line
"\e[F": end-of-line
# End /etc/inputrc
EOF
The shell program /bin/bash (hereafter referred
to as “the shell”) uses
a collection of startup files to help create an environment to
run in. Each file has a specific use and may affect login and
interactive environments differently. The files in the
/etc
directory provide global
settings. If an equivalent file exists in the home directory,
it may override the global settings.
An interactive login shell is started after a successful login,
using /bin/login,
by reading the /etc/passwd
file.
An interactive non-login shell is started at the command-line
(e.g., [prompt]$
/bin/bash). A non-interactive
shell is usually present when a shell script is running. It is
non-interactive because it is processing a script and not
waiting for user input between commands.
For more information, see info bash under the Bash Startup Files and Interactive Shells section.
The files /etc/profile
and
~/.bash_profile
are read when the
shell is invoked as an interactive login shell.
The base /etc/profile
below sets
some environment variables necessary for native language
support. Setting them properly results in:
The output of programs translated into the native language
Correct classification of characters into letters, digits and other classes. This is necessary for bash to properly accept non-ASCII characters in command lines in non-English locales
The correct alphabetical sorting order for the country
Appropriate default paper size
Correct formatting of monetary, time, and date values
This script also sets the INPUTRC
environment variable that makes Bash and Readline use the
/etc/inputrc
file created
earlier.
Replace [ll]
below
with the two-letter code for the desired language (e.g.,
“en”) and [CC]
with the two-letter code
for the appropriate country (e.g., “GB”). [charmap]
should be replaced
with the canonical charmap for your chosen locale.
The list of all locales supported by Glibc can be obtained by running the following command:
locale -a
Locales can have a number of synonyms, e.g. “ISO-8859-1” is also referred to as
“iso8859-1” and
“iso88591”. Some
applications cannot handle the various synonyms correctly, so
it is safest to choose the canonical name for a particular
locale. To determine the canonical name, run the following
command, where [locale
name]
is the output given by locale -a for your preferred
locale (“en_GB.iso88591”
in our example).
LC_ALL=[locale name]
locale charmap
For the “en_GB.iso88591” locale, the above command will print:
ISO-8859-1
This results in a final locale setting of “en_GB.ISO-8859-1”. It is important that the locale found using the heuristic above is tested prior to it being added to the Bash startup files:
LC_ALL=[locale name] locale country LC_ALL=[locale name] locale language LC_ALL=[locale name] locale charmap LC_ALL=[locale name] locale int_curr_symbol LC_ALL=[locale name] locale int_prefix
The above commands should print the language name, the character encoding used by the locale, the local currency, and the prefix to dial before the telephone number in order to get into the country. If any of the commands above fail with a message similar to the one shown below, this means that your locale was either not installed in Chapter 10 or is not supported by the default installation of Glibc.
locale: Cannot set LC_* to default locale: No such file or directory
If this happens, you should either install the desired locale using the localedef command, or consider choosing a different locale. Further instructions assume that there are no such error messages from Glibc.
Some packages beyond CLFS may also lack support for your chosen locale. One example is the X library (part of the X Window System), which outputs the following error message:
Warning: locale not supported by Xlib, locale set to C
Sometimes it is possible to fix this by removing the charmap part of the locale specification, as long as that does not change the character map that Glibc associates with the locale (this can be checked by running the locale charmap command in both locales). For example, one would have to change "de_DE.ISO-8859-15@euro" to "de_DE@euro" in order to get this locale recognized by Xlib.
Other packages can also function incorrectly (but may not necessarily display any error messages) if the locale name does not meet their expectations. In those cases, investigating how other Linux distributions support your locale might provide some useful information.
Once the proper locale settings have been determined, create
the /etc/profile
file:
cat > /etc/profile << "EOF"
# Begin /etc/profile
export LANG=[ll]
_[CC]
.[charmap]
export INPUTRC=/etc/inputrc
# End /etc/profile
EOF
The “C” (default) and “en_US” (the recommended one for United States English users) locales are different.
Setting the keyboard layout, screen font, and locale-related environment variables are the only internationalization steps needed to support locales that use ordinary single-byte encodings and left-to-right writing direction. More complex cases (including UTF-8 based locales) require additional steps and additional patches because many applications tend to not work properly under such conditions. These steps and patches are not included in the CLFS book and such locales are not yet supported by CLFS.
Part of the job of the localnet script is setting
the system's hostname. This needs to be configured in the
/etc/sysconfig/network
file.
Create the /etc/sysconfig/network
file and enter a hostname by running:
echo "HOSTNAME=[clfs]
" > /etc/sysconfig/network
[clfs]
needs to be
replaced with the name given to the computer. Do not enter the
Fully Qualified Domain Name (FQDN) here. That information will
be put in the /etc/hosts
file in
the next section.
If a network card is to be configured, decide on the IP
address, FQDN, and possible aliases for use in the /etc/hosts
file. The syntax is:
<IP address> myhost.example.org aliases
Unless the computer is to be visible to the Internet (i.e., there is a registered domain and a valid block of assigned IP addresses—most users do not have this), make sure that the IP address is in the private network IP address range. Valid ranges are:
Class Networks
A 10.0.0.0
B 172.16.0.0 through 172.31.0.255
C 192.168.0.0 through 192.168.255.255
A valid IP address could be 192.168.1.1. A valid FQDN for this
IP could be www.linuxfromscratch.org
(not recommended because this is a valid registered domain
address and could cause domain name server issues).
Even if not using a network card, an FQDN is still required. This is necessary for certain programs to operate correctly.
Create the /etc/hosts
file by
running:
cat > /etc/hosts << "EOF"
# Begin /etc/hosts (network card version)
127.0.0.1 localhost
[192.168.1.1]
[<HOSTNAME>.example.org]
[HOSTNAME]
# End /etc/hosts (network card version)
EOF
The [192.168.1.1]
and
[<HOSTNAME>.example.org]
values need to be changed for specific users or requirements
(if assigned an IP address by a network/system administrator
and the machine will be connected to an existing network).
If a network card is not going to be configured, create the
/etc/hosts
file by running:
cat > /etc/hosts << "EOF"
# Begin /etc/hosts (no network card version)
127.0.0.1 [<HOSTNAME>.example.org]
[HOSTNAME]
localhost
# End /etc/hosts (no network card version)
EOF
Some software that you may want to install later (e.g.,
various media players) expect the /dev/cdrom and /dev/dvd
symlinks to exist. Also, it may be convenient to put
references to those symlinks into /etc/fstab
. For each of your CD-ROM
devices, find the corresponding directory under /sys
(e.g., this can be /sys/block/hdd
) and run a command similar
to the following:
udevadm test /sys/block/hdd
Look at the lines containing the output of various *_id programs.
There are two approaches to creating symlinks. The first one is to use the model name and the serial number, the second one is based on the location of the device on the bus. If you are going to use the first approach, create a file similar to the following:
cat >/etc/udev/rules.d/82-cdrom.rules << EOF
# Custom CD-ROM symlinks
SUBSYSTEM=="block", ENV{ID_MODEL}=="SAMSUNG_CD-ROM_SC-148F", \
ENV{ID_REVISION}=="PS05", SYMLINK+="cdrom"
SUBSYSTEM=="block", ENV{ID_MODEL}=="PHILIPS_CDD5301", \
ENV{ID_SERIAL}=="5VO1306DM00190", SYMLINK+="cdrom1 dvd"
EOF
Although the examples in this book work properly, be aware that Udev does not recognize the backslash for line continuation. If modifying Udev rules with an editor, be sure to leave each rule on one physical line.
This way, the symlinks will stay correct even if you move the
drives to different positions on the IDE bus, but the
/dev/cdrom
symlink won't be
created if you replace the old SAMSUNG CD-ROM with a new
drive.
The SUBSYSTEM=="block" key is needed in order to avoid
matching SCSI generic devices. Without it, in the case with
SCSI CD-ROMs, the symlinks will sometimes point to the
correct /dev/srX
devices, and
sometimes to /dev/sgX
, which is
wrong.
The second approach yields:
cat >/etc/udev/rules.d/82-cdrom.rules << EOF
# Custom CD-ROM symlinks
SUBSYSTEM=="block", ENV{ID_TYPE}=="cd", \
ENV{ID_PATH}=="pci-0000:00:07.1-ide-0:1", SYMLINK+="cdrom"
SUBSYSTEM=="block", ENV{ID_TYPE}=="cd", \
ENV{ID_PATH}=="pci-0000:00:07.1-ide-1:1", SYMLINK+="cdrom1 dvd"
EOF
This way, the symlinks will stay correct even if you replace drives with different models, but place them to the old positions on the IDE bus. The ENV{ID_TYPE}=="cd" key makes sure that the symlink disappears if you put something other than a CD-ROM in that position on the bus.
Of course, it is possible to mix the two approaches.
As explained in
Section 11.4, “Device and Module Handling on a
CLFS System”, the order in which devices with the
same function appear in /dev
is
essentially random. E.g., if you have a USB web camera and a
TV tuner, sometimes /dev/video0
refers to the camera and /dev/video1
refers to the tuner, and
sometimes after a reboot the order changes to the opposite
one. For all classes of hardware except sound cards and
network cards, this is fixable by creating udev rules for
custom persistent symlinks. The case of network cards is
covered separately in Section 11.13,
“Configuring the network Script”, and sound
card configuration can be found in CBLFS.
For each of your devices that is likely to have this problem
(even if the problem doesn't exist in your current Linux
distribution), find the corresponding directory under
/sys/class
or /sys/block
. For video devices, this may be
/sys/class/video4linux/video
. Figure out the
attributes that identify the device uniquely (usually, vendor
and product IDs and/or serial numbers work):
X
udevadm info -a -p /sys/class/video4linux/video0
Then write rules that create the symlinks, e.g.:
cat >/etc/udev/rules.d/83-duplicate_devs.rules << EOF
# Persistent symlinks for webcam and tuner
KERNEL=="video*", SYSFS{idProduct}=="1910", SYSFS{idVendor}=="0d81", \
SYMLINK+="webcam"
KERNEL=="video*", SYSFS{device}=="0x036f", SYSFS{vendor}=="0x109e", \
SYMLINK+="tvtuner"
EOF
The result is that /dev/video0
and /dev/video1
devices still
refer randomly to the tuner and the web camera (and thus
should never be used directly), but there are symlinks
/dev/tvtuner
and /dev/webcam
that always point to the
correct device.
More information on writing Udev rules can be found in
/usr/share/doc/udev-124/index.html
.
This section only applies if a network card is to be configured.
If a network card will not be used, there is likely no need to
create any configuration files relating to network cards. If
that is the case, remove the network
symlinks from all run-level
directories (/etc/rc.d/rc*.d
).
Which interfaces are brought up and down by the network
script depends on the files and directories in the
/etc/sysconfig/network-devices
hierarchy. This directory should contain a sub-directory for
each interface to be configured, such as ifconfig.xyz
, where “xyz” is a network interface name. Inside
this directory would be files defining the attributes to this
interface, such as its IP address(es), subnet masks, and so
forth.
The following command creates a sample ipv4
file for the eth0 device:
cd /etc/sysconfig/network-devices &&
mkdir -v ifconfig.eth0 &&
cat > ifconfig.eth0/ipv4 << "EOF"
ONBOOT=yes
SERVICE=ipv4-static
IP=192.168.1.1
GATEWAY=192.168.1.2
PREFIX=24
BROADCAST=192.168.1.255
EOF
The values of these variables must be changed in every file
to match the proper setup. If the ONBOOT
variable is set to “yes” the network script will bring up
the Network Interface Card (NIC) during booting of the
system. If set to anything but “yes” the NIC will be ignored by the
network script and not be brought up.
The SERVICE
variable defines the
method used for obtaining the IP address. The
CLFS-Bootscripts package has a modular IP assignment format,
and creating additional files in the /etc/sysconfig/network-devices/services
directory allows other IP assignment methods. This is
commonly used for Dynamic Host Configuration Protocol (DHCP),
which is addressed in the BLFS book.
The GATEWAY
variable should
contain the default gateway IP address, if one is present. If
not, then comment out the variable entirely.
The PREFIX
variable needs to
contain the number of bits used in the subnet. Each octet in
an IP address is 8 bits. If the subnet's netmask is
255.255.255.0, then it is using the first three octets (24
bits) to specify the network number. If the netmask is
255.255.255.240, it would be using the first 28 bits.
Prefixes longer than 24 bits are commonly used by DSL and
cable-based Internet Service Providers (ISPs). In this
example (PREFIX=24), the netmask is 255.255.255.0. Adjust the
PREFIX
variable according to your
specific subnet.
If the system is going to be connected to the Internet, it
will need some means of Domain Name Service (DNS) name
resolution to resolve Internet domain names to IP addresses,
and vice versa. This is best achieved by placing the IP
address of the DNS server, available from the ISP or network
administrator, into /etc/resolv.conf
. Create the file by
running the following:
cat > /etc/resolv.conf << "EOF"
# Begin /etc/resolv.conf
domain [Your Domain Name]
nameserver [IP address of your primary nameserver]
nameserver [IP address of your secondary nameserver]
# End /etc/resolv.conf
EOF
Replace [IP address of the
nameserver]
with the IP address of the DNS most
appropriate for the setup. There will often be more than one
entry (requirements demand secondary servers for fallback
capability). If you only need or want one DNS server, remove
the second nameserver
line from the file. The IP address may also be a router on
the local network.
It is time to make the CLFS system bootable. This chapter
discusses creating an fstab
file,
building a kernel for the new CLFS system, and installing the
boot loader so that the CLFS system can be selected for booting
at startup.
The /etc/fstab
file is used by
some programs to determine where file systems are to be mounted
by default, in which order, and which must be checked (for
integrity errors) prior to mounting. Create a new file systems
table like this:
cat > /etc/fstab << "EOF"
# Begin /etc/fstab
# file system mount-point type options dump fsck
# order
/dev/[xxx]
/ [fff]
defaults 1 1
/dev/[yyy]
swap swap pri=1 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
devpts /dev/pts devpts gid=10,mode=620 0 0
shm /dev/shm tmpfs defaults 0 0
none /proc/openprom openpromfs defaults 0 0
# End /etc/fstab
EOF
Replace [xxx]
,
[yyy]
, and [fff]
with the values
appropriate for the system, for example, hda2
, hda5
, and
ext2
. For details on the six
fields in this file, see man 5
fstab.
The /dev/shm
mount point for
tmpfs
is included to allow
enabling POSIX-shared memory. The kernel must have the required
support built into it for this to work (more about this is in
the next section). Please note that very little software
currently uses POSIX-shared memory. Therefore, consider the
/dev/shm
mount point optional.
For more information, see Documentation/filesystems/tmpfs.txt
in the
kernel source tree.
The Linux package contains the Linux kernel.
A number of vulnerabilities have come to light after the stable kernel team stopped supporting 2.6.24. The following patch addresses them:
patch -Np1 -i ../linux-2.6.24.7-security_fixes-1.patch
Building the kernel involves a few steps—configuration,
compilation, and installation. Read the README
file in the kernel source tree for
alternative methods to the way this book configures the
kernel.
The following patch includes spitfire.h outside of kernel space in elf.h. It also adds spitfire.h to the list of headers installed on the system.
patch -Np1 -i ../linux-2.6.24.7-elf_spitfire_fix-1.patch
Prepare for compilation by running the following command:
make mrproper
This ensures that the kernel tree is absolutely clean. The kernel team recommends that this command be issued prior to each kernel compilation. Do not rely on the source tree being clean after un-tarring.
Configure the kernel via a menu-driven interface. Please note that the udev bootscript requires "rtc" and "tmpfs" to be enabled and built into the kernel, not as modules. CBLFS has some information regarding particular kernel configuration requirements of packages outside of CLFS at http://cblfs.cross-lfs.org/:
make menuconfig
Alternatively, make
oldconfig may be more appropriate in some
situations. See the README
file
for more information.
If desired, skip kernel configuration by copying the kernel
config file, .config
, from the
host system (assuming it is available) to the root directory
of the unpacked kernel sources. However, we do not recommend
this option. It is often better to explore all the
configuration menus and create the kernel configuration from
scratch.
Compile the kernel image and modules:
make
If using kernel modules, an /etc/modprobe.conf
file may be needed.
Information pertaining to modules and kernel configuration is
located in the kernel documentation in the Documentation
directory of the kernel
sources tree. Also, modprobe.conf(5)
may be of interest.
Be very careful when reading other documentation relating to
kernel modules because it usually applies to 2.4.x kernels
only. As far as we know, kernel configuration issues specific
to Hotplug and Udev are not documented. The problem is that
Udev will create a device node only if Hotplug or a
user-written script inserts the corresponding module into the
kernel, and not all modules are detectable by Hotplug. Note
that statements like the one below in the /etc/modprobe.conf
file do not work with
Udev:
alias char-major-XXX some-module
Because of the complications with Udev and modules, we strongly recommend starting with a completely non-modular kernel configuration, especially if this is the first time using Udev.
Install the modules, if the kernel configuration uses them:
make modules_install
After kernel compilation is complete, additional steps are
required to complete the installation. Some files need to be
copied to the /boot
directory.
Issue the following command to install the kernel:
cp vmlinux /boot/clfskernel-2.6.24.7
System.map
is a symbol file for
the kernel. It maps the function entry points of every
function in the kernel API, as well as the addresses of the
kernel data structures for the running kernel. Issue the
following command to install the map file:
cp -v System.map /boot/System.map-2.6.24.7
The kernel configuration file .config
produced by the make menuconfig step above
contains all the configuration selections for the kernel that
was just compiled. It is a good idea to keep this file for
future reference:
cp -v .config /boot/config-2.6.24.7
It is important to note that the files in the kernel source
directory are not owned by root
. Whenever a package is unpacked as
user root
(like we do inside
the final-system build environment), the files have the user
and group IDs of whatever they were on the packager's
computer. This is usually not a problem for any other package
to be installed because the source tree is removed after the
installation. However, the Linux source tree is often
retained for a long time. Because of this, there is a chance
that whatever user ID the packager used will be assigned to
somebody on the machine. That person would then have write
access to the kernel source.
If the kernel source tree is going to retained, run
chown -R 0:0 on
the linux-2.6.24.7
directory to
ensure all files are owned by user root
.
Some kernel documentation recommends creating a symlink
from /usr/src/linux
pointing
to the kernel source directory. This is specific to kernels
prior to the 2.6 series and must
not be created on a CLFS system as it can cause
problems for packages you may wish to build once your base
CLFS system is complete.
Also, the headers in the system's include
directory should always be the ones against which
Glibc was compiled (from the Linux-Headers package) and
should never be
replaced by the kernel headers.
Contains all the configuration selections for the kernel |
|
The engine of the Linux system. When turning on the computer, the kernel is the first part of the operating system that gets loaded. It detects and initializes all components of the computer's hardware, then makes these components available as a tree of files to the software and turns a single CPU into a multitasking machine capable of running scores of programs seemingly at the same time. |
|
A list of addresses and symbols; it maps the entry points and addresses of all the functions and data structures in the kernel |
Create a silo.conf
file defining
silo's boot menu:
cat > /etc/silo.conf << "EOF"
# Begin /etc/silo.conf
partition = 1 # Boot partition (= root partition)
root = /dev/sda1 # Root partition
timeout = 150 # Wait 15 seconds before booting the default section
image = /boot/clfskernel-2.6.24.7
label = linux
# End /etc/silo.conf
EOF
Now to make Silo bootable:
silo -f
Well done! The new CLFS system is installed! We wish you much success with your shiny new custom-built Linux system.
It may be a good idea to create an /etc/clfs-release
file. By having this file,
it is very easy for you (and for us if you need to ask for help
at some point) to find out which CLFS version is installed on
the system. Create this file by running:
echo 1.1.0 > /etc/clfs-release
Now that you have finished the book, do you want to be counted as a CLFS user? Head over to http://www.linuxfromscratch.org/cgi-bin/lfscounter.cgi and register as a CLFS user by entering your name and the first CLFS version you have used.
If you built your final system using the boot method, just run shutdown -r now to reboot again, using your newly-built kernel instead of the miminal one currently in use. If you chrooted, there are a few more steps.
The system you have created in this book is quite minimal, and most likely will not have the functionality you would need to be able to continue forward. By installing a few extra packages from the BLFS book while still in our current chroot environment, you can leave yourself in a much better position to continue on once you reboot into your new CLFS installation. Installing a text mode web browser, such as Lynx, you can easily view the BLFS book in one virtual terminal, while building packages in another. The GPM package will also allow you to perform copy/paste actions in your virtual terminals. Lastly, if you are in a situation where static IP configuration does not meet your networking requirements, installing packages such as Dhcpcd or PPP at this point might also be useful.
Now that we have said that, lets move on to booting our shiny new CLFS installation for the first time! First exit from the chroot environment:
logout
Then unmount the virtual file systems:
umount ${CLFS}/dev/pts umount ${CLFS}/dev/shm umount ${CLFS}/dev umount ${CLFS}/proc umount ${CLFS}/sys
Unmount the CLFS file system itself:
umount ${CLFS}
If multiple partitions were created, unmount the other partitions before unmounting the main one, like this:
umount ${CLFS}/usr umount ${CLFS}/home umount ${CLFS}
Now, reboot the system with:
shutdown -r now
Assuming the boot loader was set up as outlined earlier, CLFS 1.1.0 will boot automatically.
When the reboot is complete, the CLFS system is ready for use and more software may be added to suit your needs.
Thank you for reading this CLFS book. We hope that you have found this book helpful and have learned more about the system creation process.
Now that the CLFS system is installed, you may be wondering “What next?” To answer that question, we have compiled a list of resources for you.
Maintenance
Bugs and security notices are reported regularly for all software. Since a CLFS system is compiled from source, it is up to you to keep abreast of such reports. There are several online resources that track such reports, some of which are shown below:
Freshmeat.net (http://freshmeat.net/)
Freshmeat can notify you (via email) of new versions of packages installed on your system.
CERT (Computer Emergency Response Team)
CERT has a mailing list that publishes security alerts concerning various operating systems and applications. Subscription information is available at http://www.us-cert.gov/cas/signup.html.
Bugtraq
Bugtraq is a full-disclosure computer security mailing list. It publishes newly discovered security issues, and occasionally potential fixes for them. Subscription information is available at http://www.securityfocus.com/archive.
Community Driven Beyond Linux From Scratch
The Community Driven Beyond Linux From Scratch wiki covers installation procedures for a wide range of software beyond the scope of the CLFS Book. CBLFS is designed specifically to work with the CLFS book, and has all the necessary information to continue the builds in the same manner that CLFS uses. This is a community driven project, which means anyone can contribute and provide updates. The CBLFS project is located at http://cblfs.cross-lfs.org/.
CLFS Hints
The CLFS Hints are a collection of educational documents submitted by volunteers in the CLFS community. The hints are available at http://hints.cross-lfs.org/.
Mailing lists
There are several CLFS mailing lists you may subscribe to if you are in need of help, want to stay current with the latest developments, want to contribute to the project, and more. See Chapter 1 - Mailing Lists for more information.
The Linux Documentation Project
The goal of The Linux Documentation Project (TLDP) is to collaborate on all of the issues of Linux documentation. The TLDP features a large collection of HOWTOs, guides, and man pages. It is located at http://www.tldp.org/.
ABI |
Application Binary Interface |
ALFS |
Automated Linux From Scratch |
ALSA |
Advanced Linux Sound Architecture |
API |
Application Programming Interface |
ASCII |
American Standard Code for Information Interchange |
ATA |
Advanced Technology Attachment (see IDE) |
BIOS |
Basic Input/Output System |
bless |
manipulate a filesystem so that OF will boot from it |
BLFS |
Beyond Linux From Scratch |
BSD |
Berkeley Software Distribution |
chroot |
change root |
CLFS |
Cross-Compiled Linux From Scratch |
CMOS |
Complementary Metal Oxide Semiconductor |
COS |
Class Of Service |
CPU |
Central Processing Unit |
CRC |
Cyclic Redundancy Check |
DHCP |
Dynamic Host Configuration Protocol |
DNS |
Domain Name Service |
EGA |
Enhanced Graphics Adapter |
ELF |
Executable and Linkable Format |
EOF |
End of File |
EQN |
equation |
EVMS |
Enterprise Volume Management System |
ext2 |
second extended file system |
FAQ |
Frequently Asked Questions |
FHS |
Filesystem Hierarchy Standard |
FIFO |
First-In, First Out |
FQDN |
Fully Qualified Domain Name |
FTP |
File Transfer Protocol |
GB |
Gibabytes |
GCC |
GNU Compiler Collection |
GID |
Group Identifier |
GMT |
Greenwich Mean Time |
HTML |
Hypertext Markup Language |
IDE |
Integrated Drive Electronics |
IEEE |
Institute of Electrical and Electronic Engineers |
IO |
Input/Output |
IP |
Internet Protocol |
IPC |
Inter-Process Communication |
IRC |
Internet Relay Chat |
ISO |
International Organization for Standardization |
ISP |
Internet Service Provider |
KB |
Kilobytes |
LED |
Light Emitting Diode |
LFS |
Linux From Scratch |
LSB |
Linux Standard Base |
MB |
Megabytes |
MBR |
Master Boot Record |
MD5 |
Message Digest 5 |
NIC |
Network Interface Card |
NLS |
Native Language Support |
NNTP |
Network News Transport Protocol |
NPTL |
Native POSIX Threading Library |
OF |
Open Firmware |
OSS |
Open Sound System |
PCH |
Pre-Compiled Headers |
PCRE |
Perl Compatible Regular Expression |
PID |
Process Identifier |
PTY |
pseudo terminal |
QA |
Quality Assurance |
QOS |
Quality Of Service |
RAM |
Random Access Memory |
RPC |
Remote Procedure Call |
RTC |
Real Time Clock |
SCO |
The Santa Cruz Operation |
SATA |
Serial ATA |
SGR |
Select Graphic Rendition |
SHA1 |
Secure-Hash Algorithm 1 |
SMP |
Symmetric Multi-Processor |
TLDP |
The Linux Documentation Project |
TFTP |
Trivial File Transfer Protocol |
TLS |
Thread-Local Storage |
UID |
User Identifier |
umask |
user file-creation mask |
USB |
Universal Serial Bus |
UTC |
Coordinated Universal Time |
UUID |
Universally Unique Identifier |
VC |
Virtual Console |
VGA |
Video Graphics Array |
VT |
Virtual Terminal |
We would like to thank the following people and organizations for their contributions to the Linux From Scratch Project.
Gerard Beekmans <gerard AT linuxfromscratch D0T org> – LFS Creator, LFS Project Leader
Matthew Burgess <matthew AT linuxfromscratch D0T org> – LFS Project Leader, LFS Technical Writer/Editor, LFS Release Manager
Archaic <archaic AT linuxfromscratch D0T org> – LFS Technical Writer/Editor, HLFS Project Leader, BLFS Editor, Hints and Patches Project Maintainer
Nathan Coulson <nathan AT linuxfromscratch D0T org> – LFS-Bootscripts Maintainer
Bruce Dubbs <bdubbs AT linuxfromscratch D0T org> – BLFS Project Leader
Manuel Canales Esparcia <manuel AT linuxfromscratch D0T org> – LFS/BLFS/HLFS XML and XSL Maintainer
Jim Gifford <jim AT linuxfromscratch D0T org> – LFS Technical Writer, Patches Project Leader
Jeremy Huntwork <jhuntwork AT linuxfromscratch D0T org> – LFS Technical Writer, LFS LiveCD Maintainer, ALFS Project Leader
Anderson Lizardo <lizardo AT linuxfromscratch D0T org> – Website Backend-Scripts Maintainer
Ryan Oliver <ryan AT linuxfromscratch D0T org> – LFS Toolchain Maintainer
James Robertson <jwrober AT linuxfromscratch D0T org> – Bugzilla Maintainer
Tushar Teredesai <tushar AT linuxfromscratch D0T org> – BLFS Book Editor, Hints and Patches Project Leader
Countless other people on the various LFS and BLFS mailing lists who helped make this book possible by giving their suggestions, testing the book, and submitting bug reports, instructions, and their experiences with installing various packages.
Manuel Canales Esparcia <macana AT lfs-es D0T com> – Spanish LFS translation project
Johan Lenglet <johan AT linuxfromscratch D0T org> – French LFS translation project
Anderson Lizardo <lizardo AT linuxfromscratch D0T org> – Portuguese LFS translation project
Thomas Reitelbach <tr AT erdfunkstelle D0T de> – German LFS translation project
Scott Kveton <scott AT osuosl D0T org> – lfs.oregonstate.edu mirror
Mikhail Pastukhov <miha AT xuy D0T biz> – lfs.130th.net mirror
William Astle <lost AT l-w D0T net> – ca.linuxfromscratch.org mirror
Jeremy Polen <jpolen AT rackspace D0T com> – us2.linuxfromscratch.org mirror
Tim Jackson <tim AT idge D0T net> – linuxfromscratch.idge.net mirror
Jeremy Utley <jeremy AT linux-phreak D0T net> – lfs.linux-phreak.net mirror
Andres Meggiotto <sysop AT mesi D0T com D0T ar> – lfs.mesi.com.ar mirror
Manuel Canales Esparcia <manuel AT linuxfromscratch D0T org> – lfsmirror.lfs-es.info mirror
Eduardo B. Fonseca <ebf AT aedsolucoes D0T com D0T br> – br.linuxfromscratch.org mirror
Barna Koczka <barna AT siker D0T hu> – hu.linuxfromscratch.org mirror
UK Mirror Service – linuxfromscratch.mirror.ac.uk mirror
Martin Voss <Martin D0T Voss AT ada D0T de> – lfs.linux-matrix.net mirror
Guido Passet <guido AT primerelay D0T net> – nl.linuxfromscratch.org mirror
Bastiaan Jacques <baafie AT planet D0T nl> – lfs.pagefault.net mirror
Roel Neefs <lfs-mirror AT linuxfromscratch D0T rave D0T org> – linuxfromscratch.rave.org mirror
Justin Knierim <justin AT jrknierim D0T de> – www.lfs-matrix.de mirror
Stephan Brendel <stevie AT stevie20 D0T de> – lfs.netservice-neuss.de mirror
Antonin Sprinzl <Antonin D0T Sprinzl AT tuwien D0T ac D0T at> – at.linuxfromscratch.org mirror
Fredrik Danerklint <fredan-lfs AT fredan D0T org> – se.linuxfromscratch.org mirror
Parisian sysadmins <archive AT doc D0T cs D0T univ-paris8 D0T fr> – www2.fr.linuxfromscratch.org mirror
Alexander Velin <velin AT zadnik D0T org> – bg.linuxfromscratch.org mirror
Dirk Webster <dirk AT securewebservices D0T co D0T uk> – lfs.securewebservices.co.uk mirror
Thomas Skyt <thomas AT sofagang D0T dk> – dk.linuxfromscratch.org mirror
Simon Nicoll <sime AT dot-sime D0T com> – uk.linuxfromscratch.org mirror
Pui Yong <pyng AT spam D0T averse D0T net> – sg.linuxfromscratch.org mirror
Stuart Harris <stuart AT althalus D0T me D0T uk> – lfs.mirror.intermedia.com.sg mirror
Jason Andrade <jason AT dstc D0T edu D0T au> – au.linuxfromscratch.org mirror
Christine Barczak <theladyskye AT linuxfromscratch D0T org> – LFS Book Editor
Timothy Bauscher
Robert Briggs
Ian Chilton
Jeroen Coumans <jeroen AT linuxfromscratch D0T org> – Website Developer, FAQ Maintainer
Alex Groenewoud – LFS Technical Writer
Marc Heerdink
Mark Hymers
Seth W. Klein – FAQ maintainer
Nicholas Leippe <nicholas AT linuxfromscratch D0T org> – Wiki Maintainer
Simon Perreault
Scot Mc Pherson <scot AT linuxfromscratch D0T org> – LFS NNTP Gateway Maintainer
Alexander Patrakov <semzx AT newmail D0T ru> – LFS Technical Writer
Greg Schafer <gschafer AT zip D0T com D0T au> – LFS Technical Writer
Jesse Tie-Ten-Quee – LFS Technical Writer
Jeremy Utley <jeremy AT linuxfromscratch D0T org> – LFS Technical Writer, Bugzilla Maintainer, LFS-Bootscripts Maintainer
Zack Winkles <zwinkles AT gmail D0T com> – LFS Technical Writer
Dean Benson <dean AT vipersoft D0T co D0T uk> for several monetary contributions
Hagen Herrschaft <hrx AT hrxnet D0T de> for donating a 2.2 GHz P4 system, now running under the name of Lorien
VA Software who, on behalf of Linux.com, donated a VA Linux 420 (former StartX SP2) workstation
Mark Stone for donating Belgarath, the linuxfromscratch.org server
Every package built in CLFS relies on one or more other packages in order to build and install properly. Some packages even participate in circular dependencies, that is, the first package depends on the second which in turn depends on the first. Because of these dependencies, the order in which packages are built in CLFS is very important. The purpose of this page is to document the dependencies of each package built in CLFS.
For each package we build, we have listed three types of dependencies. The first lists what other packages need to be available in order to compile and install the package in question. The second lists what packages, in addition to those on the first list, need to be available in order to run the testsuites. The last list of dependencies are packages that require this package to be built and installed in its final location before they are built and installed. In most cases, this is because these packages will hardcode paths to binaries within their scripts. If not built in a certain order, this could result in paths of /tools/bin/[binary] being placed inside scripts installed to the final system. This is obviously not desirable.
This page contains dependency information for packages specific to Sparc.
The Open Publication works may be reproduced and distributed in whole or in part, in any medium physical or electronic, provided that the terms of this license are adhered to, and that this license or an incorporation of it by reference (with any options elected by the author(s) and/or publisher) is displayed in the reproduction.
Proper form for an incorporation by reference is as follows:
Copyright © <year> by <author's name or designee>. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, vX.Y or later (the latest version is presently available at http://www.opencontent.org/openpub/).
The reference must be immediately followed with any options elected by the author(s) and/or publisher of the document (see section VI).
Commercial redistribution of Open Publication-licensed material is permitted.
Any publication in standard (paper) book form shall require the citation of the original publisher and author. The publisher and author's names shall appear on all outer surfaces of the book. On all outer surfaces of the book the original publisher's name shall be as large as the bridgehead of the work and cited as possessive with respect to the bridgehead.
The copyright to each Open Publication is owned by its author(s) or designee.
The following license terms apply to all Open Publication works, unless otherwise explicitly stated in the document.
Mere aggregation of Open Publication works or a portion of an Open Publication work with other works or programs on the same media shall not cause this license to apply to those other works. The aggregate work shall contain a notice specifying the inclusion of the Open Publication material and appropriate copyright notice.
SEVERABILITY. If any part of this license is found to be unenforceable in any jurisdiction, the remaining portions of the license remain in force.
NO WARRANTY. Open Publication works are licensed and provided "as is" without warranty of any kind, express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose or a warranty of non-infringement.
All modified versions of documents covered by this license, including translations, anthologies, compilations and partial documents, must meet the following requirements:
The modified version must be labeled as such.
The person making the modifications must be identified and the modifications dated.
Acknowledgement of the original author and publisher if applicable must be retained according to normal academic citation practices.
The location of the original unmodified document must be identified.
The original author's (or authors') name(s) may not be used to assert or imply endorsement of the resulting document without the original author's (or authors') permission.
In addition to the requirements of this license, it is requested from and strongly recommended of redistributors that:
If you are distributing Open Publication works on hardcopy or CD-ROM, you provide email notification to the authors of your intent to redistribute at least thirty days before your manuscript or media freeze, to give the authors time to provide updated documents. This notification should describe modifications, if any, made to the document.
All substantive modifications (including deletions) be either clearly marked up in the document or else described in an attachment to the document.
Finally, while it is not mandatory under this license, it is considered good form to offer a free copy of any hardcopy and CD-ROM expression of an Open Publication-licensed work to its author(s).
The author(s) and/or publisher of an Open Publication-licensed document may elect certain options by appending language to the reference to or copy of the license. These options are considered part of the license instance and must be included with the license (or its incorporation by reference) in derived works.
A. To prohibit distribution of substantively modified versions without the explicit permission of the author(s). "Substantive modification" is defined as a change to the semantic content of the document, and excludes mere changes in format or typographical corrections.
To accomplish this, add the phrase `Distribution of substantively modified versions of this document is prohibited without the explicit permission of the copyright holder.' to the license reference or copy.
B. To prohibit any publication of this work or derivative works in whole or in part in standard (paper) book form for commercial purposes is prohibited unless prior permission is obtained from the copyright holder.
To accomplish this, add the phrase 'Distribution of the work or derivative of the work in any standard (paper) book form is prohibited unless prior permission is obtained from the copyright holder.' to the license reference or copy.
(This is not considered part of the license.)
Open Publication works are available in source format via the Open Publication home page at http://works.opencontent.org/.
Open Publication authors who want to include their own license on Open Publication works may do so, as long as their terms are not more restrictive than the Open Publication license.
If you have questions about the Open Publication License, please contact David Wiley at dw@opencontent.org, and/or the Open Publication Authors' List at opal@opencontent.org, via email.
To subscribe to the Open Publication Authors' List: Send E-mail to opal-request@opencontent.org with the word "subscribe" in the body.
To post to the Open Publication Authors' List: Send E-mail to opal@opencontent.org or simply reply to a previous post.
To unsubscribe from the Open Publication Authors' List: Send E-mail to opal-request@opencontent.org with the word "unsubscribe" in the body.