Contents
Installed Programs:
make-ca
Installed Directories:
/etc/ssl/{certs,local} and
/etc/pki/{nssdb,anchors,tls/{certs,java}}
Copyright © 2001-2021 The BLFS Development Team
Copyright © 2001-2021, The BLFS Development Team
All rights reserved.
This book is licensed under a Creative Commons License.
Computer instructions may be extracted from the book under the MIT License.
Linux® is a registered trademark of Linus Torvalds.
Published 2021-09-01
| Revision History | ||
|---|---|---|
| Revision 11.0 | 2021-09-01 | Twenty-fourth Release |
| Revision 10.1 | 2021-03-01 | Twenty-third Release |
| Revision 10.0 | 2020-09-01 | Twenty-second Release |
| Revision 9.1 | 2020-03-01 | Twenty-first Release |
| Revision 9.0 | 2019-09-01 | Twentieth release |
| Revision 8.4 | 2019-03-01 | Nineteenth release |
| Revision 8.3 | 2018-09-01 | Eighteenth release |
| Revision 8.2 | 2018-03-02 | Seventeenth release |
| Revision 8.1 | 2017-09-01 | Sixteenth release |
| Revision 8.0 | 2017-02-25 | Fifteenth release |
| Revision 7.10 | 2016-09-07 | Fourteenth release |
| Revision 7.9 | 2016-03-08 | Thirteenth release |
| Revision 7.8 | 2015-10-01 | Twelfth release |
| Revision 7.7 | 2015-03-06 | Eleventh release |
| Revision 7.6 | 2014-09-23 | Tenth release |
| Revision 7.5 | 2014-03-05 | Ninth release |
| Revision 7.4 | 2013-09-14 | Eighth release |
| Revision 6.3 | 2008-08-24 | Seventh release |
| Revision 6.2 | 2007-02-14 | Sixth release |
| Revision 6.1 | 2005-08-14 | Fifth release |
| Revision 6.0 | 2005-04-02 | Fourth release |
| Revision 5.1 | 2004-06-05 | Third release |
| Revision 5.0 | 2003-11-06 | Second release |
| Revision 1.0 | 2003-04-25 | First release |
Abstract
This book follows on from the Linux From Scratch book. It introduces and guides the reader through additions to the system including networking, graphical interfaces, sound support, and printer and scanner support.
Having helped out with Linux From Scratch for a short time, I noticed that we were getting many queries as to how to do things beyond the base LFS system. At the time, the only assistance specifically offered relating to LFS were the LFS hints (https://www.linuxfromscratch.org/hints). Most of the LFS hints are extremely good and well written but I (and others) could still see a need for more comprehensive help to go Beyond LFS — hence BLFS.
BLFS aims to be more than the LFS-hints converted to XML although much of our work is based around the hints and indeed some authors write both hints and the relevant BLFS sections. We hope that we can provide you with enough information to not only manage to build your system up to what you want, whether it be a web server or a multimedia desktop system, but also that you will learn a lot about system configuration as you go.
Thanks as ever go to everyone in the LFS/BLFS community; especially those who have contributed instructions, written text, answered questions and generally shouted when things were wrong!
Finally, we encourage you to become involved in the community; ask questions on the mailing list or news gateway and join in the fun on #lfs and #lfs-support at Libera. You can find more details about all of these in the Introduction section of the book.
Enjoy using BLFS.
Mark Hymers
markh <at> linuxfromscratch.org
BLFS Editor (July 2001–March 2003)
I still remember how I found the BLFS project and started using the instructions that were completed at the time. I could not believe how wonderful it was to get an application up and running very quickly, with explanations as to why things were done a certain way. Unfortunately, for me, it wasn't long before I was opening applications that had nothing more than "To be done" on the page. I did what most would do, I waited for someone else to do it. It wasn't too long before I am looking through Bugzilla for something easy to do. As with any learning experience, the definition of what was easy kept changing.
We still encourage you to become involved as BLFS is never really finished. Contributing or just using, we hope you enjoy your BLFS experience.
Larry Lawrence
larry <at> linuxfromscratch.org
BLFS Editor (March 2003–June 2004)
The BLFS project is a natural progression of LFS. Together, these projects provide a unique resource for the Open Source Community. They take the mystery out of the process of building a complete, functional software system from the source code contributed by many talented individuals throughout the world. They truly allow users to implement the slogan “Your distro, your rules”.
Our goal is to continue to provide the best resource available that shows you how to integrate many significant Open Source applications. Since these applications are constantly updated and new applications are developed, this book will never be complete. Additionally, there is always room for improvement in explaining the nuances of how to install the different packages. To make these improvements, we need your feedback. I encourage you to participate on the different mailing lists, news groups, and IRC channels to help meet these goals.
Bruce Dubbs
bdubbs <at> linuxfromscratch.org
BLFS Editor (June 2004–December 2006 and February 2011–now)
My introduction to the [B]LFS project was actually by accident. I was trying to build a GNOME environment using some how-tos and other information I found on the web. A couple of times I ran into some build issues and Googling pulled up some old BLFS mailing list messages. Out for curiosity, I visited the Linux From Scratch web site and shortly thereafter was hooked. I've not used any other Linux distribution for personal use since.
I can't promise anyone will feel the sense of satisfaction I felt after building my first few systems using [B]LFS instructions, but I sincerely hope that your BLFS experience is as rewarding for you as it has been for me.
The BLFS project has grown significantly the last couple of years. There are more package instructions and related dependencies than ever before. The project requires your input for continued success. If you discover that you enjoy building BLFS, please consider helping out in any way you can. BLFS requires hundreds of hours of maintenance to keep it even semi-current. If you feel confident enough in your editing skills, please consider joining the BLFS team. Simply contributing to the mailing list discussions with sound advice and/or providing patches to the book's XML will probably result in you receiving an invitation to join the team.
Randy McMurchy
randy <at> linuxfromscratch.org
BLFS Editor (December 2006–January 2011)
This version of the book is intended to be used when building on top of a system built using the LFS book. Every effort has been made to ensure accuracy and reliability of the instructions. Many people find that using the instructions in this book after building the current stable or development version of LFS provides a stable and very modern Linux system.
Enjoy!
Randy McMurchy
August 24th, 2008
Last updated on
This book is mainly aimed at those who have built a system based on the LFS book. It will also be useful for those who are using other distributions, but for one reason or another want to manually build software and are in need of some assistance. Note that the material contained in this book, in particular the dependency listings, is based upon the assumption that you are using a base LFS system with every package listed in the LFS book already installed and configured. BLFS can be used to create a range of diverse systems and so the target audience is probably nearly as wide as that of the LFS book. If you found LFS useful, you should also like this!
Since Release 7.4, the BLFS book version matches the LFS book version. This book may be incompatible with a previous or later release of the LFS book.
Last updated on
This book is divided into the following parts.
This part contains information which is essential to the rest of the book.
Here we introduce basic configuration and security issues. We also discuss a range of editors, file systems, and shells which aren't covered in the main LFS book.
In this section we cover libraries which are often needed by the rest of the book as well as system utilities. Information on Programming (including recompiling GCC to support its full range of languages) concludes this part.
Here we cover how to connect to a network when you aren't using the simple static IP setup given in the main LFS book. Networking libraries and command-line networking tools are also covered here.
Here we deal with setting up mail and other servers (such as FTP, Apache, etc.).
This part explains how to set up a basic X Window System installation along with some generic X libraries and Window managers.
For those who want to use the K Desktop Environment or some parts of it, this part covers it.
GNOME is the main alternative to KDE in the Desktop Environment arena.
Xfce is a lightweight alternative to GNOME and KDE.
LXDE is another lightweight alternative to GNOME and KDE.
Office programs and graphical web browsers are important to most people. They, along with some generic X software can be found in this part of the book.
Here we cover setting multimedia libraries and drivers along with some audio, video and CD-writing programs.
The PST part of the book covers document handling with applications like Ghostscript, CUPS and DocBook to installing texlive.
The Appendices cover information which doesn't belong in the main book; they are mainly there as a reference.
Last updated on
The Beyond Linux From Scratch book is designed to carry on from where the LFS book leaves off. But unlike the LFS book, it isn't designed to be followed straight through. Reading the Which sections of the book? part of this chapter should help guide you through the book.
Please read most of this part of the book carefully as it explains quite a few of the conventions used throughout the book.
Unlike the Linux From Scratch book, BLFS isn't designed to be followed in a linear manner. This is because LFS provides instructions on how to create a base system which is capable of turning into anything from a web server to a multimedia desktop system. BLFS attempts to guide you in the process of going from the base system to your intended destination. Choice is very much involved.
Everyone who reads the book will want to read certain sections. The Introduction part, which you are currently reading, contains generic information. Especially take note of the information in Chapter 2, Important Information, as this contains comments about how to unpack software, issues related to using different locales and various other aspects which apply throughout the book.
The part on Post LFS Configuration and Extra Software is where most people will want to turn next. This deals with not just configuration but also Security (Chapter 4, Security), File Systems (Chapter 5, File Systems and Disk Management), Editors (Chapter 6, Editors) and Shells (Chapter 7, Shells). Indeed, you may wish to reference certain parts of this chapter (especially the sections on Editors and File Systems) while building your LFS system.
Following these basic items, most people will want to at least browse through the General Libraries and Utilities part of the book. This part contains information on many items which are prerequisites for other sections of the book as well as some items (such as Chapter 13, Programming) which are useful in their own right. Note that you don't have to install all of these libraries and packages found in this part to start with as each BLFS installation procedure tells you which packages it depends upon so you can choose the program you want to install and see what it needs.
Likewise, most people will probably want to look at the Networking part. It deals with connecting to the Internet or your LAN (Chapter 14, Connecting to a Network) using a variety of methods such as DHCP and PPP, and with items such as Networking Libraries (Chapter 17, Networking Libraries) and various basic networking programs and utilities.
Once you have dealt with these basics, you may wish to configure more advanced network services. These are dealt with in the Servers part of the book. Those wanting to build servers should find a good starting point there. Note that this section also contains information on various database packages.
The next parts of the book principally deal with desktop systems. This portion of the book starts with a part talking about X plus Window and Display Managers. This part also deals with some generic X-based libraries (Chapter 25, X Libraries). After this, KDE and GNOME are given their own parts which are followed by one on X Software.
The book then moves on to deal with Multimedia packages. Note that many people may want to use the ALSA-1.2.5 instructions from this chapter quite near the start of their BLFS journey; they are placed here simply because it is the most logical place for them.
The final part of the main BLFS book deals with Printing, Scanning and Typesetting. This is useful for most people with desktop systems and even those who are creating mainly server systems will find it useful.
We hope you enjoy using BLFS and find it useful.
Last updated on
To make things easy to follow, there are a number of conventions used throughout the book. Following are some examples:
./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 to identify references to specific commands.
install-info: unknown option
`--dir-file=/mnt/lfs/usr/info/dir'This form of text (fixed width text) is showing screen output, probably a result from issuing a command. It is also used to show filenames such as
/boot/grub/grub.conf
Emphasis
This form of text is used for several purposes in the book but mainly to emphasize important points or to give examples as to what to type.
https://www.linuxfromscratch.org/
This form of text is used for hypertext links external to the book such as HowTos, download locations, websites, etc.
This form of text is used for links internal to the book such as another section describing a different package.
cat > $LFS/etc/group << "EOF"
root:x:0:
bin:x:1:
......
EOF
This type of section is used mainly when creating configuration files. The first command (in bold) tells the system to create the file
$LFS/etc/groupfrom whatever is typed on the following lines until the sequence EOF is encountered. Therefore, this whole section is generally typed as seen.
<REPLACED
TEXT>
This form of text is used to encapsulate text that should be modified and is not to be typed as seen, or copy and pasted. Note that the square brackets are not part of the text, but should be substituted for as well.
root
This form of text is used to show a specific system user or group reference in the instructions.
When packages are created, the authors depend on prior work. In order to build a package in BLFS, these dependencies must be built prior to the desired package. For each package, any prerequisite packages are listed in one or more separate sections: Required, Recommended, and Optional.
These dependencies are the minimum prerequisite packages required to build the package. Omitted from the list are packages in LFS and required dependencies of other required packages.
These dependencies are those that the BLFS editors have determined are important to give the package reasonable capabilities. Package installation instructions assume they are installed. If a recommended package is not desired, the instructions may need to be modified to accommodate the missing package.
These dependencies are those that the package may use. Integration of optional dependencies may be automatic by the package or may need additional instructions not presented by BLFS. Optional packages may be listed without corresponding BLFS instructions. In this case it is up to the user to determine appropriate installation instructions.
Some packages have specific needs regarding the kernel configuration. The general layout is the following:
Master section --->
Subsection --->
[*] Required parameter [CONFIG_REQU_PAR]
<*> Required parameter (not as module) [CONFIG_REQU_PAR_NMOD]
<*/M> Required parameter (could be a module) [CONFIG_REQU_PAR_MOD]
<*/M/ > Optional parameter [CONFIG_OPT_PAR]
[ ] Incompatible parameter [CONFIG_INCOMP_PAR]
< > Incompatible parameter (even as module) [CONFIG_INCOMP_PAR_MOD]
[CONFIG_...] on the right gives the name of the option, so
you can easily check whether it is set in your config file. The meaning of the various
entries is:
Master section top level menu item Subsection submenu item Required parameter the option could be either built-in or not selected: it must be selected Required parameter (not as module) the option could be either built-in, module, or not selected: it must be selected as built-in Required parameter (could be a module) the option could be either built-in, module, or not selected: it must be selected, either as built-in or module Optional parameter rarely used: the option could be either built-in, module, or not selected: it may be selected at will Incompatible parameter the option could be either built-in or not selected: it must not be selected Incompatible parameter (even as module) the option could be either built-in, module, or not selected: it must not be selected
Note that, depending on other selections, the angle brackets (<>) may appear as braces ({}), if the option cannot be unselected, or even dashes (-*- or -M-), when the choice is imposed. The help text about the option specifies the other selections on which this option relies, and how those other selections are set.
As in LFS, each package in BLFS has a build time listed in Standard Build Units (SBUs). These times are relative to the time it took to build binutils in LFS and are intended to provide some insight into how long it will take to build a package. Most times listed are for a single processor or core to build the package. In some cases, large, long running builds tested on multi-core systems have SBU times listed with comments such as '(parallelism=4)'. These values indicate testing was done using multiple cores. Note that while this speeds up the build on systems with the appropriate hardware, the speedup is not linear and to some extent depends on the individual package and specific hardware used.
For packages which use ninja (e.g. anything using meson) or rust, by default all cores are used so similar comments will be seen on such packages even when the build time is minimal.
Where even a parallel build takes more than 15 SBU, on certain machines the time may be considerably greater even when the build does not use swap. In particular, different micro-architectures will build some files at different relative speeds and this can introduce delays when certain make targets wait for another file to be created. Where a large build uses a lot of C++ files, processors with Simultaneous Multi Threading will share the Floating Point Unit and can take 45% longer than when using four 'prime' cores (measured on an intel i7 using taskset and keeping the other cores idle).
Some packages do not support parallel builds and using -j1 for the make command is required. Packages that are known to have such limits are marked as such in the text.
Last updated on
This is BLFS-BOOK version 11.0 dated September 1st, 2021. This is the 11.0 branch of the BLFS book, currently targeting the LFS 11.0 book. For development versions, if this version is older than a month, it's likely that your mirror hasn't been synchronized recently and a newer version is probably available for download or viewing. Check one of the mirror sites at https://www.linuxfromscratch.org/mirrors.html for an updated version.
Last updated on
The BLFS project has a number of mirrors set up world-wide to make it easier and more convenient for you to access the website. Please visit the https://www.linuxfromscratch.org/mirrors.html website for the list of current mirrors.
Last updated on
Within the BLFS instructions, each package has two references for finding the source files for the package—an HTTP link and an FTP link (some packages may only list one of these links). Every effort has been made to ensure that these links are accurate. However, the World Wide Web is in continuous flux. Packages are sometimes moved or updated and the exact URL specified is not always available.
To overcome this problem, the BLFS Team, with the assistance of Oregon State University Open Source Lab, has made an HTTP/FTP site available through world wide mirrors. See https://www.linuxfromscratch.org/blfs/download.html#sources for a list. These sites have all the sources of the exact versions of the packages used in BLFS. If you can't find the BLFS package you need at the listed addresses, get it from these sites.
We would like to ask a favor, however. Although this is a public resource for you to use, please do not abuse it. We have already had one unthinking individual download over 3 GB of data, including multiple copies of the same files that are placed at different locations (via symlinks) to make finding the right package easier. This person clearly did not know what files he needed and downloaded everything. The best place to download files is the site or sites set up by the source code developer. Please try there first.
Last updated on
Current release: 11.0 – September 1st, 2021
Changelog Entries:
September 1st, 2021
[bdubbs] - Release of BLFS-11.0.
August 30th, 2021
[renodr] - Update to ntfs-3g-2021.8.22 (Security Update). Fixes #14583.
[renodr] - Fix a regression in Samba's default configuration. Fixes #15474.
[renodr] - Update to gtk-4.4.0. Fixes #15452.
[pierre] - Create a link from /opt/kf5/share/polkit-1 to its
counterpart in /usr/share/ so that action files
get installed to a place where Polkit finds them.
[thomas] - Upgrade to proftpd-1.3.7c. Fixes #15482.
August 29th, 2021
[ken] - fetchmail: Recommend using ssl where possible to ensure that TLS is enforced.
[renodr] - Fix a regression in BIND identified upstream. Fixes #15472.
[ken] - Update to seamonkey-2.53.9 (security update). Fixes #15464.
[bdubbs] - Update to pipewire-0.3.34. Fixes #15470.
[bdubbs] - Update to soundtouch-2.3.0. Fixes #15447.
August 28th, 2021
August 27th, 2021
[ken] - Update to iso-codes_4.7.0. Fixes #15460.
[bdubbs] - Update to mercurial-5.9. Fixes #15433.
[bdubbs] - Update to doxygen-1.9.2. Fixes #15429.
[bdubbs] - Update to umockdev-0.16.2. Fixes #15459.
[bdubbs] - Update to bluez-5.61. Fixes #15451.
[thomas] - Update to php-8.0.10. Fixes #15469.
[thomas] - Update to wireshark-3.4.8. Fixes #15463.
[bdubbs] - Update to libsoup-2.74.0. Fixes #15448.
August 26th, 2021
[bdubbs] - Update to json-glib-1.6.6. Fixes #15416.
[ken] - Update to mesa-21.2.1. Fixes #15349.
[ken] - Add --wrap-mode=nofallback to gdk-pixbuf and pango. Fixes #15466.
[ken] - Update to Unicode-Collate-1.31 (perl module). Fixes #15446.
[renodr] - Update to blfs-systemd-units-20210819. Fixes #15467.
[pierre] - Update to qemu-6.1.0. Fixes #15456.
[pierre] - Update to thunderbird-91.0.3. Fixes #15445.
[pierre] - Update to openssh-8.7p1, with ssh-askpass. Fixes #15439.
[pierre] - Update to licap-2.53 with PAM. Fixes #15406.
[pierre] - Add a sed to apr-1.7.0 to fix a security issue. Fixes #15453.
[pierre] - Update to libgcrypt-1.9.4 (security fix). Fixes #15450.
[xry111] - Update to harfbuzz-2.9.0. Fixes #15428.
[xry111] - Update to glib-2.68.4. Fixes #15432.
[xry111] - Update to cmake-3.21.2. Fixes #15462.
[xry111] - Update to libarchive-3.5.2 (security update). Fixes #15449.
[renodr] - Update to samba-4.14.7. Fixes #15457.
[renodr] - Update to Mako-1.1.5 (Python Module). Fixes #15442.
[renodr] - Update to balsa-2.6.3. Fixes #15431.
[renodr] - Update to openldap-2.5.7. Fixes #14530.
[renodr] - Update to git-2.33.0. Fixes #15409.
[renodr] - Update to Pygments-2.10.0 (Python Module). Fixes #15402.
August 25th, 2021
August 23rd, 2021
[renodr] - Update to gnome-shell-extensions-40.4. Fixes #15420.
[renodr] - Update to gnome-shell-40.4. Fixes #15420.
[renodr] - Update to mutter-40.4. Fixes #15419.
[renodr] - Update to network-manager-applet-1.24.0. Fixes #15413.
[renodr] - Update to libnma-1.8.32. Fixes #15438.
[bdubbs] - Update to libreoffice-7.2.0.4. Fixes #15434.
[renodr] - Update to gsound-1.0.3. Fixes #15425.
[renodr] - Update to NetworkManager-1.32.10. Fixes #15423.
[renodr] - Update to gnome-desktop-40.4. Fixes #15427.
[ken] - Update to dvisvgm-2.12. Fixes #15412.
[ken] - Patch ghostscript-9.54.0 to fix a segfault.
August 22nd, 2021
August 21st, 2021
August 20th, 2021
[renodr] - Update to gexiv2-0.12.3. Fixes #15400.
August 19th, 2021
August 18th, 2021
August 17th, 2021
August 16th, 2021
[ken] - Firefox-91 and Thunderbird: Replace create-mach-environment by MACH_USE_SYSTEM_PYTHON=1. Fixes #15405.
August 15th, 2021
[bdubbs] - Update to plasma-5.22.4. Fixes #15211.
[bdubbs] - Update to kf5-apps-21.08.0. Includes kate and kwave. Fixes #15256.
[bdubbs] - Update to mlt-7.0.1. Fixes #14896.
[bdubbs] - Update to kf5-5.85.0. Includes extra-cmake-modules, breeze-icons, and oxygen-icons. Fixes #15267.
[renodr] - Update to gjs-1.68.3. Fixes #15398.
[renodr] - Update to boost-1.77.0. Fixes #15392.
[renodr] - Update to libwebp-1.2.1. Fixes #15393.
[renodr] - Update to eog-40.3. Fixes #15394.
[renodr] - Update to gnome-user-docs-40.4. Fixes #15395.
[renodr] - Update to libepoxy-1.5.9. Fixes #15396.
[renodr] - Update to libgudev-237. Fixes #15397.
[renodr] - Fix building Firefox-91.0 on i686 systems.
August 14th, 2021
[ken] - Update to x264-20210814. Addresses #7555.
[ken] - Update to ImageMagick-7.1.0-4. Addresses #7859.
[ken] Add a patch to firefox-91 to work around the unexplained build failures I'm seeing on two systems.
[ken] Update qtwebengine-20210401 to use build_fixes-4 patch for glibc-2.34. Please note that binutils-2.37 from LFS-dev needs the patch which is now in LFS.
August 13th, 2021
[renodr] - Update to thunderbird-91.0 (Security Update). Fixes #15279.
[bdubbs] - Update to postgresql-13.4. Fixes #15385.
[bdubbs] - Update to unbound-1.13.2. Fixes #15386.
[bdubbs] - Update to LVM2-2.03.13. Fixes #15383.
[renodr] - Update to epiphany-40.3. Fixes #15387.
[renodr] - Update to evolution-data-server-3.40.4. Fixes #15390.
[renodr] - Update to evolution-3.40.4. Fixes #15389.
[renodr] - Update to gnome-maps-40.4. Fixes #15391.
August 12th, 2021
[ken] - Update to node.js-v14.17.5 (security update). Fixes #15382.
[renodr] - Update to pango-1.48.8. Fixes #15384.
[renodr] - Update to enchant-2.3.1. Fixes #15376.
[renodr] - Update to gnome-autoar-0.4.0. Fixes #15375.
[renodr] - Update to fetchmail-6.4.21. Fixes #15370.
[renodr] - Update to gjs-1.68.2. Fixes #15363.
August 11th, 2021
[bdubbs] - Update to SDL2-2.0.16. Fixes #15380.
[bdubbs] - Update to NetworkManager-1.32.8. Fixes #15379.
[bdubbs] - Update to libjpeg-turbo-2.1.1. Fixes #15377.
[bdubbs] - Update to c-ares-1.17.2. Fixes #15374.
[timtas] - Remove ifconfig from net-tools-2.10. Fixes #15381.
[renodr] - Add a patch for xf86-video-ati that fixes various performance regressions and allows for the driver to build with a future version of xorg-server. This also allows users of ATI graphics cards on SysV systems to be able to run GNOME and KDE Plasma 5 again. Fixes #14129.
August 10th, 2021
[ken] - Update to JS-78.13.0, firefox-91.0esr and introduce a firefox-legacy page for firefox-78.13.0esr (all are security fixes). Fixes #15367 and #15369. If in doubt about which version of firefox to use, consult the firefox page in the wiki which is linked from both.
[bdubbs] - Update to ModemManager-1.16.10. Fixes #15372.
[bdubbs] - Update to xrdb-1.2.1 (Xorg application). Fixes #15371.
[bdubbs] - Update to net-tools-2.10. Fixes #15366.
August 8th, 2021
August 7th, 2021
August 6th, 2021
[renodr] - Fix building guile-3.0.7 with glibc-2.34.
[bdubbs] - Update to pipewire-0.3.33. Fixes #15356.
[bdubbs] - Update to glib-networking-2.68.2. Fixes #15354.
[bdubbs] - Update to SCons-4.2.0. Fixes #15353.
[bdubbs] - Update to libqmi-1.30.0. Fixes #15352.
[bdubbs] - Update to nss-3.69. Fixes #15351.
[bdubbs] - Fix an issue when building gcc identified upstream. Fixes #15350.
August 5th, 2021
[renodr] - Update to gnome-maps-40.3. Fixes #15263.
[renodr] - Update to gnome-disk-utility-40.2. Fixes #15266.
[renodr] - Update to evince-40.4. Fixes #15274.
[bdubbs] - Update to udisks-2.9.3. Fixes #15348.
[bdubbs] - Update to poppler-21.08.0. Fixes #15342.
[bdubbs] - Update to jasper-2.0.33. Fixes #15341.
August 4th, 2021
[bdubbs] - Update to asciidoctor-2.0.16. Fixes #15346.
[bdubbs] - Update to libqmi-1.28.8. Fixes #15344.
[bdubbs] - Update to libcap-2.52. Fixes #15343.
[bdubbs] - Update to NetworkManager-1.32.6. Fixes #15323.
[bdubbs] - Update to krb5-1.19.2. Fixes #15309.
[bdubbs] - Update to libinput-1.18.1 (Xorg driver). Fixes #15345.
[bdubbs] - Update to xwd-1.0.8 (Xorg Application). Fixes #15338.
[bdubbs] - Update to libXft-2.3.4 (Xorg Library). Fixes #15340.
[bdubbs] - Update to libXfont2-2.0.5 (Xorg Library). Fixes #15339.
[thomas] - Fix a typo in xinit instructions.
August 1st, 2021
July 30th, 2021
[bdubbs] - Update to php-8.0.9. Fixes #15332.
[bdubbs] - Update to cbindgen-0.20.0. Fixes #15331.
[bdubbs] - Fix dependencies for elogind and p11kit. Fixes #15333.
[bdubbs] - Fix gcr-3.40.0 to build properly with meson-0.59. Fixes #15329.
[bdubbs] - Update to xorg-server-1.20.13. Fixes #15328.
[bdubbs] - Update to mesa-21.1.6. Fixes #15326.
[bdubbs] - Update to libstatgrab-0.92.1. Fixes #15327.
[bdubbs] - Update to libblockdev-2.26. Fixes #15325.
July 30th, 2021
[bdubbs] - Update to libreoffice-7.1.5.2. Fixes #15305.
[ken] - Update to fetchmail-6.4.20 (security fix). Fixes #15324.
[ken] - Update Perl Module Dependencies - Alien-Build-2.41, Business-ISBN-Data-20210112.006, Config-AutoConf-0.320, DateTime-Format-Strptime-1.79, DateTime-Locale-1.32, DateTime-TimeZone-2.47, Exception-Class-1.45, FFI-CheckLib-0.28, File-ShareDir-1.118, HTTP-Message-6.33, libwww-perl-6.55, Net-HTTP-6.21, Net-SSLeay-1.90, Path-Tiny-0.118, Role-Tiny-2.002004, Specio-0.47, Test-Fatal-0.016, Test-File-1.448, Test-LeakTrace-0.17, Test-MockModule-v0.176.0, Test-Needs-0.002009, Test-Warnings-0.031, Test2-Suite-0.000140, Text-CSV_XS-1.46, XML-LibXML-2.0207. Addresses #13850.
[ken] - Update to node.js-v14.17.4 (security fix). Fixes #15330.
[bdubbs] - Update to pulseaudio-15.0. Fixes #15320.
[bdubbs] - Update to imlib2-1.7.2. Fixes #15319.
[bdubbs] - Update to cmake-3.21.1. Fixes #15317.
[bdubbs] - Update to libmbim-1.26.0. Fixes #15316.
July 29th, 2021
July 28th, 2021
[renodr] - Update to mutter-40.3. Fixes #15271.
[renodr] - Update to gnome-shell-40.3. Fixes #15269.
[renodr] - Update to gnome-shell-extensions-40.3. Fixes #15270.
[renodr] - Update to gdm-40.1. Fixes #15308.
[renodr] - Update to gnome-user-docs-40.3. Fixes #15262.
[renodr] - Update to yelp-40.3. Fixes #15261.
[bdubbs] - Update to pipewire-0.3.32. Fixes #15300.
[bdubbs] - Update to shadow-4.9. Fixes #15304.
[bdubbs] - Update to dbus-python-1.2.18 (Python module). Fixes #15299.
[bdubbs] - Update to libidn-2.3.2. Fixes #15295.
[bdubbs] - Update to libidn-1.38. Fixes #15315.
[renodr] - Update to samba-4.14.6. Fixes #15276.
[thomas] - Update to bind-9.16.19, bind-utils-9.16.19. Fixes #15302.
[thomas] - Update to libuv-1.42.0. Fixes #15298.
July 27th, 2021
July 26th, 2021
[timtas] - Update to fltk-1.3.7. Fixes #15312.
July 25th, 2021
[renodr] - Update to WebKitGTK+-2.32.3 (Security Update). Fixes #15306.
July 23rd, 2021
[ken] - perl dependant module Alien::Libxml2 was missing its required dependency of Path::Tiny.
[ken] - Reinstate perl module dependency Scalar::List::Utils which provides core module List::Utils. List::AllUtils-0.19 requires version 1.56 at runtime, but perl-5.34.0 shipped with 1.55. Fixes #15307.
[ken] - Update to mutt-2.1.1. Fixes #15294.
[ken] - Update to seamonkey-2.53.8.1 (security fix). Fixes #15303.
[renodr] - Guard systemd against CVE-2021-33910. Fixes #15297.
July 22nd, 2021
July 21st, 2021
[timtas] - Update to curl-7.78.0. Fixes #15301.
July 20th, 2021
[renodr] - Update to ModemManager-1.16.8. Fixes #15273.
July 19th, 2021
July 18th, 2021
July 17th, 2021
July 13th, 2021
July 12th, 2021
[renodr] - Adjust cups-pk-helper to no longer use deprecated syntax that will cause issues with future versions of CUPS.
[renodr] - Adjust polkit-gnome to be able to pull user icons again.
[renodr] - Update to abiword-3.0.5. Fixes #15237.
[renodr] - Update to WebKitGTK+-2.32.2. Fixes #15258.
[thomas] - Fix install path of docs in libusb.
July 11th, 2021
July 10th, 2021
[renodr] - Update to mercurial-5.8.1. Fixes #15254.
July 9th, 2021
[renodr] - Update to icewm-2.6.0. Fixes #15255.
[renodr] - Update to evolution-data-server-3.40.3. Finishes #15257.
[renodr] - Update to evolution-3.40.3. Part of #15257.
[renodr] - Update to at-spi2-core-2.40.3. Fixes #15259.
[ken] - Update to gucharmap-13.0.8. Fixes #15244.
[renodr] - Update to gtk+-3.24.30. Fixes #15250.
[renodr] - Update to gnome-terminal-3.40.3. Fixes #15251.
[renodr] - Update to xorg-server-1.20.12. Fixes #15252.
[renodr] - Update to harfbuzz-2.8.2. Fixes #15253.
[bdubbs] - Update to ruby-3.0.2. Fixes #15249.
[bdubbs] - Update to bluez-5.60. Fixes #15248.
[bdubbs] - Update to libuv-1.41.1. Fixes #15247.
[bdubbs] - Update to libbytesize-2.6. Fixes #15246.
[bdubbs] - Update to mariadb-10.6.3. Fixes #15243.
[renodr] - Update to opencv-4.5.3. Fixes #15241.
[renodr] - Update to gnupg-2.2.29. Fixes #15242.
July 8th, 2021
[renodr] - Update to Python-3.9.6 (Security Update). Fixes #15221.
[renodr] - Update to systemd-249 (Security Update). Fixes #15245.
[renodr] - Adapt gptfdisk to merged-/usr changes. Partially fixes #15223.
[renodr] - Adapt ntfs-3g to merged-/usr changes. Partially fixes #15223.
[renodr] - Adapt keyutils to merged-/usr changes. Partially fixes #15223.
July 7th, 2021
July 6th, 2021
July 5th, 2021
July 1st, 2021
[ken] - Patch gcc-11.1.0 to match LFS (this will be needed when firefox moves to 91ESR). Fixes #15225.
[renodr] - Update to mesa-21.1.4. Fixes #15231.
[renodr] - Update to babl-0.1.88. Fixes #15230.
[renodr] - Update to nspr-4.32. Fixes #15229.
[renodr] - Update to php-8.0.8 (security update). Fixes #15232.
June 30th, 2021
June 29th, 2021
June 28th, 2021
[bdubbs] - Update to libuninameslist-20210626. Fixes #15220.
June 27th, 2021
June 26th, 2021
[timtas] - Update to dovecot-2.3.15. Fixes #15208.
June 24th, 2021
[renodr] - Update to cmake-3.20.5. Fixes #15207.
[renodr] - Update to libva-2.12.0. Fixes #15210.
[renodr] - Update to mariadb-10.5.11. Fixes #15212.
[renodr] - Update to xf86-input-libinput-1.1.0. Fixes #15213.
[renodr] - Update to gpgme-1.16.0. Fixes #15215.
[renodr] - Update to glu-9.0.2. Fixes #15216.
[renodr] - Update to vlc-3.0.16. Fixes #15204.
[renodr] - Update to graphviz-2.47.3. Fixes #15200.
June 23rd, 2021
June 22nd, 2021
June 21st, 2021
June 20th, 2021
June 19th, 2021
[renodr] - Update to exiv2-0.27.4 (security update). Fixes #15199.
June 18th, 2021
[renodr] - Update to python-dbusmock-0.23.1. Fixes #15189.
[renodr] - Update to mutter-40.2.1. Fixes #15190.
[renodr] - Update to NetworkManager-1.32.0. Fixes #15192.
[renodr] - Update to upower-0.99.12. Fixes #15194.
[renodr] - Update to mesa-21.1.3. Fixes #15196.
[bdubbs] - Update to cups-filters-1.28.9. Fixes #15191.
[bdubbs] - Update to bind-9.16.18. Fixes #15193.
[renodr] - Update to node-v14.17.1. Fixes #15187.
June 17th, 2021
[bdubbs] - Update to plasma-5.22.1. Fixes #14728.
[renodr] - Update to pcre-8.45. Fixes #15188.
[bdubbs] - Update to kf5-apps-21.04.2. Includes kate and kwave. Fixes #14730.
[renodr] - Update to nano-5.8. Fixes #15186.
[renodr] - Update to proftpd-1.3.7b. Fixes #15185.
[renodr] - Update to nfs-utils-2.5.4. Fixes #15184.
June 16th, 2021
[renodr] - Update to cmake-3.20.4. Fixes #15183.
[renodr] - Update to enchant-2.3.0. Fixes #15181.
[renodr] - Update to unrar-6.0.7. Fixes #15182.
[renodr] - Update to postfix-3.6.1. Fixes #15180.
[renodr] - Update to bluez-5.59. Fixes #15178.
[renodr] - Update to tracker and tracker-miners 3.1.2. Fixes #15175.
[renodr] - Update to libwpe-1.10.1. Fixes #15166.
[renodr] - Update to alsa-lib and alsa-utils 1.2.5.1. Fixes #15173.
[xry111] - Update to GRUB-2.06. Fixes #15152.
June 15th, 2021
[renodr] - Update to PDFBox/FontBox 2.0.24 (Security Update). Fixes #15176.
June 14th, 2021
[bdubbs] - Update to kf5-5.83.0. Includes extra-cmake-modules, breeze-icons, and oxygen-icons. Fixes #14773.
[bdubbs] - Update to plasma-wayland-protocols-1.3.0.
June 12th, 2021
June 11th, 2021
[bdubbs] - Update to ristretto-0.11.0. Fixes #15172.
[bdubbs] - Update to vlc-3.0.15. Fixes #15171.
[bdubbs] - Update to gnumeric-1.12.50. Fixes #15169.
[bdubbs] - Update to goffice-0.10.50. Fixes #15168.
[bdubbs] - Update to libpcap-1.10.1. Fixes #15167.
[bdubbs] - Update to libksba-1.6.0. Fixes #15165.
[bdubbs] - Update to nss-3.67. Fixes #15164.
June 10th, 2021
[renodr] - Update to glib-2.68.3. Fixes #15163.
[renodr] - Update to mutter-40.2. Fixes #15161.
[renodr] - Update to gnome-shell-40.2. Fixes #15159.
[renodr] - Update to gnome-shell-extensions-40.2. Fixes #15160.
[renodr] - Update to gnupg-2.2.28. Fixes #15162.
[bdubbs] - Update to gptfdisk-1.0.8. Fixes #15158.
[bdubbs] - Update to pipewire-0.3.30. Fixes #15157.
[bdubbs] - Update to xscreensaver-6.01. Fixes #15156.
[bdubbs] - Update to fuse3-3.10.4. Fixes #15155.
June 9th, 2021
June 8th, 2021
[renodr] - Update to xterm-368. Fixes #15147.
[renodr] - Update to sysstat-12.5.4. Fixes #15146.
[ken] - Update to Intel microcode-20210608 (security fix). Fixes #15149.
[renodr] - Update to libiodbc-3.52.15. Fixes #15144.
[renodr] - Update to nettle-3.7.3. Fixes #15143.
[renodr] - Update to wpebackend-fdo-1.10.0. Fixes #15145.
[thomas] - Upgrade to xfce4-settings-4.16.2. Fixes #15148.
June 7th, 2021
[renodr] - Update to network-manager-applet-1.22.0. Fixes #15020.
[renodr] - Update to ModemManager-1.16.6. Fixes #15136.
[renodr] - Update to icewm-2.4.0. Fixes #15140.
[bdubbs] - Update to git-2.32.0. Fixes #15138.
[bdubbs] - Update to Unicode-Collate-1.30 (Perl module). Fixes #15137.
[renodr] - Update to pidgin-2.14.5. Fixes #14976.
[renodr] - Update to epiphany-40.2. Fixes #14955.
[renodr] - Update to gnome-maps-40.2. Fixes #15119.
[renodr] - Update to evolution-3.40.2. Fixes #15118.
[timtas] - Update to openldap-2.5.5. Fixes #15115.
June 6th, 2021
[renodr] - Update to eog-40.2. Fixes #15129.
[renodr] - Fix installing documentation in cdrtools.
[renodr] - Update to yelp-40.2. Fixes #15134.
[renodr] - Update to Nautilus-40.2. Fixes #15121.
[renodr] - Adapt rpcbind to merged-/usr changes.
[renodr] - Update to evolution-data-server-3.40.2. Part of #15118.
[renodr] - Update to gnome-autoar-0.3.3. Fixes #15120.
[renodr] - Update to yelp-xsl-40.2. Fixes #15135.
[renodr] - Update to vala-0.52.4. Fixes #15117.
[renodr] - Update to libX11-1.7.2 (Xorg Library). Fixes #15133.
[bdubbs] - Update to wireshark-3.4.6. Fixes #15132.
[bdubbs] - Update to mpg123-1.28.0. Fixes #15132.
[bdubbs] - Update to at-spi2-core-2.40.2. Fixes #15130.
[bdubbs] - Update to polkit-0.119. Fixes #15110.
[bdubbs] - Update to pipewire-0.3.29. Fixes #15109.
[bdubbs] - Update to gnome-terminal-3.40.2. Fixes #15128.
[bdubbs] - Update to vte-0.64.2. Fixes #15131.
[bdubbs] - Update to libogg-1.3.5. Fixes #15126.
[bdubbs] - Update to nfs-utils-2.5.3. Fixes #15125.
[bdubbs] - Update to librsvg-2.50.7. Fixes #15124.
[bdubbs] - Update to libqmi-1.28.6. Fixes #15123.
[bdubbs] - Update to dash-0.5.11.4. Fixes #15122.
June 5th, 2021
June 4th, 2021
June 3rd, 2021
[renodr] - Adapt btrfs-progs to merged-/usr changes.
[renodr] - Adapt libpwquality to merged-/usr changes.
[renodr] - Adapt the timer/unit creation for pciutils, usbutils, and logrotate to the merged-/usr changes.
[renodr] - Adapt cracklib to merged-/usr changes.
[renodr] - Adapt reiserfsprogs to merged-/usr changes.
[renodr] - Adapt IW to merged-/usr changes.
[bdubbs] - Update to mesa-21.1.2. Fixes #15107.
[bdubbs] - Update to libinput-1.18.0 (Xorg driver). Fixes #15106.
[bdubbs] - Update to libmbim-1.24.8. Fixes #15104.
[bdubbs] - Update to poppler-21.06.0. Fixes #15102.
[bdubbs] - Update to qca-2.3.3. Fixes #15101.
[bdubbs] - Update to gsl-2.7. Fixes #15100.
[timtas] - Update to alsa-lib-1.2.5, alsa-tools-1.2.5, alsa-utils-1.2.5, and alsa-plugins 1.2.5. Fixes #15099.
June 1st, 2021
[renodr] - Adapt libnsl to merged-/usr changes.
[renodr] - Adapt wpa_supplicant to merged-/usr changes.
[renodr] - Update to NetworkManager-1.30.4. Fixes #14927.
[xry111] - Add asciidoctor, to build man page for util-linux (in LFS).
[ken] - Update to firefox-78.11.0esr (security fixes) and JS-78.11.0. Fixes #15098.
May 31st, 2021
May 29th, 2021
[ken] - Fix seamonkey build breakage with nss-3.65 by using the shipped nss. Fixes #15079.
May 28th, 2021
May 27th, 2021
[xry111] - Upgrade to graphviz-2.47.2. Fixes #15091.
[bdubbs] - Upgrade to libinput-1.17.3 (Xorg driver). Fixes #15090.
[bdubbs] - Upgrade to pcre2-10.37. Fixes #15088.
[bdubbs] - Upgrade to nspr-4.31. Fixes #15087.
[thomas] - Update to dhcp-4.4.2-P1. Fixes #15089.
[renodr] - Update to WebKitGTK+-2.32.1. Fixes #15019.
[renodr] - Add wpebackend-fdo to the book. Finishes #14913.
[renodr] - Add libwpe to the book. Part of #14913.
May 26th, 2021
[timtas] - Upgrade to curl-7.77.0. Fixes #15086.
[renodr] - Update to ModemManager-1.16.4. Fixes #14923.
[renodr] - Stop moving the PAM Module to /lib/security in gnome-keyring.
[bdubbs] - Upgrade to librsvg-2.50.6. Fixes #15084.
[renodr] - Fix building v4l-utils with GCC-11.1 if Qt5 is installed.
[timtas] - Update to httpd-2.4.48. Fixes #15085.
May 25th, 2021
May 24th, 2021
[renodr] - Use the correct systemd unit in Gutenprint.
[renodr] - Stop modifying the systemd unit for cups-browsed now that we're using OpenPrinting CUPS.
[ken] - Add patch to enable building gst-plugins-good against Qt5 or some other dependencies.
[ken] - Upgrade to mutt-2.0.7. Fixes #14996.
[renodr] - Use the correct unit name for CUPS.
[bdubbs] - Upgrade to IO-Socket-SSL-2.071 (Perl module). Fixes #15077.
[bdubbs] - Upgrade to links-2.23. Fixes #15078.
May 22nd, 2021
[bdubbs] - Upgrade to logrotate-3.18.1. Fixes #15076.
[bdubbs] - Upgrade to gtkmm3-3.24.5. Fixes #15075.
[bdubbs] - Upgrade to libepoxy-1.5.8. Fixes #15074.
[bdubbs] - Upgrade to pangomm-2.46.1. Fixes #15073.
[bdubbs] - Upgrade to atkmm-2.28.2. Fixes #15072.
[renodr] - Disable valgrind in libdrm to allow sysprof to build properly.
May 21st, 2021
May 20th, 2021
[bdubbs] - Update to glibmm-2.66.1. Fixes #15069.
[bdubbs] - Update to libsigc++-3.0.7. Fixes #15068.
[bdubbs] - Update to libsigc++-2.10.7. Fixes #15067.
[bdubbs] - Update to pipewire-0.3.28. Fixes #15066.
[bdubbs] - Update to mesa-21.1.1. Fixes #15065.
[bdubbs] - Update to bind9-9.16.16. Fixes #15064.
[bdubbs] - Update to Test-Differences-0.68 (Perl module). Fixes #15063.
[renodr] - Update to GCC-11.1.0. Fixes #14993.
[renodr] - Update to Python-3.9.5. Fixes #14993.
[renodr] - Update to systemd-248. Fixes #14968.
May 19th, 2021
[bdubbs] - Update to libdrm-2.4.106. Fixes #15062.
[bdubbs] - Update to Test-Differences-0.68 (Perl Module). Fixes #15061.
[bdubbs] - Update to MarkupSafe-2.0.1 (Python Module). Fixes #15060.
[bdubbs] - Update to Jinja2-3.0.1 (Python Module). Fixes #15059.
[ken] - Fix building gst-plugins-base with meson-0.58.0.
[renodr] - Fix building Fluxbox with gcc-11.1.
[renodr] - Remove unnecessary configure switches from the xf86-input-wacom driver.
[renodr] - Remove instructions for moving the dbus shared library to /lib.
May 18th, 2021
[renodr] - Update the default path in shadow to be consistent with LFS.
[renodr] - Force libxcb to use python3, even if python2 is present on the system.
[renodr] - Adapt some scripts in subversion to python3.
[renodr] - Remove unnecessary instructions from hdparm due to the merged-/usr transition.
[thomas] - Use OpenPrinting CUPS. Thanks to Marty Jack for the pointer.
[ken] - in Linux-PAM do not move libs to /lib.
[bdubbs] - Update to pango-1.48.5. Fixes #15057.
[bdubbs] - Update to libX11-1.7.1 (xorg library; Security Release). Fixes #15056.
[bdubbs] - Update to unrar-6.0.6. Fixes #15053.
[bdubbs] - Update to decorator-5.0.9 (Python module). Fixes #15054.
May 17th, 2021
[bdubbs] - Update to postgresql-13.3. Fixes #15040.
[ken] - Patch exiv2-0.27.3 (security fix). Fixes #15052.
[bdubbs] - Update to nss-3.65. Fixes #15044.
[bdubbs] - Update to libidn-1.37. Fixes #15048.
[bdubbs] - Update to btrfs-progs-v5.12.1. Fixes #15038.
[bdubbs] - Update to mutter-40.1. Fixes #15043.
[bdubbs] - Update to gnome-shell-extensions-40.1. Fixes #15042.
[bdubbs] - Update to gnome-shell-40.1. Fixes #15041.
[bdubbs] - Update to decorator-5.0.8 (Python module). Fixes #15051.
[bdubbs] - Update to rxvt-unicode-9.26. Fixes #15047.
[bdubbs] - Update to libqmi-1.28.4. Fixes #15045.
[ken] - DHCP - remove instruction to move dhclient to /sbin and use /usr/sbin for dhclient-script.
[timtas] - Update to fltk-1.3.6. Fixes #15050.
May 16th, 2021
[bdubbs] - Update to libxml2-2.9.12. Fixes #15039.
[renodr] - Restore the ICU-69 patch in node.js.
May 15th, 2021
[renodr] - Create symlinks to /usr/sbin instead of /sbin in ntfs-3g (for consistency).
[renodr] - Fix building fuse-3.10.3 with GCC-11.1.0 and also stop moving libraries/binaries to /bin and /lib.
[renodr] - Stop moving /usr/bin/traceroute to /bin in the installation instructions for traceroute.
[renodr] - Remove an unnecessary test adaptation to keyutils now that merged-/usr changes have landed in LFS.
[renodr] - Make changes to the MIT Kerberos V5 page to stop moving libraries and programs to /lib and /bin.
[renodr] - Install pax in /usr/bin instead of /bin.
[renodr] - Remove instructions for installing cpio in /bin. In merged-/usr, /usr/bin is fine.
May 14th, 2021
[ken] - Remove instructions from libtirpc for moving libraries to /lib.
[ken] - Remove instructions from libmnl for moving libraries to /lib.
[ken] - Remove instructions from iptables for installing to /sbin and /lib/xtables.
[renodr] - Disable generating documentation on cyrus-sasl until Sphinx and docutils are both fixed.
[renodr] - Remove instructions from PCRE for moving libraries to /lib.
May 13th, 2021
[bdubbs] - Update to vlc-3.0.14. Fixes #15033.
[bdubbs] - Update to libtasn1-4.17.0. Fixes #15037.
[bdubbs] - Update to highlight-4.1. Fixes #15036.
[bdubbs] - Update to mousepad-0.5.5. Fixes #15034.
[bdubbs] - Update to node.js-14.17.0. Fixes #15030.
[renodr] - Removed the instructions for moving the popt library in the event that /usr is not available.
[bdubbs] - Update to MarkupSafe-2.0.0 (Python module). Fixes #15032.
[bdubbs] - Update to jinja2-3.0.0 (Python module). Fixes #15031.
[bdubbs] - Update to sudo-1.9.7. Fixes #15029.
[bdubbs] - Update to libXfixes-6.0.0. Fixes #15028.
[renodr] - Update to libidn2-2.3.1. Fixes #15035.
May 12th, 2021
[renodr] - Update to fuse-3.10.3. Fixes #14902.
[renodr] - Update to fetchmail-6.4.19. Fixes #14930.
[renodr] - Update to apache-ant-1.10.10. Fixes #14925.
[renodr] - Update to samba-4.14.4 (Security Update). Fixes #14928.
[renodr] - Update to llvm-12.0.0. Fixes #14911.
[pierre] - Patch firefox so that HTML videos do not crash, if compiled with rust-1.52.0.
May 11th, 2021
[pierre] - Fix the pkgconfig file for lua-5.2: the library was -llua instead of -llua5.2.
[bdubbs] - Update to btrfs-progs-5.12. Fixes #15021.
[bdubbs] - Update to gtk-4.2.1. Fixes #15013.
[bdubbs] - Update to glib-2.68.2. Fixes #15027.
[bdubbs] - Update to hdparm-9.62. Fixes #15023.
[bdubbs] - Update to guile-3.0.7. Fixes #15018.
[bdubbs] - Update to feh-3.7. Fixes #15017.
[bdubbs] - Update to rpcbind-1.2.6. Fixes #15024.
[bdubbs] - Update to libtirpc-1.3.2. Fixes #15025.
[thomas] - Add a patch to make curl compatible with openldap-2.5.4. Fixes #15026.
May 10th, 2021
[bdubbs] - Update to nautilus-40.1. Fixes #14965.
[bdubbs] - Update to gnome-user-docs-40.1. Fixes #14983.
[bdubbs] - Update to gnome-terminal-3.40.1. Fixes #14969.
[bdubbs] - Update to gnome-system-monitor-40.1. Fixes #14966.
[bdubbs] - Update to gnome-maps-40.1. Fixes #14984.
[bdubbs] - Update to gnome-disk-utility-40.1. Fixes #14977.
[bdubbs] - Update to gnome-calculator-40.1. Fixes #14967.
[bdubbs] - Update to evolution-3.40.1. Fixes #14961.
[bdubbs] - Update to eog-40.1. Fixes #14987.
[bdubbs] - Update to gnome-settings-daemon-40.0.1. Fixes #14909.
[bdubbs] - Update to gvfs-1.48.1. Fixes #14963.
[bdubbs] - Update to libwnck-40.0. Fixes #15022.
[bdubbs] - Update to evolution-data-server-3.40.1. Partially fixes #14961.
[bdubbs] - Update to gnome-online-accounts-3.40.0. Fixes #14937.
[bdubbs] - Update to gnome-desktop-40.1. Fixes #14986.
[bdubbs] - Update to gnome-autoar-0.3.2. Fixes #14964.
[bdubbs] - Update to gjs-1.68.1. Fixes #15009.
May 9th, 2021
[ken] - Update to firefox-78.10.1 and js78.10.1. Fixes #14995.
[ken] - Fix seamonkey build breakage with rust-1.52.0.
[ken] - Update to rustc-1.52.0 (security fix). Fixes #15000.
[bdubbs] - Update to mariadb-10.5.10. Fixes #15008.
[bdubbs] - Update to qpdf-10.3.2. Fixes #15014.
[bdubbs] - Update to File-Which-1.27 (Perl module). Fixes #15015.
[bdubbs] - Update to at_3.2.2. Fixes #15012.
[bdubbs] - Update to pipewire-0.3.27. Fixes #15011.
[bdubbs] - Update to LVM2.2.03.12. Fixes #15007.
[bdubbs] - Update to vlc-3.0.13. Fixes #14975.
[bdubbs] - Update to libreoffice-7.1.3.2. Fixes #15010.
[bdubbs] - Update to qemu-6.0.0. Fixes #14956.
[bdubbs] - Update to mercurial-5.8. Fixes #14992.
[bdubbs] - Update to libyaml-0.2.5. Fixes #15004.
[bdubbs] - Update to libinput-1.17.2 (xorg driver). Fixes #15005.
[bdubbs] - Update to LMDB-0.9.29. Fixes #15005.
[bdubbs] - Update to six-1.16.0 (Python Module). Fixes #15001.
[bdubbs] - Update to Pygments-2.9.0. Fixes #14991.
[bdubbs] - Update to umockdev-0.15.5. Fixes #14989.
May 8th, 2021
May 7th, 2021
[bdubbs] - Update to librsvg-2.50.5. Fixes #14970.
[bdubbs] - Update to php-8.0.5. Fixes #14958.
[bdubbs] - Update to gparted-1.3.0. Fixes #14988.
[bdubbs] - Update to libass-0.15.1. Fixes #14985.
[bdubbs] - Update to wayland-protocols-1.21. Fixes #14973.
[bdubbs] - Update to Net-DNS-1.31 (Perl Module). Fixes #14982.
[renodr] - Add the systemd-oomd group.
[bdubbs] - Update to at-spi2-core-2.40.1. Fixes #14972.
[bdubbs] - Update to fdk-aac-2.0.2. Fixes #14953.
[bdubbs] - Update to guile-3.0.6. Fixes #14948.
[bdubbs] - Update to hdparm-9.61. Fixes #14946.
[bdubbs] - Update to tcsh-6.22.04. Fixes #14945.
[bdubbs] - Update to graphviz-2.47.1. Fixes #14942.
[bdubbs] - Update to gedit-40.1. Fixes #14941.
[bdubbs] - Update to adwaita-icon-theme-40.1.1. Fixes #14935 (again).
[bdubbs] - Update to gtk+3-3.24.29. Fixes #14934.
[bdubbs] - Update to mesa-21.1.0. Fixes #14758.
[timtas] - Update to thunar-4.16.8. Fixes #15003.
May 6th, 2021
[renodr] - Update to exo-4.16.2. Fixes #14897.
[renodr] - Update to xfce4-settings-4.16.1. Fixes #14898.
[renodr] - Update to gnome-session-40.1.1. Fixes #14899.
[renodr] - Update to gnome-backgrounds-40.1. Fixes #14900.
[bdubbs] - Update to libdvdnav-6.1.1. Fixes #14939.
[bdubbs] - Update to libdvdread-6.1.2. Fixes #14940.
[bdubbs] - Update to libdvdcss-1.4.3. Fixes #14938.
[bdubbs] - Update to wireshark-3.4.5. Fixes #14929.
[bdubbs] - Update to glib-networking-2.68.1. Fixes #14931.
[bdubbs] - Update to libjpeg-turbo-2.1.0. Fixes #14310.
[ken] - Patch qtwebengine-20210401 for latest fixes (security update). Fixes #14999.
[bdubbs] - Update to adwaita-icon-theme-40.1. Fixes #14935.
[bdubbs] - Update to xf86-input-libinput-1.0.1 (Xorg Driver). Fixes #14933.
[bdubbs] - Update to docutils-0.17.1 (Python module). Fixes #14926.
[bdubbs] - Update to List-AllUtils-0.19 (Perl module). Fixes #14924.
[bdubbs] - Update to libtiff-4.3.0. Fixes #14922.
[bdubbs] - Update to jasper-2.0.32. Fixes #14921.
[renodr] - Update to cbindgen-0.19.0. Fixes #14885.
[renodr] - Update to postfix-3.6.0. Fixes #14892.
[renodr] - Update to gdk-pixbuf-2.42.6. Fixes #14893.
[renodr] - Update to file-roller-3.40.0. Fixes #14894.
[renodr] - Update to seahorse-40.0. Fixes #14895.
[renodr] - Update to ICU-69.1. Fixes #14884.
[renodr] - Fix building WebKitGTK+ with ICU-69.1. Patch by Xi Ruoyao.
[renodr] - Fix building Node.JS with ICU-69.1. Patch by Ken Moffat.
[timtas] - Upgrade to xfce4-panel-4.16.3. Fixes #15002.
May 5th, 2021
May 4th, 2021
[renodr] - Adapt the Dovecot Lua plugin to Lua-5.4. Fixes #14977.
[renodr] - Update to vala-0.52.3. Fixes #14879.
[renodr] - Update to libksba-1.5.1. Fixes #14874.
[renodr] - Update to pipewire-0.3.26. Fixes #14878.
[renodr] - Update to graphene-1.10.6. Fixes #14873.
[renodr] - Update to ruby-3.0.1 (Security Update). Fixes #14871.
[thomas] - Upgrade to xorgproto-2021.4. Fixes #14960.
[thomas] - Upgrade to harfbuzz-2.8.1. Fixes #14990.
[timtas] - Upgrade to exim-4.94.2. Fixes #14994.
May 3rd, 2021
[bdubbs] - Upgrade to libical-3.0.10. Fixes #14920.
[bdubbs] - Upgrade to boost_1_76_0. Fixes #14918.
[bdubbs] - Upgrade to gtk-vnc-1.2.0. Fixes #14908.
[bdubbs] - Upgrade to libhandy-1.2.2. Fixes #14906.
[bdubbs] - Upgrade to unrar-6.0.5. Fixes #14903.
[timtas] - Upgrade to openldap-2.5.4. Fixes #14959.
May 2nd, 2021
May 1st, 2021
[timtas] - Add a sed to cups-filters to allow building with openldap 2.5.4. Fixes #14978.
[renodr] - Update to opencv-4.5.2. Fixes #14855.
[renodr] - Update to bluez-5.58. Fixes #14856.
[renodr] - Update to decorator-5.0.7 (Python Module). Fixes #14857.
[renodr] - Update to stunnel-5.59. Fixes #14869.
[renodr] - Update to libportal-0.4. Fixes #14870.
[thomas] - Update to bind-9.16.15 (server and utils). Fixes #14951.
[thomas] - Update to cmake-3.20.2. Fixes #14957.
[thomas] - Update to libgcrypt-1.9.3. Fixes #14919.
April 30th, 2021
April 29th, 2021
April 28th, 2021
[renodr] - Fix the systemd patch to allow compilation with meson-0.57.2 and with Linux-API-Headers-5.11.14 and higher.
[ken] - Update to xorg-server-1.20.11 (security fix). Fixes #14905.
April 27th, 2021
April 26th, 2021
April 23rd, 2021
[ken] - Patch xindy to include upstream changes.
[ken] - Update to texlive-2021. Fixes #14846.
April 21th, 2021
[xry111] - Add workaround for cracklib to build Python 3 module.
[xry111] - Revert 7b66ed21, as the proposed fix in it is rejected by Python maintainers.
April 19th, 2021
[ken] - Update to firefox-78.10.0esr (security fixes) and JS-78.10.0.
April 17th, 2021
[pierre] - Fix a build error in evolution-data-server-3.40.0 with cmake-3.20.1.
April 15th, 2021
April 14th, 2021
April 13th, 2021
[timtas] - Upgrade to cifs-utils-6.13. Fixes #14904.
April 12th, 2021
[timtas] - Upgrade to glib-2.68.1. Fixes #14881.
April 11th, 2021
April 9th, 2021
[ken] - Update to a qtwebengine snapshot from 2021-04-01 (Security Update). Fixes #14863.
April 8th, 2021
[ken] - Update to node-v14.16.1 (Security Update). Fixes #14875.
[renodr] - Update to baobab-40.0. Part of #14801.
[renodr] - Update to eog-40.0. Part of #14801.
[renodr] - Update to evince-40.1. Part of #14801.
[renodr] - Update to gnome-calculator-40.0. Part of #14801.
[renodr] - Update to gnome-disk-utility-40.0. Part of #14801.
[renodr] - Update to gnome-maps-40.0. Part of #14801.
[renodr] - Update to gnome-screenshot-40.0. Part of #14801.
[renodr] - Update to gnome-system-monitor-40.0. Part of #14801.
[renodr] - Update to gnome-terminal-3.40.0. Part of #14801.
[renodr] - Update to gnome-weather-40.0. Part of #14801.
[renodr] - Update to gedit-40.0. Part of #14801.
[renodr] - Update to epiphany-40.0. Part of #14801.
[renodr] - Adapt Cheese to changes in vala-0.52. Fixes #14882.
[thomas] - Update to xf86-input-libinput-1.0.0. Fixes #14872.
[thomas] - Update to libva-2.11.0. Fixes #14860.
[thomas] - Update to libdrm-2.4.105. Fixes #14877.
[thomas] - Update to libxkbcommon-1.2.1. Fixes #14864.
[renodr] - Update to gnome-tweaks-40.0. Part of #14801.
[renodr] - Update to evolution-3.40.0. Part of #14801.
[renodr] - Update to yelp-40.0. Part of #14800.
[renodr] - Update to gnome-user-docs-40.0. Part of #14800.
[renodr] - Update to gdm-40.0. Part of #14800.
[renodr] - Update to gnome-shell-extensions-40.0. Part of #14800.
[renodr] - Update to gnome-shell-40.0. Part of #14800.
[renodr] - Update to mutter-40.0. Part of #14800.
[renodr] - Update to gnome-control-center-40.0. Part of #14800.
[renodr] - Update to gnome-settings-daemon-40.0. Part of #14800.
[renodr] - Update to gnome-keyring-40.0. Part of #14800.
[renodr] - Update to gnome-bluetooth-3.34.5. Part of #14800.
[renodr] - Update to nautilus-40.0. Part of #14800.
[renodr] - Update to gvfs-1.48.0. Part of #14800.
[renodr] - Update to dconf-editor-3.38.3. Part of #14800.
April 6th, 2021
[renodr] - Update to tracker3-miners-3.1.1. Part of #14799.
[renodr] - Update to tracker3-3.1.1. Part of #14799.
[renodr] - Update to evolution-data-server-3.40.0. Part of #14799.
[renodr] - Update to libgweather-40.0. Part of #14799.
[renodr] - Update to libpeas-1.30.0. Part of #14799.
[renodr] - Update to libgee-0.20.4. Part of #14799.
[renodr] - Update to gnome-desktop-40.0. Part of #14799.
[renodr] - Update to gjs-1.68.0. Part of #14799.
[renodr] - Update to vte-0.64.0. Fixes #14862.
[renodr] - Update to yelp-xsl-40.0. Part of #14799.
[renodr] - Update to gsettings-desktop-schemas-40.0. Part of #14799.
[renodr] - Update to gcr-3.40.0. Part of #14799.
[renodr] - Fix a security vulnerability in avahi. Fixes #14866.
[renodr] - Fix a security vulnerability in NetworkManager. Fixes #14868.
[renodr] - Fix a security vulnerability in p7zip. Fixes #14867.
April 5th, 2021
[pierre] - Remove a spurious file in doxygen that prevents building the documentation.
April 3rd, 2021
April 2nd, 2021
[renodr] - Added gtksourceview-5.0.0. Finishes #14798.
[renodr] - Added GTK-4.2.0. Part of #14798.
[renodr] - Update to tepl-6.00.0. Part of #14798.
[renodr] - Update to sysprof-3.40.1. Part of #14798.
[renodr] - Update to libdazzle-3.40.0. Part of #14798.
[renodr] - Update to gtk+-3.24.28. Part of #14798.
[renodr] - Update to gdk-pixbuf-2.42.4. Part of #14798.
[renodr] - Update to at-spi2-core-2.40.0. Part of #14798.
[renodr] - Update to glib-networking-2.68.0. Part of #14798.
[renodr] - Update to pygobject-3.40.1. Part of #14798.
[renodr] - Update to gobject-introspection-1.68.0. Part of #14798.
[renodr] - Update to vala-0.52.0. Part of #14798.
[renodr] - Update to glib-2.68.0. Part of #14798.
[ken] - Add a warning in xdg-utils about an unfixed security vulnerability.
[ken] - Patch libssh2-1.9.0 for a security vulnerability. Fixes #14853.
[ken] - Patch flac-1.3.3 for a security vulnerability. Fixes #14852.
[timtas] - Update to xscreensaver-6.00. Fixes #14851.
April 1st, 2021
[renodr] - Update to ghostscript-9.54.0. Fixes #14842.
[renodr] - Update to libXres-1.2.1 (Xorg Library). Fixes #14845.
[renodr] - Update to Net-DNS-1.30 (Perl Module). Fixes #14841.
[renodr] - Fix Hexchat to work with Python-3.8+ and fix a crash that occurs when Lua-5.4.3 is installed.
[renodr] - Update to Seamonkey-2.53.7 (Security Update). Fixes #14840.
[timtas] - Update to curl-7.76.0. Fixes #14844.
March 31st, 2021
March 30th, 2021
March 29th, 2021
[renodr] - Update to graphviz-2.47.0. Fixes #14832.
[renodr] - Update to glib-2.66.8 (Security Update). Fixes #14833.
[renodr] - Update to libgweather-3.38.2. Fixes #14834.
[renodr] - Update to sg3_utils-1.46. Fixes #14835.
[renodr] - Update to libXaw-1.0.14 (Xorg Library). Fixes #14828.
[renodr] - Update to phonon-backend-vlc-0.11.3. Fixes #14827.
[renodr] - Update to dbus-glib-0.112. Fixes #14829.
[renodr] - Update to fetchmail-6.4.18. Fixes #14831.
[renodr] - Update to python-dbusmock-0.23.0. Fixes #14818.
[renodr] - Update to emacs-27.2. Fixes #14822.
[renodr] - Update to cups-filters-1.28.8. Fixes #14823.
[renodr] - Update to xterm-367. Fixes #14825.
[renodr] - Update to pango-1.48.4. Fixes #14826.
March 28th, 2021
[xry111] - Update to samba-4.14.2. Fixes #14819.
[renodr] - Adapted the instructions for backgrounds in Fluxbox to be able to copy themes that are stored in directories.
[renodr] - Fix a syntax error that causes MariaDB to fail to build with CMake-3.20.
[renodr] - Update to webkitgtk-2.30.6 (Security Update). Fixes #14811.
[renodr] - Update to gnumeric-1.12.49. Fixes #14810.
[timtas] - Update to gegl-0.4.30. Fixes #14830.
[timtas] - Update to git-2.31.1. Fixes #14824.
March 27th, 2021
[renodr] - Update to cairo-1.17.4. Fixes #14802.
[renodr] - Update to Thunar-4.16.6. Fixes #14806.
[renodr] - Update to nettle-3.7.2 (Security Update). Fixes #14807.
[renodr] - Update to lxml-4.6.3 (Python Module). Includes a fix for a security vulnerability. Fixes #14808.
[renodr] - Update to valgrind-3.17.0. Fixes #14809.
[renodr] - Update to links-2.22. Fixes #14787.
[renodr] - Update to sqlite-3.35.3. Fixes #14788.
[renodr] - Update to NSS-3.63. Fixes #14790.
[renodr] - Update to jasper-2.0.27. Fixes #14792.
[renodr] - Update to pipewire-0.3.24. Fixes #14797.
March 26th, 2021
[ken] - Update to thunderbird-78.9.0 (security fixes). Fixes #14816.
[pierre] - Update to libinput-1.17.1. Fixes #14820.
[pierre] - Update to btrfs-progs-5.11.1. Fixes #14817.
[pierre] - Update to cmake-3.20.0. Fixes #14815.
[pierre] - Update to libgpg-error-1.42. Fixes #14813.
[pierre] - Update to libassuan-2.5.5. Fixes #14812.
[pierre] - Update to libvpx-1.10.0. Fixes #14741.
[timtas] - Update to bridge-utils-1.7.1. Fixes #14814.
[timtas] - Update to mpg123-1.26.5. Fixes #14821.
March 25th, 2021
March 23rd, 2021
[renodr] - Modify the qtwebengine patch to fix a build failure when building on a system with libxml2 that was built before ICU was installed.
[xry111] - Add packages and instructions for booting on UEFI based system. Fixes #5379.
[ken] - Update to firefox-78.9.0 and JS-78.9.0 (security fixes). Fixes #14804.
March 22nd, 2021
[ken] - Revise the Kernel Configuration section of QtWebEngine: User namespace works if PID namespace is enabled.
March 21st, 2021
March 20th, 2021
[ken] - Update to git-2.31.0. Fixes #14775.
March 18th, 2021
[ken] - Update to qtwebengine-5.15.3 from git (security fixes). Fixes #14729.
March 17th, 2021
[bdubbs] - Update to libcap-2.49. Fixes #14770.
[pierre] - Patch dconf-editor so that it builds with vala-0.50.4.
[renodr] - Update to xkbcomp-1.4.5 (Xorg Application). Fixes #14786.
[renodr] - Update to nspr-4.30. Fixes #14783.
[renodr] - Update to harfbuzz-2.8.0. Fixes #14784.
[timtas] - Update to icewm-2.2.1. Fixes #14720.
[timtas] - Update to openldap-2.4.58. Fixes #14785.
[timtas] - Update to sudo-1.9.6p1. Fixes #14771.
[renodr] - Update to cmake-3.19.7. Fixes #14778.
[renodr] - Update to gnome-online-accounts-3.38.1. Fixes #14779.
[renodr] - Update to mutter-3.38.4. Fixes #14781.
[renodr] - Update to gnome-shell-3.38.4. Fixes #14780.
[renodr] - Update to libgudev-236. Fixes #14782.
[renodr] - Update to goffice-0.10.49. Fixes #14772.
[renodr] - Update to pyatspi-2.38.1. Fixes #14769.
[renodr] - Update the gstreamer stack to gst*-1.18.4. Includes updates for five security vulnerabilities. Fixes #14776.
March 16th, 2021
[renodr] - Update to exo-4.16.1. Fixes #14759.
[renodr] - Update to libhandy-1.2.0. Fixes #14760.
[renodr] - Update to NetworkManager-1.30.2. Fixes #14761.
[renodr] - Update to gtk+-3.24.27. Fixes #14762.
[renodr] - Update to epiphany-3.38.3. Fixes #14763.
[renodr] - Update to dconf-0.40.0. Fixes #14764.
[renodr] - Update to xfsprogs-5.11.0. Fixes #14765.
[renodr] - Update to libgusb-0.3.6. Fixes #14766.
[renodr] - Update to sqlite-3.35.1. Fixes #14767.
[renodr] - Update to wireshark-3.4.4 (Security Update). Fixes #14751.
[renodr] - Update to pango-1.48.3. Fixes #14753.
[renodr] - Update to cryptsetup-2.3.5. Fixes #14754.
[renodr] - Update to gptfdisk-1.0.7. Fixes #14755.
[renodr] - Update to libxkbcommon-1.1.0. Fixes #14756.
[renodr] - Update to qpdf-10.3.1. Fixes #14757.
March 15th, 2021
March 14th, 2021
[ken] - Update to mutt-2.0.6. Fixes #14742.
[xry111] - Update to gnome-autoar-0.3.1. Fixes #14768.
[renodr] - Update to iso-codes-4.6.0. Fixes #14744.
[renodr] - Update to Thunderbird-78.8.1. Fixes #14745.
[renodr] - Update to git-2.30.2. Fixes #14746.
[renodr] - Update to mercurial-5.7.1. Fixes #14747.
[renodr] - Update to samba-4.14.0. Fixes #14748.
March 12th, 2021
March 11th, 2021
[renodr] - Make sure that the instructions for creating a symlink for /usr/lib/systemd in $KF5_PREFIX are still run when reinitializing /opt/kf5.
[renodr] - Update to php-8.0.3. Fixes #14732.
[renodr] - Update to libgdata-0.18.1. Fixes #14736.
[renodr] - Update to HTML-Parser-3.76. Fixes #14731.
[ken] - Prevent a (mostly harmless) segfault when a urxvt term (from rxvt-unicode) shuts down.
March 10th, 2021
March 8th, 2021
[timtas] - Update to fetchmail-6.4.17. Fixes #14743.
March 7th, 2021
March 5th, 2021
[timtas] - Update to dovecot-2.3.14. Fixes #14733.
March 4th, 2021
[renodr] - Update the systemd patch to allow systemd-rfkill to still function properly once LFS gets updated to Linux-5.11.
March 3rd, 2021
[renodr] - Update to URI-5.09 (Perl Module). Fixes #14723.
[renodr] - Update to OpenSSH-8.5p1 (and ssh-askpass-8.5p1). Includes a security fix for ssh-agent. Fixes #14725.
[renodr] - Update to gtksourceview-4.8.1. Includes a patch to prevent a race condition on some systems. Fixes #14724.
[renodr] - Update to poppler-21.03.0. Fixes #14722.
[renodr] - Update to babl-0.1.86. Fixes #14715.
[renodr] - Update to libgxps-0.3.2. Fixes #14714.
[renodr] - Update to qpdf-10.2.0. Fixes #14707.
[renodr] - Update to libqmi-1.28.2. Fixes #14721.
[renodr] - Update to ModemManager-1.16.2. Fixes #14705.
[bdubbs] - Update to bluez-5.56. Fixes #14698.
[bdubbs] - Update to nano-5.6.1. Fixes #14727.
[bdubbs] - Update to mousepad-0.5.3. Fixes #14718.
[bdubbs] - Update to liblinear-243. Fixes #14709.
[bdubbs] - Update to libwacom-1.9. Fixes #14703.
[bdubbs] - Update to libiodbc-3.52.14. Fixes #14702.
[bdubbs] - Update to gtkmm3-3.24.4. Fixes #14701.
[bdubbs] - Update to gtk+3 3.24.26. Fixes #14700.
[renodr] - Update to vala-0.50.4. Fixes #14719.
[renodr] - Update to cbindgen-0.18.0. Fixes #14717.
[renodr] - Update to mariadb-10.5.9. Fixes #14699.
[renodr] - Update to cmake-3.19.6. Fixes #14710.
March 2nd, 2021
[pierre] - Force usage of python3 for cracklib bindings.
[pierre] - Fix a header file in python, so that #include <python3.9/Python.h> works.
[thomas] - Fix a seccomp issue in OpenSSH on non-x86_64 platforms.
[ken] - Update to nss-3.62. Fixes #14684.
[bdubbs] - Update to xorgproto-2021.3. Fixes #14711.
[bdubbs] - Update to libinput-1.17.0 (Xorg Driver). Fixes #14706.
[bdubbs] - Update to IO-Socket-SSL-2.070 (Perl module). Fixes #14716.
[bdubbs] - Update to libqmi-1.28.0. Fixes #14697.
[bdubbs] - Update to ibus-1.5.24. Fixes #14693.
March 1st, 2021
[timtas] - Update to icewm-2.2.0. Fixes #14720.
[bdubbs] - Release of BLFS-10.1.
Last updated on
The linuxfromscratch.org server is hosting a number of mailing lists that are used for the development of the BLFS book. These lists include, among others, the main development and support lists.
For more information regarding which lists are available, how to subscribe to them, archive locations, etc., visit https://www.linuxfromscratch.org/mail.html.
Last updated on
The BLFS Project has created a Wiki for users to comment on pages and instructions at https://wiki.linuxfromscratch.org/blfs/wiki. Comments are welcome from all users.
The following are the rules for posting:
Users must register and log in to edit a page.
Suggestions to change the book should be made by creating a new ticket, not by making comments in the Wiki.
Questions with your specific installation problems should be made by subscribing and mailing to the BLFS Support Mailing List at mailto:blfs-support AT linuxfromscratch D0T org.
Discussions of build instructions should be made by subscribing and mailing to the BLFS Development List at mailto:blfs-dev AT linuxfromscratch D0T org.
Inappropriate material will be removed.
Last updated on
If you encounter a problem while using this book, and your problem is not listed in the FAQ (https://www.linuxfromscratch.org/faq), you will find that most of the people on Internet Relay Chat (IRC) and on the mailing lists are willing to help you. An overview of the LFS mailing lists can be found in Mailing lists. To assist us in diagnosing and solving your problem, include as much relevant information as possible in your request for help.
Before asking for help, you should review the following items:
Is the hardware support compiled into the kernel or
available as a module to the kernel? If it is a module,
is it configured properly in modprobe.conf and has it been loaded?
You should use lsmod as the
root user to see if
it's loaded. Check the sys.log file or run modprobe <driver>
to review any error message. If it loads properly, you
may need to add the modprobe command to
your boot scripts.
Are your permissions properly set, especially for
devices? LFS uses groups to make these settings easier,
but it also adds the step of adding users to groups to
allow access. A simple usermod -G audio <user>
may be all that's necessary for that user to have
access to the sound system. Any question that starts
out with “It works as root, but not as
...” requires a thorough review of
permissions prior to asking.
BLFS liberally uses /opt/.
The main objection to this centers around the need to
expand your environment variables for each package
placed there (e.g., PATH=$PATH:/opt/kde/bin). In most
cases, the package instructions will walk you through
the changes, but some will not. The section called
“Going Beyond
BLFS” is available to help you
check.
<package>
Apart from a brief explanation of the problem you're having, the essential things to include in your request are:
the version of the book you are using (being 11.0),
the package or section giving you problems,
the exact error message or symptom you are receiving,
whether you have deviated from the book or LFS at all,
if you are installing a BLFS package on a non-LFS system.
(Note that saying that you've deviated from the book doesn't mean that we won't help you. It'll just help us to see other possible causes of your problem.)
Expect guidance instead of specific instructions. If you are instructed to read something, please do so. It generally implies that the answer was way too obvious and that the question would not have been asked if a little research was done prior to asking. The volunteers in the mailing list prefer not to be used as an alternative to doing reasonable research on your end. In addition, the quality of your experience with BLFS is also greatly enhanced by this research, and the quality of volunteers is enhanced because they don't feel that their time has been abused, so they are far more likely to participate.
An excellent article on asking for help on the Internet in general has been written by Eric S. Raymond. It is available online at http://www.catb.org/~esr/faqs/smart-questions.html. Read and follow the hints in that document and you are much more likely to get a response to start with and also to get the help you actually need.
Last updated on
Many people have contributed both directly and indirectly to BLFS. This page lists all of those we can think of. We may well have left people out and if you feel this is the case, drop us a line. Many thanks to all of the LFS community for their assistance with this project.
Bruce Dubbs
Pierre Labastie
DJ Lucas
Ken Moffat
Douglas Reno
The list of contributors is far too large to provide detailed information about the contributions for each contributor. Over the years, the following individuals have provided significant inputs to the book:
Timothy Bauscher
Daniel Bauman
Jeff Bauman
Andy Benton
Wayne Blaszczyk
Paul Campbell
Nathan Coulson
Jeroen Coumans
Guy Dalziel
Robert Daniels
Richard Downing
Manuel Canales Esparcia
Jim Gifford
Manfred Glombowski
Ag Hatzimanikas
Mark Hymers
James Iwanek
David Jensen
Jeremy Jones
Seth Klein
Alex Kloss
Eric Konopka
Larry Lawrence
Chris Lynn
Andrew McMurry
Randy McMurchy
Denis Mugnier
Billy O'Connor
Fernando de Oliveira
Alexander Patrakov
Olivier Peres
Andreas Pedersen
Henning Rohde
Matt Rogers
James Robertson
Henning Rohde
Chris Staub
Jesse Tie-Ten-Quee
Ragnar Thomsen
Thomas Trepl
Tushar Teredesai
Jeremy Utley
Zack Winkles
Christian Wurst
Igor Živković
Fernando Arbeiza
Miguel Bazdresch
Gerard Beekmans
Oliver Brakmann
Jeremy Byron
Ian Chilton
David Ciecierski
Jim Harris
Lee Harris
Marc Heerdink
Steffen Knollmann
Eric Konopka
Scot McPherson
Ted Riley
Last updated on
Please direct your emails to one of the BLFS mailing lists. See Mailing lists for more information on the available mailing lists.
Last updated on
This chapter is used to explain some of the policies used throughout the book, to introduce important concepts and to explain some issues you may see with some of the included packages.
Those people who have built an LFS system may be aware of the general principles of downloading and unpacking software. Some of that information is repeated here for those new to building their own software.
Each set of installation instructions contains a URL from which you can download the package. The patches; however, are stored on the LFS servers and are available via HTTP. These are referenced as needed in the installation instructions.
While you can keep the source files anywhere you like, we assume that you have unpacked the package and changed into the directory created by the unpacking process (the 'build' directory). We also assume you have uncompressed any required patches and they are in the directory immediately above the 'build' directory.
We can not emphasize strongly enough that you should start from
a clean source tree each
time. This means that if you have had an error during
configuration or compilation, it's usually best to delete the
source tree and re-unpack it before trying again. This obviously
doesn't apply if you're an advanced user used to hacking
Makefiles and C code, but if in
doubt, start from a clean tree.
The golden rule of Unix System Administration is to use your
superpowers only when necessary. Hence, BLFS recommends that
you build software as an unprivileged user and only become
the root user when installing
the software. This philosophy is followed in all the packages
in this book. Unless otherwise specified, all instructions
should be executed as an unprivileged user. The book will
advise you on instructions that need root privileges.
If a file is in .tar format and
compressed, it is unpacked by running one of the following
commands:
tar -xvf filename.tar.gz tar -xvf filename.tgz tar -xvf filename.tar.Z tar -xvf filename.tar.bz2
You may omit using the v
parameter in the commands shown above and below if you wish
to suppress the verbose listing of all the files in the
archive as they are extracted. This can help speed up the
extraction as well as make any errors produced during the
extraction more obvious to you.
You can also use a slightly different method:
bzcat filename.tar.bz2 | tar -xv
Finally, you sometimes need to be able to unpack patches
which are generally not in .tar
format. The best way to do this is to copy the patch file to
the parent of the 'build' directory and then run one of the
following commands depending on whether the file is a
.gz or .bz2 file:
gunzip -v patchname.gz bunzip2 -v patchname.bz2
Generally, to verify that the downloaded file is complete,
many package maintainers also distribute md5sums of the
files. To verify the md5sum of the downloaded files, download
both the file and the corresponding md5sum file to the same
directory (preferably from different on-line locations), and
(assuming file.md5sum is the
md5sum file downloaded) run the following command:
md5sum -c file.md5sum
If there are any errors, they will be reported. Note that the
BLFS book includes md5sums for all the source files also. To
use the BLFS supplied md5sums, you can create a file.md5sum (place the md5sum data and the
exact name of the downloaded file on the same line of a file,
separated by white space) and run the command shown above.
Alternately, simply run the command shown below and compare
the output to the md5sum data shown in the BLFS book.
md5sum <name_of_downloaded_file>
MD5 is not cryptographically secure, so the md5sums are only provided for detecting random errors or truncations introduced during network transfer. There is no “100%” secure way to make sure the genuity of the source files. Assuming the upstream is managing their website correctly (the private key is not leaked and the domain is not hijacked), and the trust anchors have been set up correctly using make-ca-1.7 on the BLFS system, we can reasonably trust download URLs to the upstream official website with https protocol. Note that BLFS book itself is published on a website with https, so you should already have some confidence in https protocol or you wouldn't trust the book content.
If the package is downloaded from an unofficial location (for example a local mirror), checksums generated by cryptographically secure digest algorithms (for example SHA256) can be used to verify the genuity of the package. Download the checksum file from the upstream official website (or somewhere you can trust) and compare the checksum of the package from unoffical location with it. For example, SHA256 checksum can be checked with the command:
If the checksum and the package are downloaded from the same untrusted location, you won't gain security enhancement by verifying the package with the checksum. The attacker can fake the checksum as well as compromising the package itself.
sha256sum -c file.sha256sum
If GnuPG-2.2.29 is installed, you can also verify the genuity of the package with a GPG signature. Import the upstream GPG public key with:
gpg --recv-key keyID
keyID should be
replaced with the key ID from somewhere you can trust (for example,
copy it from the upstream official website using https). Now
you can verify the signature with:
gpg --recv-keyfile.sigfile
The advantage of GnuPG signature is, once you imported a public key which can be trusted, you can download both the package and its signature from the same unofficial location and verify them with the public key. So you won't need to connect to the official upstream website to retrieve a checksum for each new release. You only need to update the public key if it's expired or revoked.
For larger packages, it is convenient to create log files
instead of staring at the screen hoping to catch a particular
error or warning. Log files are also useful for debugging and
keeping records. The following command allows you to create
an installation log. Replace <command> with the
command you intend to execute.
( <command> 2>&1 | tee compile.log && exit $PIPESTATUS )
2>&1 redirects error
messages to the same location as standard output. The
tee command
allows viewing of the output while logging the results to a
file. The parentheses around the command run the entire
command in a subshell and finally the exit $PIPESTATUS command
ensures the result of the <command> is returned
as the result and not the result of the tee command.
For many modern systems with multiple processors (or cores) the compilation time for a package can be reduced by performing a "parallel make" by either setting an environment variable or telling the make program how many processors are available. For instance, a Core2Duo can support two simultaneous processes with:
export MAKEFLAGS='-j2'
or just building with:
make -j2
Generally the number of processes should not exceed the
number of cores supported by the CPU. To list the processors
on your system, issue: grep
processor /proc/cpuinfo.
In some cases, using multiple processors may result in a 'race' condition where the success of the build depends on the order of the commands run by the make program. For instance, if an executable needs File A and File B, attempting to link the program before one of the dependent components is available will result in a failure. This condition usually arises because the upstream developer has not properly designated all the prerequisites needed to accomplish a step in the Makefile.
If this occurs, the best way to proceed is to drop back to a single processor build. Adding '-j1' to a make command will override the similar setting in the MAKEFLAGS environment variable.
When running the package tests or the install portion of the package build process, we do not recommend using an option greater than '-j1' unless specified otherwise. The installation procedures or checks have not been validated using parallel procedures and may fail with issues that are difficult to debug.
There are times when automating the building of a package can
come in handy. Everyone has their own reasons for wanting to
automate building, and everyone goes about it in their own
way. Creating Makefiles,
Bash scripts, Perl scripts or simply a list of
commands used to cut and paste are just some of the methods
you can use to automate building BLFS packages. Detailing how
and providing examples of the many ways you can automate the
building of packages is beyond the scope of this section.
This section will expose you to using file redirection and
the yes command
to help provide ideas on how to automate your builds.
You will find times throughout your BLFS journey when you will come across a package that has a command prompting you for information. This information might be configuration details, a directory path, or a response to a license agreement. This can present a challenge to automate the building of that package. Occasionally, you will be prompted for different information in a series of questions. One method to automate this type of scenario requires putting the desired responses in a file and using redirection so that the program uses the data in the file as the answers to the questions.
Building the CUPS package is a good example of how redirecting a file as input to prompts can help you automate the build. If you run the test suite, you are asked to respond to a series of questions regarding the type of test to run and if you have any auxiliary programs the test can use. You can create a file with your responses, one response per line, and use a command similar to the one shown below to automate running the test suite:
make check < ../cups-1.1.23-testsuite_parms
This effectively makes the test suite use the responses in the file as the input to the questions. Occasionally you may end up doing a bit of trial and error determining the exact format of your input file for some things, but once figured out and documented you can use this to automate building the package.
Sometimes you will only need to provide one response, or provide the same response to many prompts. For these instances, the yes command works really well. The yes command can be used to provide a response (the same one) to one or more instances of questions. It can be used to simulate pressing just the Enter key, entering the Y key or entering a string of text. Perhaps the easiest way to show its use is in an example.
First, create a short Bash script by entering the following commands:
cat > blfs-yes-test1 << "EOF"
#!/bin/bash
echo -n -e "\n\nPlease type something (or nothing) and press Enter ---> "
read A_STRING
if test "$A_STRING" = ""; then A_STRING="Just the Enter key was pressed"
else A_STRING="You entered '$A_STRING'"
fi
echo -e "\n\n$A_STRING\n\n"
EOF
chmod 755 blfs-yes-test1
Now run the script by issuing ./blfs-yes-test1 from the command line. It will wait for a response, which can be anything (or nothing) followed by the Enter key. After entering something, the result will be echoed to the screen. Now use the yes command to automate the entering of a response:
yes | ./blfs-yes-test1
Notice that piping yes by itself to the script results in y being passed to the script. Now try it with a string of text:
yes 'This is some text' | ./blfs-yes-test1
The exact string was used as the response to the script. Finally, try it using an empty (null) string:
yes '' | ./blfs-yes-test1
Notice this results in passing just the press of the Enter key to the script. This is useful for times when the default answer to the prompt is sufficient. This syntax is used in the Net-tools instructions to accept all the defaults to the many prompts during the configuration step. You may now remove the test script, if desired.
In order to automate the building of some packages, especially those that require you to read a license agreement one page at a time, requires using a method that avoids having to press a key to display each page. Redirecting the output to a file can be used in these instances to assist with the automation. The previous section on this page touched on creating log files of the build output. The redirection method shown there used the tee command to redirect output to a file while also displaying the output to the screen. Here, the output will only be sent to a file.
Again, the easiest way to demonstrate the technique is to show an example. First, issue the command:
ls -l /usr/bin | more
Of course, you'll be required to view the output one page at
a time because the more filter was used. Now
try the same command, but this time redirect the output to a
file. The special file /dev/null can be used instead of the
filename shown, but you will have no log file to examine:
ls -l /usr/bin | more > redirect_test.log 2>&1
Notice that this time the command immediately returned to the shell prompt without having to page through the output. You may now remove the log file.
The last example will use the yes command in combination with output redirection to bypass having to page through the output and then provide a y to a prompt. This technique could be used in instances when otherwise you would have to page through the output of a file (such as a license agreement) and then answer the question of “do you accept the above?”. For this example, another short Bash script is required:
cat > blfs-yes-test2 << "EOF"
#!/bin/bash
ls -l /usr/bin | more
echo -n -e "\n\nDid you enjoy reading this? (y,n) "
read A_STRING
if test "$A_STRING" = "y"; then A_STRING="You entered the 'y' key"
else A_STRING="You did NOT enter the 'y' key"
fi
echo -e "\n\n$A_STRING\n\n"
EOF
chmod 755 blfs-yes-test2
This script can be used to simulate a program that requires you to read a license agreement, then respond appropriately to accept the agreement before the program will install anything. First, run the script without any automation techniques by issuing ./blfs-yes-test2.
Now issue the following command which uses two automation techniques, making it suitable for use in an automated build script:
yes | ./blfs-yes-test2 > blfs-yes-test2.log 2>&1
If desired, issue tail blfs-yes-test2.log to see the end of the paged output, and confirmation that y was passed through to the script. Once satisfied that it works as it should, you may remove the script and log file.
Finally, keep in mind that there are many ways to automate and/or script the build commands. There is not a single “correct” way to do it. Your imagination is the only limit.
For each package described, BLFS lists the known dependencies. These are listed under several headings, whose meaning is as follows:
Required means that the target package cannot be correctly built without the dependency having first been installed.
Recommended means that BLFS strongly suggests this package is installed first for a clean and trouble-free build, that won't have issues either during the build process, or at run-time. The instructions in the book assume these packages are installed. Some changes or workarounds may be required if these packages are not installed.
Optional means that this package might be installed for added functionality. Often BLFS will describe the dependency to explain the added functionality that will result.
On occasion you may run into a situation in the book when a package will not build or work properly. Though the Editors attempt to ensure that every package in the book builds and works properly, sometimes a package has been overlooked or was not tested with this particular version of BLFS.
If you discover that a package will not build or work properly, you should see if there is a more current version of the package. Typically this means you go to the maintainer's web site and download the most current tarball and attempt to build the package. If you cannot determine the maintainer's web site by looking at the download URLs, use Google and query the package's name. For example, in the Google search bar type: 'package_name download' (omit the quotes) or something similar. Sometimes typing: 'package_name home page' will result in you finding the maintainer's web site.
If you did not strip programs and libraries in LFS, the following will probably make your system unusable. To avoid that, run the instructions at ../../../../lfs/view/11.0/chapter08/strippingagain.html instead. After the critical files are stripped using those instructions, the instructions below can be run any time new packages are installed.
In LFS, stripping of debugging symbols was discussed a couple of times. When building BLFS packages, there are generally no special instructions that discuss stripping again. It is probably not a good idea to strip an executable or a library while it is in use, so exiting any windowing environment is a good idea. Then you can do:
find /usr/{bin,lib,sbin} \
-type f \( -name \*.so* -a ! -name \*dbg \) \
-exec strip --strip-unneeded {} \;
If you install programs in other directories such as
/opt or /usr/local, you may want to strip the files
there too.
For more information on stripping, see http://www.technovelty.org/linux/stripping-shared-libraries.html.
There are now three different build systems in common use for converting C or C++ source code into compiled programs or libraries and their details (particularly, finding out about available options and their default values) differ. It may be easiest to understand the issues caused by some choices (typically slow execution or unexpected use of, or omission of, optimizatons) by starting with the CFLAGS and CXXFLAGS environment variables. There are also some programs which use rust.
Most LFS and BLFS builders are probably aware of the basics of CFLAGS and CXXFLAGS for altering how a program is compiled. Typically, some form of optimization is used by upstream developers (-O2 or -O3), sometimes with the creation of debug symbols (-g), as defaults.
If there are contradictory flags (e.g. multiple different -O values), the last value will be used. Sometimes this means that flags specified in environment variables will be picked up before values hardcoded in the Makefile, and therefore ignored. For example, where a user specifies '-O2' and that is followed by '-O3' the build will use '-O3'.
There are various other things which can be passed in CFLAGS or CXXFLAGS, such as forcing compilation for a specific microarchitecture (e.g. -march=amdfam10, -march=native) or specifying a specific standard for C or C++ (-std=c++17 for example). But one thing which has now come to light is that programmers might include debug assertions in their code, expecting them to be disabled in releases by using -DNDEBUG. Specifically, if Mesa-21.2.1 is built with these assertions enabled, some activities such as loading levels of games can take extremely long times, even on high-class video cards.
This combination is often described as 'CMMI' (configure, make, make install) and is used here to also cover the few packages which have a configure script that is not generated by autotools.
Sometimes running ./configure --help will produce useful options about switches which might be used. At other times, after looking at the output from configure you may need to look at the details of the script to find out what it was actually searching for.
Many configure scripts will pick up any CFLAGS or CXXFLAGS from the environment, but CMMI packages vary about how these will be mixed with any flags which would otherwise be used (variously: ignored, used to replace the programmer's suggestion, used before the programmer's suggestion, or used after the programmer's suggestion).
In most CMMI packages, running 'make' will list each command and run it, interspersed with any warnings. But some packages try to be 'silent' and only show which file they are compiling or linking instead of showing the command line. If you need to inspect the command, either because of an error, or just to see what options and flags are being used, adding 'V=1' to the make invocation may help.
CMake works in a very different way, and it has two backends which can be used on BLFS: 'make' and 'ninja'. The default backend is make, but ninja can be faster on large packages with multiple processors. To use ninja, specify '-G Ninja' in the cmake command. However, there are some packages which create fatal errors in their ninja files but build successfully using the default of Unix Makefiles.
The hardest part of using CMake is knowing what options you might wish to specify. The only way to get a list of what the package knows about is to run cmake -LAH and look at the output for that default configuration.
Perhaps the most-important thing about CMake is that it has a variety of CMAKE_BUILD_TYPE values, and these affect the flags. The default is that this is not set and no flags are generated. Any CFLAGS or CXXFLAGS in the environment will be used. If the programmer has coded any debug assertions, those will be enabled unless -DNDEBUG is used. The following CMAKE_BUILD_TYPE values will generate the flags shown, and these will come after any flags in the environment and therefore take precedence.
Debug : '-g'
Release : '-O3 -DNDEBUG'
RelWithDebInfo : '-O2 -g -DNDEBUG'
MinSizeRel : '-Os -DNDEBUG'
CMake tries to produce quiet builds. To see the details of the commands which are being run, use 'make VERBOSE=1' or 'ninja -v'.
Meson has some similarities to CMake, but many differences.
To get details of the defines that you may wish to change you
can look at meson_options.txt
which is usually in the top-level directory.
If you have already configured the package by running meson and now wish to change one or more settings, you can either remove the build directory, recreate it, and use the altered options, or within the build directory run meson configure, e.g. to set an option:
meson configure -D<some_option>=true
If you do that, the file meson-private/cmd_line.txt will show the
last commands which
were used.
Meson provides the following buildtype values, and the flags they enable come after any flags supplied in the environment and therefore take precedence.
plain : no added flags. This is for distributors to supply their own CLFAGS, CXXFLAGS and LDFLAGS. There is no obvious reason to use this in BLFS.
debug : '-g' - this is the default if nothing is
specified in either meson.build or the command line.
However it results large and slow binaries, so we
should override it in BLFS.
debugoptimized : '-O2 -g' : this is the default
specified in meson.build
of some packages.
release : '-O3 -DNDEBUG' (but occasionally a package will force -O2 here)
Although the 'release' buildtype is described as enabling -DNDEBUG, and all CMake Release builds pass that, it has so far only been observed (in verbose builds) for Mesa-21.2.1. That suggests that it might only be used when there are debug assertions present.
The -DNDEBUG flag can also be provided by passing -Db_ndebug=true.
To see the details of the commands which are being run in a package using meson, use 'ninja -v'.
Most released rustc programs are provided as crates (source
tarballs) which will query a server to check current versions
of dependencies and then download them as necessary. These
packages are built using cargo
--release. In theory, you can manipulate the
RUSTFLAGS to change the optimize-level (default is 3, like
-O3, e.g. -Copt-level=3) or to
force it to build for the machine it is being compiled on,
using -Ctarget-cpu=native but in
practice this seems to make no significant difference.
If you find an interesting rustc program which is only
provided as unpackaged source, you should at least specify
RUSTFLAGS=-Copt-level=2
otherwise it will do an unoptimized compile with debug info
and run much slower.
The rust developers seem to assume that everyone will compile
on a machine dedicated to producing builds, so by default all
CPUs are used. This can often be worked around, either by
exporting CARGO_BUILD_JOBS=<N> or passing --jobs
<N> to cargo. For compiling rustc itself, specifying
--jobs <N> on invocations of x.py (together with the
CARGO_BUILD_JOBS environment
variable, which looks like a "belt and braces" approach but
seems to be necessary) mostly works. The exception is running
the tests when building rustc, some of them will nevertheless
use all online CPUs, at least as of rustc-1.42.0.
Many people will prefer to optimize compiles as they see fit, by providing CFLAGS or CXXFLAGS. For an introduction to the options available with gcc and g++ see https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html and https://gcc.gnu.org/onlinedocs/gcc/Instrumentation-Options.html and info gcc.
Some packages default to '-O2 -g', others to '-O3 -g', and if CFLAGS or CXXFLAGS are supplied they might be added to the package's defaults, replace the package's defaults, or even be ignored. There are details on some desktop packages which were mostly current in April 2019 at https://www.linuxfromscratch.org/~ken/tuning/ - in particular, README.txt, tuning-1-packages-and-notes.txt, and tuning-notes-2B.txt. The particular thing to remember is that if you want to try some of the more interesting flags you may need to force verbose builds to confirm what is being used.
Clearly, if you are optimizing your own program you can spend time to profile it and perhaps recode some of it if it is too slow. But for building a whole system that approach is impractical. In general, -O3 usually produces faster programs than -O2. Specifying -march=native is also beneficial, but means that you cannot move the binaries to an incompatible machine - this can also apply to newer machines, not just to older machines. For example programs compiled for 'amdfam10' run on old Phenoms, Kaveris, and Ryzens : but programs compiled for a Kaveri will not run on a Ryzen because certain op-codes are not present. Similarly, if you build for a Haswell not everything will run on a SandyBridge.
There are also various other options which some people claim are beneficial. At worst, you get to recompile and test, and then discover that in your usage the options do not provide a benefit.
If building Perl or Python modules, or Qt packages which use qmake, in general the CFLAGS and CXXFLAGS used are those which were used by those 'parent' packages.
Even on desktop systems, there are still a lot of exploitable vulnerabilities. For many of these, the attack comes via javascript in a browser. Often, a series of vulnerabilities are used to gain access to data (or sometimes to pwn, i.e. own, the machine and install rootkits). Most commercial distros will apply various hardening measures.
For hardening options which are reasonably cheap, there is some discussion in the 'tuning' link above (occasionally, one or more of these options might be inappropriate for a package). These options are -D_FORTIFY_SOURCE=2, -fstack-protector=strong, and (for C++) -D_GLIBCXX_ASSERTIONS. On modern machines these should only have a little impact on how fast things run, and often they will not be noticeable.
In the past, there was Hardened LFS where gcc (a much older version) was forced to use hardening (with options to turn some of it off on a per-package basis. What is being covered here is different - first you have to make sure that the package is indeed using your added flags and not over-riding them.
The main distros use much more, such as RELRO (Relocation Read Only) and perhaps -fstack-clash-protection. You may also encounter the so-called 'userspace retpoline' (-mindirect-branch=thunk etc.) which is the equivalent of the spectre mitigations applied to the linux kernel in late 2018). The kernel mitigations caused a lot of complaints about lost performance, if you have a production server you might wish to consider testing that, along with the other available options, to see if performance is still sufficient.
Whilst gcc has many hardening options, clang/LLVM's strengths lie elsewhere. Some options which gcc provides are said to be less effective in clang/LLVM.
Last updated on
Should I install XXX in /usr or /usr/local?
This is a question without an obvious answer for an LFS based system.
In traditional Unix systems, /usr
usually contains files that come with the system distribution,
and the /usr/local tree is free
for the local administrator to manage. The only really hard and
fast rule is that Unix distributions should not touch
/usr/local, except perhaps to
create the basic directories within it.
With Linux distributions like Red Hat, Debian, etc., a possible
rule is that /usr is managed by
the distribution's package system and /usr/local is not. This way the package
manager's database knows about every file within /usr.
LFS users build their own system and so deciding where the
system ends and local files begin is not straightforward. So
the choice should be made in order to make things easier to
administer. There are several reasons for dividing files
between /usr and /usr/local.
On a network of several machines all running LFS, or
mixed LFS and other Linux distributions, /usr/local could be used to hold
packages that are common between all the computers in the
network. It can be NFS mounted or mirrored from a single
server. Here local indicates local to the site.
On a network of several computers all running an
identical LFS system, /usr/local could hold packages that are
different between the machines. In this case local refers
to the individual computers.
Even on a single computer, /usr/local can be useful if you have
several distributions installed simultaneously, and want
a place to put packages that will be the same on all of
them.
Or you might regularly rebuild your LFS, but want a place to put files that you don't want to rebuild each time. This way you can wipe the LFS file system and start from a clean partition every time without losing everything.
Some people ask why not use your own directory tree, e.g.,
/usr/site, rather than
/usr/local?
There is nothing stopping you, many sites do make their own
trees, however it makes installing new software more difficult.
Automatic installers often look for dependencies in
/usr and /usr/local, and if the file it is looking for
is in /usr/site instead, the
installer will probably fail unless you specifically tell it
where to look.
What is the BLFS position on this?
All of the BLFS instructions install programs in /usr with optional instructions to install
into /opt for some specific
packages.
Last updated on
As you follow the various sections in the book, you will observe that the book occasionally includes patches that are required for a successful and secure installation of the packages. The general policy of the book is to include patches that fall in one of the following criteria:
Fixes a compilation problem.
Fixes a security problem.
Fixes a broken functionality.
In short, the book only includes patches that are either required or recommended. There is a Patches subproject which hosts various patches (including the patches referenced in the books) to enable you to configure your LFS the way you like it.
Last updated on
The BLFS Systemd Units package contains the systemd unit files that are used throughout the book.
Package Information
The BLFS Systemd Units package will be used throughout the BLFS
book for systemd unit files. Each systemd unit has a separate
install target. It is recommended that you keep the package
source directory around until completion of your BLFS system.
When a systemd unit is requested from BLFS Systemd Units,
simply change to the directory, and as the root user, execute the given make install-<systemd-unit>
command. This command installs the systemd unit to its proper
location (along with any auxiliary configuration scripts) and
also enables it by default.
It is advisable to peruse each systemd unit before installation to determine whether the installed files meet your needs.
Last updated on
In LFS we installed a package, libtool, that is used by many packages to build on a variety of Unix platforms. This includes platforms such as AIX, Solaris, IRIX, HP-UX, and Cygwin as well as Linux. The origins of this tool are quite dated. It was intended to manage libraries on systems with less advanced capabilities than a modern Linux system.
On a Linux system, libtool specific files are generally unneeded. Normally libraries are specified in the build process during the link phase. Since a linux system uses the Executable and Linkable Format (ELF) for executables and libraries, information needed to complete the task is embedded in the files. At run time the program loader can query the appropriate files and properly load and execute the program.
The problem is that libtool usually creates one or more text files for package libraries called libtool archives. These small files have a ".la" extention and contain information that is similar to that embedded in the libraries. When building a package that uses libtool, the process automatically looks for these files. If a package is updated and no longer uses the .la file, then the build process can break.
The solution is to remove the .la files. However there is a catch. Some packages, such as ImageMagick-7.1.0-4, use a libtool function, lt_dlopen, to load libraries as needed during execution and resolve their dependencies at run time. In this case, the .la files should remain.
The script below, removes all unneeded .la files and saves them in a directory, /var/local/la-files by default, not in the normal library path. It also searches all pkg-config files (.pc) for embedded references to .la files and fixes them to be conventional library references needed when an application or library is built. It can be run as needed to clean up the directories that may be causing problems.
cat > /usr/sbin/remove-la-files.sh << "EOF"
#!/bin/bash
# /usr/sbin/remove-la-files.sh
# Written for Beyond Linux From Scratch
# by Bruce Dubbs <[email protected]>
# Make sure we are running with root privs
if test "${EUID}" -ne 0; then
echo "Error: $(basename ${0}) must be run as the root user! Exiting..."
exit 1
fi
# Make sure PKG_CONFIG_PATH is set if discarded by sudo
source /etc/profile
OLD_LA_DIR=/var/local/la-files
mkdir -p $OLD_LA_DIR
# Only search directories in /opt, but not symlinks to directories
OPTDIRS=$(find /opt -mindepth 1 -maxdepth 1 -type d)
# Move any found .la files to a directory out of the way
find /usr/lib $OPTDIRS -name "*.la" ! -path "/usr/lib/ImageMagick*" \
-exec mv -fv {} $OLD_LA_DIR \;
###############
# Fix any .pc files that may have .la references
STD_PC_PATH='/usr/lib/pkgconfig
/usr/share/pkgconfig
/usr/local/lib/pkgconfig
/usr/local/share/pkgconfig'
# For each directory that can have .pc files
for d in $(echo $PKG_CONFIG_PATH | tr : ' ') $STD_PC_PATH; do
# For each pc file
for pc in $d/*.pc ; do
if [ $pc == "$d/*.pc" ]; then continue; fi
# Check each word in a line with a .la reference
for word in $(grep '\.la' $pc); do
if $(echo $word | grep -q '.la$' ); then
mkdir -p $d/la-backup
cp -fv $pc $d/la-backup
basename=$(basename $word )
libref=$(echo $basename|sed -e 's/^lib/-l/' -e 's/\.la$//')
# Fix the .pc file
sed -i "s:$word:$libref:" $pc
fi
done
done
done
EOF
chmod +x /usr/sbin/remove-la-files.sh
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/la-files
Last updated on
The original libraries were simply an archive of routines from which the required routines were extracted and linked into the executable program. These are described as static libraries (libfoo.a). On some old operating systems they are the only type available.
On almost all Linux platforms there are also shared libraries (libfoo.so) - one copy of the library is loaded into virtual memory, and shared by all the programs which call any of its functions. This is space efficient.
In the past, essential programs such as a shell were often
linked statically so that some form of minimal recovery
system would exist even if shared libraries, such as libc.so,
became damaged (e.g. moved to lost+found after fsck following an unclean
shutdown). Nowadays, most people use an alternative system
install or a Live CD if they have to recover. Journaling
filesystems also reduce the likelihood of this sort of
problem.
Developers, at least while they are developing, often prefer to use static versions of the libraries which their code links to.
Within the book, there are various places where configure switches such as --disable-static are employed, and other places where the possibility of using system versions of libraries instead of the versions included within another package is discussed. The main reason for this is to simplify updates of libraries.
If a package is linked to a dynamic library, updating to a newer library version is automatic once the newer library is installed and the program is (re)started (provided the library major version is unchanged, e.g. going from libfoo.so.2.0 to libfoo.so.2.1. Going to libfoo.so.3 will require recompilation - ldd can be used to find which programs use the old version). If a program is linked to a static library, the program always has to be recompiled. If you know which programs are linked to a particular static library, this is merely an annoyance. But usually you will not know which programs to recompile.
Most libraries are shared, but if you do something unusual,
such as moving a shared library to /lib accidentally breaking the .so symlink in /usr/lib while keeping the static library
in /lib, the static library
will be silently linked into the programs which need it.
One way to identify when a static library is used, is to deal
with it at the end of the installation of every package.
Write a script to find all the static libraries in
/usr/lib or wherever you are
installing to, and either move them to another directory so
that they are no longer found by the linker, or rename them
so that libfoo.a becomes e.g. libfoo.a.hidden. The static
library can then be temporarily restored if it is ever
needed, and the package needing it can be identified. You may
choose to exclude some of the static libraries from glibc if
you do this (libc_nonshared.a, libg.a,
libieee.a, libm.a, libpthread_nonshared.a, librpcsvc.a,
libsupc++.a) to simplify compilation.
If you use this approach, you may discover that more packages than you were expecting use a static library. That was the case with nettle-2.4 in its default static-only configuration: It was required by GnuTLS-3.0.19, but also linked into package(s) which used GnuTLS, such as glib-networking-2.32.3.
Many packages put some of their common functions into a static library which is only used by the programs within the package and, crucially, the library is not installed as a standalone library. These internal libraries are not a problem - if the package has to be rebuilt to fix a bug or vulnerability, nothing else is linked to them.
When BLFS mentions system libraries, it means shared versions of libraries. Some packages such as Firefox-91.0.1 and ghostscript-9.54.0 include many other libraries. When they link to them, they link statically so this also makes the programs bigger. The version they ship is often older than the version used in the system, so it may contain bugs - sometimes developers go to the trouble of fixing bugs in their included libraries, other times they do not.
Sometimes, deciding to use system libraries is an easy decision. Other times it may require you to alter the system version (e.g. for libpng-1.6.37 if used for Firefox-91.0.1). Occasionally, a package ships an old library and can no longer link to the current version, but can link to an older version. In this case, BLFS will usually just use the shipped version. Sometimes the included library is no longer developed separately, or its upstream is now the same as the package's upstream and you have no other packages which will use it. In those cases, you might decide to use the included static library even if you usually prefer to use system libraries.
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/libraries
Last updated on
This page contains information about locale related problems and issues. In the following paragraphs you'll find a generic overview of things that can come up when configuring your system for various locales. Many (but not all) existing locale related problems can be classified and fall under one of the headings below. The severity ratings below use the following criteria:
Critical: The program doesn't perform its main function. The fix would be very intrusive, it's better to search for a replacement.
High: Part of the functionality that the program provides is not usable. If that functionality is required, it's better to search for a replacement.
Low: The program works in all typical use cases, but lacks some functionality normally provided by its equivalents.
If there is a known workaround for a specific package, it will appear on that package's page. For the most recent information about locale related issues for individual packages, check the User Notes in the BLFS Wiki.
Severity: Critical
Some programs require the user to specify the character
encoding for their input or output data and present only a
limited choice of encodings. This is the case for the
-X option in Enscript-1.6.6,
the -input-charset option in
unpatched Cdrtools-3.02a09, and the character
sets offered for display in the menu of Links-2.23. If the required
encoding is not in the list, the program usually becomes
completely unusable. For non-interactive programs, it may be
possible to work around this by converting the document to a
supported input character set before submitting to the
program.
A solution to this type of problem is to implement the necessary support for the missing encoding as a patch to the original program or to find a replacement.
Severity: High for non-text documents, low for text documents
Some programs, nano-5.8 or JOE-4.6 for example, assume that documents are always in the encoding implied by the current locale. While this assumption may be valid for the user-created documents, it is not safe for external ones. When this assumption fails, non-ASCII characters are displayed incorrectly, and the document may become unreadable.
If the external document is entirely text based, it can be converted to the current locale encoding using the iconv program.
For documents that are not text-based, this is not possible. In fact, the assumption made in the program may be completely invalid for documents where the Microsoft Windows operating system has set de facto standards. An example of this problem is ID3v1 tags in MP3 files (see the BLFS Wiki ID3v1Coding page for more details). For these cases, the only solution is to find a replacement program that doesn't have the issue (e.g., one that will allow you to specify the assumed document encoding).
Among BLFS packages, this problem applies to nano-5.8, JOE-4.6, and all media players except Audacious-4.1.
Another problem in this category is when someone cannot read the documents you've sent them because their operating system is set up to handle character encodings differently. This can happen often when the other person is using Microsoft Windows, which only provides one character encoding for a given country. For example, this causes problems with UTF-8 encoded TeX documents created in Linux. On Windows, most applications will assume that these documents have been created using the default Windows 8-bit encoding.
In extreme cases, Windows encoding compatibility issues may be solved only by running Windows programs under Wine.
Severity: Critical
The POSIX standard mandates that the filename encoding is the
encoding implied by the current LC_CTYPE locale category.
This information is well-hidden on the page which specifies
the behavior of Tar and
Cpio programs. Some programs
get it wrong by default (or simply don't have enough
information to get it right). The result is that they create
filenames which are not subsequently shown correctly by
ls, or they
refuse to accept filenames that ls shows properly. For the
GLib-2.68.4 library, the problem can be
corrected by setting the G_FILENAME_ENCODING environment variable to
the special "@locale" value. Glib2 based programs that don't respect
that environment variable are buggy.
The Zip-3.0 and UnZip-6.0 have this problem because they hard-code the expected filename encoding. UnZip contains a hard-coded conversion table between the CP850 (DOS) and ISO-8859-1 (UNIX) encodings and uses this table when extracting archives created under DOS or Microsoft Windows. However, this assumption only works for those in the US and not for anyone using a UTF-8 locale. Non-ASCII characters will be mangled in the extracted filenames.
The general rule for avoiding this class of problems is to avoid installing broken programs. If this is impossible, the convmv command-line tool can be used to fix filenames created by these broken programs, or intentionally mangle the existing filenames to meet the broken expectations of such programs.
In other cases, a similar problem is caused by importing filenames from a system using a different locale with a tool that is not locale-aware (e.g., OpenSSH-8.7p1). In order to avoid mangling non-ASCII characters when transferring files to a system with a different locale, any of the following methods can be used:
Transfer anyway, fix the damage with convmv.
On the sending side, create a tar archive with the
--format=posix
switch passed to tar (this will be the
default in a future version of tar).
Mail the files as attachments. Mail clients specify the encoding of attached filenames.
Write the files to a removable disk formatted with a FAT or FAT32 filesystem.
Transfer the files using Samba.
Transfer the files via FTP using RFC2640-aware server (this currently means only wu-ftpd, which has bad security history) and client (e.g., lftp).
The last four methods work because the filenames are automatically converted from the sender's locale to UNICODE and stored or sent in this form. They are then transparently converted from UNICODE to the recipient's locale encoding.
Severity: High or critical
Many programs were written in an older era where multibyte locales were not common. Such programs assume that C "char" data type, which is one byte, can be used to store single characters. Further, they assume that any sequence of characters is a valid string and that every character occupies a single character cell. Such assumptions completely break in UTF-8 locales. The visible manifestation is that the program truncates strings prematurely (i.e., at 80 bytes instead of 80 characters). Terminal-based programs don't place the cursor correctly on the screen, don't react to the "Backspace" key by erasing one character, and leave junk characters around when updating the screen, usually turning the screen into a complete mess.
Fixing this kind of problems is a tedious task from a programmer's point of view, like all other cases of retrofitting new concepts into the old flawed design. In this case, one has to redesign all data structures in order to accommodate to the fact that a complete character may span a variable number of "char"s (or switch to wchar_t and convert as needed). Also, for every call to the "strlen" and similar functions, find out whether a number of bytes, a number of characters, or the width of the string was really meant. Sometimes it is faster to write a program with the same functionality from scratch.
Among BLFS packages, this problem applies to xine-ui-0.99.12 and all the shells.
Severity: Low
LFS expects that manual pages are in the language-specific (usually 8-bit) encoding, as specified on the LFS Man DB page. However, some packages install translated manual pages in UTF-8 encoding (e.g., Shadow, already dealt with), or manual pages in languages not in the table. Not all BLFS packages have been audited for conformance with the requirements put in LFS (the large majority have been checked, and fixes placed in the book for packages known to install non-conforming manual pages). If you find a manual page installed by any of BLFS packages that is obviously in the wrong encoding, please remove or convert it as needed, and report this to BLFS team as a bug.
You can easily check your system for any non-conforming manual pages by copying the following short shell script to some accessible location,
#!/bin/sh
# Begin checkman.sh
# Usage: find /usr/share/man -type f | xargs checkman.sh
for a in "$@"
do
# echo "Checking $a..."
# Pure-ASCII manual page (possibly except comments) is OK
grep -v '.\\"' "$a" | iconv -f US-ASCII -t US-ASCII >/dev/null 2>&1 \
&& continue
# Non-UTF-8 manual page is OK
iconv -f UTF-8 -t UTF-8 "$a" >/dev/null 2>&1 || continue
# Found a UTF-8 manual page, bad.
echo "UTF-8 manual page: $a" >&2
done
# End checkman.sh
and then issuing the following command (modify the command
below if the checkman.sh script is not
in your PATH environment
variable):
find /usr/share/man -type f | xargs checkman.sh
Note that if you have manual pages installed in any location
other than /usr/share/man
(e.g., /usr/local/share/man),
you must modify the above command to include this additional
location.
Last updated on
The packages that are installed in this book are only the tip of the iceberg. We hope that the experience you gained with the LFS book and the BLFS book will give you the background needed to compile, install and configure packages that are not included in this book.
When you want to install a package to a location other than
/, or /usr, you are installing outside the default
environment settings on most machines. The following examples
should assist you in determining how to correct this situation.
The examples cover the complete range of settings that may need
updating, but they are not all needed in every situation.
Expand the PATH to include
$PREFIX/bin.
Expand the PATH for
root to include
$PREFIX/sbin.
Add $PREFIX/lib to
/etc/ld.so.conf or expand
LD_LIBRARY_PATH to include it.
Before using the latter option, check out http://xahlee.org/UnixResource_dir/_/ldpath.html.
If you modify /etc/ld.so.conf, remember to update
/etc/ld.so.cache by
executing ldconfig as the
root user.
Add $PREFIX/man to
/etc/man_db.conf or expand
MANPATH.
Add $PREFIX/info to
INFOPATH.
Add $PREFIX/lib/pkgconfig
to PKG_CONFIG_PATH. Some
packages are now installing .pc files in $PREFIX/share/pkgconfig, so you may
have to include this directory also.
Add $PREFIX/include to
CPPFLAGS when compiling
packages that depend on the package you installed.
Add $PREFIX/lib to
LDFLAGS when compiling
packages that depend on a library installed by the
package.
If you are in search of a package that is not in the book, the following are different ways you can search for the desired package.
If you know the name of the package, then search Freecode
for it at http://freecode.com/. Also
search Google at http://google.com/. Sometimes a
search for the rpm at
http://rpmfind.net/ or the
deb at http://www.debian.org/distrib/packages#search_packages
can also lead to a link to the package.
If you know the name of the executable, but not the package that the executable belongs to, first try a Google search with the name of the executable. If the results are overwhelming, try searching for the given executable in the Debian repository at http://www.debian.org/distrib/packages#search_contents.
Some general hints on handling new packages:
Many of the newer packages follow the ./configure && make && make install process. Help on the options accepted by configure can be obtained via the command ./configure --help.
Most of the packages contain documentation on compiling and installing the package. Some of the documents are excellent, some not so excellent. Check out the homepage of the package for any additional and updated hints for compiling and configuring the package.
If you are having a problem compiling the package, try searching the LFS archives at https://www.linuxfromscratch.org/search.html for the error or if that fails, try searching Google. Often, a distribution will have already solved the problem (many of them use development versions of packages, so they see the changes sooner than those of us who normally use stable released versions). But be cautious - all builders tend to carry patches which are no longer necessary, and to have fixes which are only required because of their particular choices in how they build a package. You may have to search deeply to find a fix for the package version you are trying to use, or even to find the package (names are sometimes not what you might expect, e.g. ghostscript often has a prefix or a suffix in its name), but the following notes might help, particularly for those who, like the editors, are trying to build the latest versions and encountering problems:
Arch http://www.archlinux.org/packages/
- enter the package name in the 'Keywords' box,
select the package name, select the 'Source Files'
field, and then select the PKGBUILD entry to see how they
build this package.
Debian http://ftp.uk.debian.org/debian/pool
(use your country's version if there is one) - the
source will be in .tar.gz tarballs (either the
original upstream .orig source, or else a
dfsg containing those
parts which comply with debian's free software
guidelines) accompanied by versioned .diff.gz or
.tar.gz additions. These additions often show how
the package is built, and may contain patches. In
the .diff.gz versions, any patches create files in
debian/patches.
Fedora package source gets reorganized from time to time. At the moment the package source for rpms is at https://src.fedoraproject.org/projects/rpms/%2A and from there you can try putting a package name in the search box. If the package is found you can look at the files (specfile to control the build, various patches) or the commits. If that fails, you can download an srpm (source rpm) and using rpm2cpio (see the Tip at the bottom of the page). For rpms go to https://dl.fedoraproject.org/pub/fedora/linux/ and then choose which repo you wish to look at - development/rawhide is the latest development, or choose releases for what was shipped in a release, updates for updates to a release, or updates/testing for the latest updates which might work or might have problems.
Gentoo - the mirrors for ebuilds and patches seem
to be well-hidden, and they change frequently.
Also, if you have found a mirror, you need to know
which directory the application has been assigned
to. The ebuilds themselves can be found at
http://packages.gentoo.org/
- use the search field. If there are any patches, a
mirror will have them in the files/ directory. Depending on
your browser, or the mirror, you might need to
download the ebuild to be able to read it. Treat
the ebuild as a sort of pseudo-code / shell
combination - look in particular for sed commands and
patches, or hazard a guess at the meanings of the
functions such as dodoc.
openSUSE provide a rolling release, some package versions are in http://download.opensuse.org/source/tumbleweed/repo/oss/src/ but others are in ../update/openSUSE-current/src - the source only seems to be available in source rpms.
Slackware - the official package browser is
currently broken. The site at http://slackbuilds.org/
has current and previous versions in their
unofficial repository with links to homepages,
downloads, and some individual files, particularly
the .SlackBuild
files.
Ubuntu ftp://ftp.ubuntu.com/ubuntu/pool/ - see the debian notes above.
If everything else fails, try the blfs-support mailing-list.
If you have found a package that is only available in
.deb or .rpm format, there are two small scripts,
rpm2targz and
deb2targz that
are available at https://downloads.linuxfromscratch.org/deb2targz.tar.bz2
and https://downloads.linuxfromscratch.org/rpm2targz.tar.bz2
to convert the archives into a simple tar.gz format.
You may also find an rpm2cpio script useful. The Perl version in the linux kernel archives at http://lkml.indiana.edu/hypermail/linux/kernel/0210.2/att-0093/01-rpm2cpio works for most source rpms. The rpm2targz script will use an rpm2cpio script or binary if one is on your path. Note that rpm2cpio will unpack a source rpm in the current directory, giving a tarball, a spec file, and perhaps patches or other files.
Last updated on
The intention of LFS is to provide a basic system which you can build upon. There are several things about tidying up the system which many people wonder about once they have done the base install. We hope to cover these issues in this chapter.
Most people coming from non-Unix like backgrounds to Linux find
the concept of text-only configuration files slightly strange. In
Linux, just about all configuration is done via the manipulation
of text files. The majority of these files can be found in the
/etc hierarchy. There are often
graphical configuration programs available for different
subsystems but most are simply pretty front ends to the process
of editing a text file. The advantage of text-only configuration
is that you can edit parameters using your favorite text editor,
whether that be vim, emacs, or any other editor.
The first task is making a recovery boot device in Creating a Custom Boot Device because it's the most critical need. Hardware issues relevant to firmware and other devices is addressed next. The system is then configured to ease addition of new users, because this can affect the choices you make in the two subsequent topics—The Bash Shell Startup Files and The vimrc Files.
There is one remaining topic: Customizing your Logon with /etc/issue. It doesn't have much interaction with the other topics in this chapter.
This section is really about creating a rescue device. As the name rescue implies, the host system has a problem, often lost partition information or corrupted file systems, that prevents it from booting and/or operating normally. For this reason, you must not depend on resources from the host being "rescued". To presume that any given partition or hard drive will be available is a risky presumption.
In a modern system, there are many devices that can be used as a rescue device: floppy, cdrom, usb drive, or even a network card. Which one you use depends on your hardware and your BIOS. In the past, a rescue device was thought to be a floppy disk. Today, many systems do not even have a floppy drive.
Building a complete rescue device is a challenging task. In many ways, it is equivalent to building an entire LFS system. In addition, it would be a repetition of information already available. For these reasons, the procedures for a rescue device image are not presented here.
The software of today's systems has grown large. Linux 2.6 no longer supports booting directly from a floppy. In spite of this, there are solutions available using older versions of Linux. One of the best is Tom's Root/Boot Disk available at http://www.toms.net/rb/. This will provide a minimal Linux system on a single floppy disk and provides the ability to customize the contents of your disk if necessary.
There are several sources that can be used for a rescue CD-ROM. Just about any commercial distribution's installation CD-ROMs or DVDs will work. These include RedHat, Ubuntu, and SuSE. One very popular option is Knoppix.
Also, the LFS Community has developed its own LiveCD available at https://www.linuxfromscratch.org/livecd/. This LiveCD, is no longer capable of building an entire LFS/BLFS system, but is still a good rescue CD-ROM. If you download the ISO image, use xorriso to copy the image to a CD-ROM.
The instructions for using GRUB2 to make a custom rescue CD-ROM are also available in LFS Chapter 10.
A USB Pen drive, sometimes called a Thumb drive, is recognized by Linux as a SCSI device. Using one of these devices as a rescue device has the advantage that it is usually large enough to hold more than a minimal boot image. You can save critical data to the drive as well as use it to diagnose and recover a damaged system. Booting such a drive requires BIOS support, but building the system consists of formatting the drive, adding GRUB as well as the Linux kernel and supporting files.
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/CreatingaCustomBootDevice
Last updated on
An LFS system can be used without a graphical desktop, and unless or until you install X Window System you will have to work in the console. Most, if not all, PCs boot with an 8x16 font - whatever the actual screen size. There are a few things you can do to alter the display on the console. Most of them involve changing the font, but the first alters the commandline used by grub.
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/aboutconsolefonts
Modern screens often have a lot more pixels then the screens used in the past. If your screen is 1600 pixels wide, an 8x16 font will give you 200 columns of text - unless your monitor is enormous, the text will be tiny. One of the ways to work around this is to tell grub to use a smaller size, such as 1024x768 or 800x600 or even 640x480. Even if your screen does not have a 4:3 aspect ratio, this should work.
To try this, you can reboot and edit grub's command-line to
insert a 'video=' parameter between the 'root=/dev/sdXn' and
'ro', for example root=/dev/sda2
video=1024x768 ro based on the example in LFS section
10.4.4 : ../../../../lfs/view/11.0-systemd/chapter10/grub.html.
If you decide that you wish to do this, you can then (as the
root user) edit /boot/grub/grub.cfg.
In LFS the kbd package is
used. The fonts it provides are PC Screen Fonts, usually
called PSF, and they were installed into /usr/share/consolefonts. Where these
include a unicode mapping table, the file suffix is often
changed to .psfu although
packages such as terminus-font (see below) do not add the
'u'. These fonts are usually compressed with gzip to save
space, but that is not essential.
The initial PC text screens had 8 colours, or 16 colours if the bright versions of the original 8 colours were used. A PSF font can include up to 256 characters (technically, glyphs) while allowing 16 colours, or up to 512 characters (in which case, the bright colours will not be available). Clearly, these console fonts cannot be used to display CJK text - that would need thousands of available glyphs.
Some fonts in kbd can cover more than 512 codepoints ('characters'), with varying degrees of fidelity: unicode contains several whitespace codepoints which can all be mapped to a space, varieties of dashes can be mapped to a minus sign, smart quotes can map to the regular ASCII quotes rather than to whatever is used for "codepoint not present or invalid", and those cyrillic or greek letters which look like latin letters can be mapped onto them, so 'A' can also do duty for cyrillic A and greek Alpha, and 'P' can also do duty for cyrillic ER and greek RHO. Unfortunately, where a font has been created from a BDF file (the method in terminus and debian's console-setup ) such mapping of additional codepoints onto an existing glyph is not always done, although the terminus ter-vXXn fonts do this well.
There are over 120 combinations of font and size in
kbd: often a font is
provided at several character sizes, and sometimes varieties
cover different subsets of unicode. Most are 8 pixels wide,
in heights from 8 to 16 pixels, but there are a few which are
9 pixels wide, some others which are 12x22, and even one
(latarcyrheb-sun32.psfu) which
has been scaled up to 16x32. Using a bigger font is another
way of making text on a large screen easier to read.
You can test fonts as a normal user. If you have a font which has not been installed, you can load it with :
setfont /path/to/yourfont.ext
For the fonts already installed you only need the name, so
using gr737a-9x16.psfu.gz as an
example:
setfont gr737a-9x16
To see the glyphs in the font, use:
showconsolefont
If the font looks as if it might be useful, you can then go on to test it more thoroughly.
When you find a font which you wish to use, as the
root user) edit /etc/vconsole.conf as
described in LFS section 9.6 ../../../../lfs/view/11.0-systemd/chapter09/console.html..
For fonts not supplied with the kbd package you will need to optionally
compress it / them with gzip and then install it /
them as the root user.
Although some console fonts are created from BDF files, which is a text format with hex values for the pixels in each row of the character, there are more-modern tools available for editing psf fonts. The psftools package allows you to dump a font to a text representation with a dash for a pixel which is off (black) and a hash for a pixel which is on (white). You can then edit the text file to add more characters, or reshape them, or map extra codepoints onto them, and then create a new psf font with your changes.
The Terminus Font
package provides fixed-width bitmap fonts designed for long
(8 hours and more per day) work with computers. Under
'Character variants' on that page is a list of patches (in
the alt/ directory). If you are
using a graphical browser to look at that page, you can see
what the patches do, e.g. 'll2' makes 'l' more visibly
different from 'i' and '1'.
By default terminus-fonts will try to create several types of font, and it will fail if bdftopcf from Xorg Applications has not been installed. The configure script is only really useful if you go on to install all the fonts (console and X11 bitmap) to the correct directories, as in a distro. To build only the PSF fonts and their dependencies, run:
make psf
This will create more than 240 ter-*.psf fonts. The 'b' suffix indicates bright, 'n' indicates normal. You can then test them to see if any fit your requirements. Unless you are creating a distro, there seems little point in installing them all.
As an example, to install the last of these fonts, you can
gzip it and then as the root
user:
install -v -m644 ter-v32n.psf.gz /usr/share/consolefonts
Last updated on
On some recent PCs it can be necessary, or desirable, to load
firmware to make them work at their best. There is a directory,
/lib/firmware, where the kernel
or kernel drivers look for firmware images.
Currently, most firmware can be found at a git repository:
http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/.
For convenience, the LFS Project has created a mirror, updated
daily, where these firmware files can be accessed via
wget or a web
browser at https://anduin.linuxfromscratch.org/BLFS/linux-firmware/.
To get the firmware, either point a browser to one of the above repositories and then download the item(s) which you need, or install git-2.33.0 and clone that repository.
For some other firmware, particularly for Intel microcode and certain wifi devices, the needed firmware is not available in the above repository. Some of this will be addressed below, but a search of the Internet for needed firmware is sometimes necessary.
Firmware files are conventionally referred to as blobs because you cannot determine what they will do. Note that firmware is distributed under various different licenses which do not permit disassembly or reverse-engineering.
Firmware for PCs falls into four categories:
Updates to the CPU to work around errata, usually referred to as microcode.
Firmware for video controllers. On x86 machines this is required for ATI devices (Radeon and AMDGPU chips) and may be useful for Intel (Skylake and later) and Nvidia (Kepler and later) GPUs.
ATI Radeon and AMGPU devices all require firmware to be able to use KMS (kernel modesetting - the preferred option) as well as for Xorg. For old radeon chips (before the R600), the firmware is still in the kernel source.
Intel integrated GPUs from Skylake onwards can use firmware for GuC (the Graphics microcontroller), and also for the HuC (HEVC/H265 microcontroller which offloads to the GPU) and the DMC (Display Microcontroller) to provide additional low-power states. The GuC and HuC have had a chequered history in the kernel and updated firmware may be disabled by default, depending on your kernel version. Further details may be found at 01.org and Arch linux.
Nvidia GPUs from Kepler onwards require signed firmware, otherwise the nouveau driver is unable to provide hardware acceleration. Nvidia has now released firmware up to Turing (most, maybe all, GTX16xx and RTX20xx GPUs) to linux-firmware, and kernels from linux-5.6 should support it, although Mesa support may require a development version until Mesa-20.2 is released. Note that faster clocks than the default are not enabled by the released firmware.
Firmware updates for wired network ports. Mostly they work even without the updates, but probably they will work better with the updated firmware. For some modern laptops, firmware for both wired ethernet (e.g. rtl_nic) and also for bluetooth devices (e.g. qca) is required before the wired network can be used.
Firmware for other devices, such as wifi. These devices are not required for the PC to boot, but need the firmware before these devices can be used.
Although not needed to load a firmware blob, the following tools may be useful for determining, obtaining, or preparing the needed firmware in order to load it into the system: cpio-2.13, git-2.33.0, pciutils-3.7.0, and Wget-1.21.1
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/aboutfirmware
In general, microcode can be loaded by the BIOS or UEFI, and it might be updated by upgrading to a newer version of those. On linux, you can also load the microcode from the kernel if you are using an AMD family 10h or later processor (first introduced late 2007), or an Intel processor from 1998 and later (Pentium4, Core, etc), if updated microcode has been released. These updates only last until the machine is powered off, so they need to be applied on every boot.
Intel provide updates of their microcode for Skylake and later processors as new vulnerabilities come to light, and have in the past provided updates for processors from SandyBridge onwards, although those are no-longer supported for new fixes. New versions of AMD firmware are rare and usually only apply to a few models, although motherboard manufacturers get extra updates which maybe update microcode along with the changes to support newer CPUs and faster memory.
There are two ways of loading the microcode, described as 'early' and 'late'. Early loading happens before userspace has been started, late loading happens after userspace has started. Not surprisingly, early loading is preferred, (see e.g. an explanatory comment in a kernel commit noted at x86/microcode: Early load microcode on LWN.) Indeed, it is needed to work around one particular erratum in early Intel Haswell processors which had TSX enabled. (See Intel Disables TSX Instructions: Erratum Found in Haswell, Haswell-E/EP, Broadwell-Y .) Without this update glibc can do the wrong thing in uncommon situations.
It is still possible to manually force late loading of
microcode, either for testing or to prevent having to reboot.
You will need to reconfigure your kernel for either method.
The instructions here will create a kernel .config to suite early loading, before
forcing late loading to see if there is any microcode. If
there is, the instructions then show you how to create an
initrd for early loading.
To confirm what processor(s) you have (if more than one, they will be identical) look in /proc/cpuinfo.
If you are creating an initrd to update firmware for different machines, as a distro would do, go down to 'Early loading of microcode' and cat all the Intel blobs to GenuineIntel.bin or cat all the AMD blobs to AuthenticAMD.bin. This creates a larger initrd - for all Intel machines in the 20200609 update the size is 3.0 MB compared to typically 24 KB for one machine.
The first step is to get the most recent version of the
Intel microcode. This must be done by navigating to
https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/
and downloading the latest file there. As of this writing
the most secure version of the microcode, for those
machines which can boot it, is microcode-20210608. Extract
this file in the normal way, the microcode is in the
intel-ucode directory,
containing various blobs with names in the form XX-YY-ZZ.
There are also various other files, and a releasenote.
In the past, intel did not provide any details of which blobs had changed versions, but now the release note details this.
The recent firmware for older processors is provided to deal with vulnerabilities which have now been made public, and for some of these such as Microarchitectural Data Sampling (MDS) you might wish to increase the protection by disabling hyperthreading, or alternatively to disable the kernel's default mitigation because of its impact on compile times. Please read the online documentation at https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/index.html.
Now you need to determine your processor's identity to see if there is any microcode for it. Determine the decimal values of the cpu family, model and stepping by running the following command (it will also report the current microcode version):
head -n7 /proc/cpuinfo
Convert the cpu family, model and stepping to pairs of hexadecimal digits. For a Skylake i3 6100 (described as Intel(R) Core(TM) i3-6100 CPU) the relevant values are cpu family 6, model 94, stepping 3 so in this case the required identification is 06-5e-03. A look at the blobs will show that there is one for this CPU (although for older issues it might have already been applied by the BIOS). If there is a blob for your system then test if it will be applied by copying it (replace <XX-YY-ZZ> by the identifier for your CPU) to where the kernel can find it:
mkdir -pv /lib/firmware/intel-ucode cp -v intel-ucode/<XX-YY-ZZ> /lib/firmware/intel-ucode
Now that the Intel microcode has been prepared, use the following options when you configure the kernel to load Intel microcode:
General Setup --->
[*] Initial RAM filesystem and RAM disk (initramfs/initrd) support [CONFIG_BLK_DEV_INITRD]
Processor type and features --->
[*] CPU microcode loading support [CONFIG_MICROCODE]
[*] Intel microcode loading support [CONFIG_MICROCODE_INTEL]After you have successfully booted the new system, force late loading by using the command:
echo 1 > /sys/devices/system/cpu/microcode/reload
Then use the following command to see if anything was loaded: (N.B. the dates when microcode was created may be months ahead of when it was released.)
dmesg | grep -e 'microcode' -e 'Linux version' -e 'Command line'
This reformatted example for a machine with old microcode in its BIOS was created by temporarily booting without microcode, to show the current Firmware Bug messages, then the late load shows it being updated to revision 0xea.
[ 0.000000] Linux version 5.12.8 (lfs@leshp) (gcc (GCC) 11.1.0,
GNU ld (GNU Binutils) 2.36.1)
#2 SMP PREEMPT Fri Jun 4 01:25:02 BST 2021
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-5.12.8-sda11 root=/dev/sda11 ro
resume=/dev/sda10
[ 0.028741] [Firmware Bug]: TSC_DEADLINE disabled due to Errata;
please update microcode to version: 0xb2 (or later)
[ 0.115716] SRBDS: Vulnerable: No microcode
[ 0.115826] MDS: Vulnerable: Clear CPU buffers attempted, no microcode
[ 0.389005] microcode: sig=0x506e3, pf=0x2, revision=0x74
[ 0.389030] microcode: Microcode Update Driver: v2.2.
[ 70.089502] microcode: updated to revision 0xea, date = 2021-01-25
[ 70.089528] x86/CPU: CPU features have changed after loading microcode,
but might not take effect.
[ 70.089530] microcode: Reload completed, microcode revision: 0xeaIf the microcode was not updated, there is no new microcode for this system's processor. If it did get updated, you can now proceed to the section called “Early loading of microcode”.
Begin by downloading a container of firmware for your CPU
family from
https://anduin.linuxfromscratch.org/BLFS/linux-firmware/amd-ucode/.
The family is always specified in hex. Families 10h to 14h
(16 to 20) are in microcode_amd.bin. Families 15h, 16h and
17h have their own containers. Create the required
directory and put the firmware you downloaded into it as
the root user:
mkdir -pv /lib/firmware/amd-ucode cp -v microcode_amd* /lib/firmware/amd-ucode
When you configure the kernel, use the following options to load AMD microcode:
General Setup --->
[*] Initial RAM filesystem and RAM disk (initramfs/initrd) support [CONFIG_BLK_DEV_INITRD]
Processor type and features --->
[*] CPU microcode loading support [CONFIG_MICROCODE]
[*] AMD microcode loading support [CONFIG_MICROCODE_AMD]After you have successfully booted the new system, force late loading by using the command:
echo 1 > /sys/devices/system/cpu/microcode/reload
Then use the following command to see if anything was loaded:
dmesg | grep -e 'microcode' -e 'Linux version' -e 'Command line'
This historic example from an old Athlon(tm) II X2 shows it has been updated. At that time, all CPUs were still reported in the microcode details on AMD machines (the current position for AMD machines where newer microcode is available is unknown) :
[ 0.000000] Linux version 4.15.3 (ken@testserver) (gcc version 7.3.0 (GCC))
#1 SMP Sun Feb 18 02:08:12 GMT 2018
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.15.3-sda5 root=/dev/sda5 ro
[ 0.307619] microcode: CPU0: patch_level=0x010000b6
[ 0.307671] microcode: CPU1: patch_level=0x010000b6
[ 0.307743] microcode: Microcode Update Driver: v2.2.
[ 187.928891] microcode: CPU0: new patch_level=0x010000c8
[ 187.928899] microcode: CPU1: new patch_level=0x010000c8If the microcode was not updated, there is no new microcode for this system's processor. If it did get updated, you can now proceed to the section called “Early loading of microcode”.
If you have established that updated microcode is available for your system, it is time to prepare it for early loading. This requires an additional package, cpio-2.13 and the creation of an initrd which will need to be added to grub.cfg.
It does not matter where you prepare the initrd, and once it is working you can apply the same initrd to later LFS systems or newer kernels on this same machine, at least until any newer microcode is released. Use the following commands:
mkdir -p initrd/kernel/x86/microcode cd initrd
For an AMD machine, use the following command (replace <MYCONTAINER> with the name of the container for your CPU's family):
cp -v /lib/firmware/amd-ucode/<MYCONTAINER> kernel/x86/microcode/AuthenticAMD.bin
Or for an Intel machine copy the appropriate blob using this command:
cp -v /lib/firmware/intel-ucode/<XX-YY-ZZ> kernel/x86/microcode/GenuineIntel.bin
Now prepare the initrd:
find . | cpio -o -H newc > /boot/microcode.img
You now need to add a new entry to /boot/grub/grub.cfg and here you should add a new line after the linux line within the stanza. If /boot is a separate mountpoint:
initrd /microcode.img
or this if it is not:
initrd /boot/microcode.img
If you are already booting with an initrd (see the
section called “About initramfs”), you
should run mkinitramfs again after
putting the appropriate blob or container into /lib/firmware as explained above.
Alternatively, you can have both initrd on the same line,
such as initrd
/microcode.img /other-initrd.img (adapt
that as above if /boot is not a separate mountpoint).
You can now reboot with the added initrd, and then use the same command to check that the early load worked:
dmesg | grep -e 'microcode' -e 'Linux version' -e 'Command line'
If you updated to address vulnerabilities, you can look at
/sys/devices/system/cpu/vulnerabilities/
to see what is now reported.
The places and times where early loading happens are very different in AMD and Intel machines. First, an Intel (Skylake) example with early loading:
[ 0.000000] microcode: microcode updated early to revision 0xea, date = 2021-01-25
[ 0.000000] Linux version 5.12.8 (lfs@leshp) (gcc (GCC) 11.1.0,
GNU ld (GNU Binutils) 2.36.1) #2 SMP PREEMPT Fri Jun 4 01:25:02 BST 2021
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-5.12.8-sda11 root=/dev/sda11 ro
resume=/dev/sda10
[ 0.381420] microcode: sig=0x506e3, pf=0x2, revision=0xea
[ 0.381479] microcode: Microcode Update Driver: v2.2.A historic AMD example:
[ 0.000000] Linux version 4.15.3 (ken@testserver) (gcc version 7.3.0 (GCC))
#2 SMP Sun Feb 18 02:32:03 GMT 2018
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.15.3-sda5 root=/dev/sda5 ro
[ 0.307619] microcode: microcode updated early to new patch_level=0x010000c8
[ 0.307678] microcode: CPU0: patch_level=0x010000c8
[ 0.307723] microcode: CPU1: patch_level=0x010000c8
[ 0.307795] microcode: Microcode Update Driver: v2.2.
These instructions do NOT apply to old radeons before the
R600 family. For those, the firmware is in the kernel's
/lib/firmware/ directory. Nor
do they apply if you intend to avoid a graphical setup such
as Xorg and are content to use the default 80x25 display
rather than a framebuffer.
Early radeon devices only needed a single 2K blob of firmware. Recent devices need several different blobs, and some of them are much bigger. The total size of the radeon firmware directory is over 500K — on a large modern system you can probably spare the space, but it is still redundant to install all the unused files each time you build a system.
A better approach is to install pciutils-3.7.0 and
then use lspci to identify which
VGA controller is installed.
With that information, check the RadeonFeature page of the Xorg wiki for Decoder ring for engineering vs marketing names to identify the family (you may need to know this for the Xorg driver in BLFS — Southern Islands and Sea Islands use the radeonsi driver) and the specific model.
Now that you know which controller you are using, consult the Radeon page of the Gentoo wiki which has a table listing the required firmware blobs for the various chipsets. Note that Southern Islands and Sea Islands chips use different firmware for kernel 3.17 and later compared to earlier kernels. Identify and download the required blobs then install them:
mkdir -pv /lib/firmware/radeon cp -v <YOUR_BLOBS> /lib/firmware/radeon
There are actually two ways of installing this firmware. BLFS, in the 'Kernel Configuration for additional firmware' section part of the Xorg ATI Driver-19.1.0 section gives an example of compiling the firmware into the kernel - that is slightly faster to load, but uses more kernel memory. Here we will use the alternative method of making the radeon driver a module. In your kernel config set the following:
Device Drivers --->
Graphics support --->
Direct Rendering Manager --->
[*] Direct Rendering Manager (XFree86 ... support) [CONFIG_DRM]
[M] ATI Radeon [CONFIG_DRM_RADEON]Loading several large blobs from /lib/firmware takes a noticeable time, during which the screen will be blank. If you do not enable the penguin framebuffer logo, or change the console size by using a bigger font, that probably does not matter. If desired, you can slightly reduce the time if you follow the alternate method of specifying 'y' for CONFIG_DRM_RADEON covered in BLFS at the link above — you must specify each needed radeon blob if you do that.
Some Nvidia graphics chips need firmware updates to take advantage of all the card's capability. These are generally the GeForce 8, 9, 9300, and 200-900 series chips. For more exact information, see https://nouveau.freedesktop.org/wiki/VideoAcceleration/#firmware.
First, the kernel Nvidia driver must be activated:
Device Drivers --->
Graphics support --->
Direct Rendering Manager --->
<*> Direct Rendering Manager (XFree86 ... support) [CONFIG_DRM]
<*/M> Nouveau (NVIDIA) cards [CONFIG_DRM_NOUVEAU]The steps to install the Nvidia firmware are:
wget https://raw.github.com/imirkin/re-vp2/master/extract_firmware.py wget http://us.download.nvidia.com/XFree86/Linux-x86/325.15/NVIDIA-Linux-x86-325.15.run sh NVIDIA-Linux-x86-325.15.run --extract-only python extract_firmware.py mkdir -p /lib/firmware/nouveau cp -d nv* vuc-* /lib/firmware/nouveau/
The kernel likes to load firmware for some network drivers,
particularly those from Realtek (the
/lib/linux-firmware/rtl_nic/) directory, but they generally
appear to work without it. Therefore, you can boot the
kernel, check dmesg for messages about this missing firmware,
and if necessary download the firmware and put it in the
specified directory in /lib/firmware so that it will be found on
subsequent boots. Note that with current kernels this works
whether or not the driver is compiled in or built as a
module, there is no need to build this firmware into the
kernel. Here is an example where the R8169 driver has been
compiled in but the firmware was not made available. Once the
firmware had been provided, there was no mention of it on
later boots.
dmesg | grep firmware | grep r8169
[ 7.018028] r8169 0000:01:00.0: Direct firmware load for rtl_nic/rtl8168g-2.fw failed with error -2
[ 7.018036] r8169 0000:01:00.0 eth0: unable to load firmware patch rtl_nic/rtl8168g-2.fw (-2)
Identifying the correct firmware will typically require you
to install pciutils-3.7.0, and then use
lspci to
identify the device. You should then search online to check
which module it uses, which firmware, and where to obtain the
firmware — not all of it is in linux-firmware.
If possible, you should begin by using a wired connection when you first boot your LFS system. To use a wireless connection you will need to use a network tools such as Wireless Tools-29 and wpa_supplicant-2.9.
Different countries have different regulations on the radio
spectrum usage of wireless devices. You can install a
firmware to make the wireless devices obey local spectrum
regulations, so you won't be inquired by local authority or
find your wireless NIC jamming the frequencies of other
devices (for example, remote controllers). The regulatory
database firmware can be downloaded from https://kernel.org/pub/software/network/wireless-regdb/.
To install it, simply extract regulatory.db and regulatory.db.p7s from the tarball into
/lib/firmware. The access point
would send a country code to your wireless NIC, and wpa_supplicant-2.9 would tell the
kernel to load the regulation of this country from
regulatory.db, and enforce it.
Firmware may also be needed for other devices such as some SCSI controllers, bluetooth adaptors, or TV recorders. The same principles apply.
Last updated on
Although most devices needed by packages in BLFS and beyond are
set up properly by udev using
the default rules installed by LFS in /etc/udev/rules.d, there are cases where the
rules must be modified or augmented.
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/aboutdevices
If there are multiple sound cards in a system, the "default"
sound card becomes random. The method to establish sound card
order depends on whether the drivers are modules or not. If
the sound card drivers are compiled into the kernel, control
is via kernel command line parameters in /boot/grub/grub.cfg. For example, if a
system has both an FM801 card and a SoundBlaster PCI card,
the following can be appended to the command line:
snd-fm801.index=0 snd-ens1371.index=1
If the sound card drivers are built as modules, the order can
be established in the /etc/modprobe.conf file with:
options snd-fm801 index=0
options snd-ens1371 index=1USB devices usually have two kinds of device nodes associated with them.
The first kind is created by device-specific drivers (e.g., usb_storage/sd_mod or usblp) in the kernel. For example, a USB mass storage device would be /dev/sdb, and a USB printer would be /dev/usb/lp0. These device nodes exist only when the device-specific driver is loaded.
The second kind of device nodes (/dev/bus/usb/BBB/DDD, where BBB is the bus number and DDD is the device number) are created even if the device doesn't have a kernel driver. By using these "raw" USB device nodes, an application can exchange arbitrary USB packets with the device, i.e., bypass the possibly-existing kernel driver.
Access to raw USB device nodes is needed when a userspace program is acting as a device driver. However, for the program to open the device successfully, the permissions have to be set correctly. By default, due to security concerns, all raw USB devices are owned by user root and group usb, and have 0664 permissions (the read access is needed, e.g., for lsusb to work and for programs to access USB hubs). Packages (such as SANE and libgphoto2) containing userspace USB device drivers also ship udev rules that change the permissions of the controlled raw USB devices. That is, rules installed by SANE change permissions for known scanners, but not printers. If a package maintainer forgot to write a rule for your device, report a bug to both BLFS (if the package is there) and upstream, and you will need to write your own rule.
There is one situation when such fine-grained access control with pre-generated udev rules doesn't work. Namely, PC emulators such as KVM, QEMU and VirtualBox use raw USB device nodes to present arbitrary USB devices to the guest operating system (note: patches are needed in order to get this to work without the obsolete /proc/bus/usb mount point described below). Obviously, maintainers of these packages cannot know which USB devices are going to be connected to the guest operating system. You can either write separate udev rules for all needed USB devices yourself, or use the default catch-all "usb" group, members of which can send arbitrary commands to all USB devices.
Before Linux-2.6.15, raw USB device access was performed not with /dev/bus/usb/BBB/DDD device nodes, but with /proc/bus/usb/BBB/DDD pseudofiles. Some applications (e.g., VMware Workstation) still use only this deprecated technique and can't use the new device nodes. For them to work, use the "usb" group, but remember that members will have unrestricted access to all USB devices. To create the fstab entry for the obsolete usbfs filesystem:
usbfs /proc/bus/usb usbfs devgid=14,devmode=0660 0 0Adding users to the "usb" group is inherently insecure, as they can bypass access restrictions imposed through the driver-specific USB device nodes. For instance, they can read sensitive data from USB hard drives without being in the "disk" group. Avoid adding users to this group, if you can.
Fine-tuning of device attributes such as group name and
permissions is possible by creating extra udev rules, matching on something like
this. The vendor and product can be found by searching the
/sys/devices directory entries
or using udevadm
info after the device has been attached. See
the documentation in the current udev directory of /usr/share/doc for details.
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="05d8", SYSFS{idProduct}=="4002", \
GROUP:="scanner", MODE:="0660"The above line is used for descriptive purposes only. The scanner udev rules are put into place when installing SANE-1.0.29.
If the initial boot process does not set up the /dev/dvd device properly, it can be
installed using the following modification to the default
udev rules. As the root user,
run:
sed '1d;/SYMLINK.*cdrom/ a\
KERNEL=="sr0", ENV{ID_CDROM_DVD}=="1", SYMLINK+="dvd", OPTIONS+="link_priority=-100"' \
/lib/udev/rules.d/60-cdrom_id.rules > /etc/udev/rules.d/60-cdrom_id.rules
Last updated on
Together, the /usr/sbin/useradd command and
/etc/skel directory (both are
easy to set up and use) provide a way to assure new users are
added to your LFS system with the same beginning settings for
things such as the PATH, keyboard
processing and other environmental variables. Using these two
facilities makes it easier to assure this initial state for
each new user added to the system.
The /etc/skel directory holds
copies of various initialization and other files that may be
copied to the new user's home directory when the /usr/sbin/useradd program
adds the new user.
The useradd
program uses a collection of default values kept in
/etc/default/useradd. This file
is created in a base LFS installation by the Shadow package. If it has been removed or
renamed, the useradd program uses some
internal defaults. You can see the default values by running
/usr/sbin/useradd
-D.
To change these values, simply modify the /etc/default/useradd file as the root user. An alternative to directly
modifying the file is to run useradd as the root user while supplying the desired
modifications on the command line. Information on how to do
this can be found in the useradd man page.
To get started, create an /etc/skel directory and make sure it is
writable only by the system administrator, usually root. Creating the directory as
root is the best way to go.
The mode of any files from this part of the book that you put
in /etc/skel should be writable
only by the owner. Also, since there is no telling what kind of
sensitive information a user may eventually place in their copy
of these files, you should make them unreadable by "group" and
"other".
You can also put other files in /etc/skel and different permissions may be
needed for them.
Decide which initialization files should be provided in every
(or most) new user's home directory. The decisions you make
will affect what you do in the next two sections, The Bash Shell Startup Files
and The vimrc Files. Some
or all of those files will be useful for root, any already-existing users, and new
users.
The files from those sections that you might want to place in
/etc/skel include .inputrc, .bash_profile, .bashrc, .bash_logout, .dircolors, and .vimrc. If you are unsure which of these
should be placed there, just continue to the following
sections, read each section and any references provided, and
then make your decision.
You will run a slightly modified set of commands for files
which are placed in /etc/skel.
Each section will remind you of this. In brief, the book's
commands have been written for files not added to /etc/skel and instead just sends the results
to the user's home directory. If the file is going to be in
/etc/skel, change the book's
command(s) to send output there instead and then just copy the
file from /etc/skel to the
appropriate directories, like /etc, ~ or the
home directory of any other user already in the system.
When adding a new user with useradd, use the -m parameter, which tells useradd to create the user's
home directory and copy files from /etc/skel (can be overridden) to the new
user's home directory. For example (perform as the root user):
useradd -m <newuser>
Last updated on
Throughout BLFS, many packages install programs that run as
daemons or in some way should have a user or group name
assigned. Generally these names are used to map a user ID (uid)
or group ID (gid) for system use. Generally the specific uid or
gid numbers used by these applications are not significant. The
exception of course, is that root has a uid and gid of 0 (zero) that is
indeed special. The uid values are stored in /etc/passwd and the gid values are found in
/etc/group.
Customarily, Unix systems classify users and groups into two
categories: system users and regular users. The system users
and groups are given low numbers and regular users and groups
have numeric values greater than all the system values. The
cutoff for these numbers is found in two parameters in the
/etc/login.defs configuration
file. The default UID_MIN value is 1000 and the default GID_MIN
value is 1000. If a specific uid or gid value is not specified
when creating a user with useradd or a group with
groupadd the
values assigned will always be above these cutoff values.
Additionally, the Linux Standard Base recommends that system uid and gid values should be below 100.
Below is a table of suggested uid/gid values used in BLFS beyond those defined in a base LFS installation. These can be changed as desired, but provide a suggested set of consistent values.
Table 3.1. UID/GID Suggested Values
| Name | uid | gid |
|---|---|---|
| bin | 1 | |
| lp | 9 | |
| adm | 16 | |
| atd | 17 | 17 |
| messagebus | 18 | 18 |
| lpadmin | 19 | |
| named | 20 | 20 |
| gdm | 21 | 21 |
| fcron | 22 | 22 |
| systemd-journal | 23 | 23 |
| apache | 25 | 25 |
| smmsp | 26 | 26 |
| polkitd | 27 | 27 |
| rpc | 28 | 28 |
| exim | 31 | 31 |
| postfix | 32 | 32 |
| postdrop | 33 | |
| sendmail | 34 | |
| 34 | ||
| vmailman | 35 | 35 |
| news | 36 | 36 |
| kdm | 37 | 37 |
| fetchmail | 38 | |
| mysql | 40 | 40 |
| postgres | 41 | 41 |
| dovecot | 42 | 42 |
| dovenull | 43 | 43 |
| ftp | 45 | 45 |
| proftpd | 46 | 46 |
| vsftpd | 47 | 47 |
| rsyncd | 48 | 48 |
| sshd | 50 | 50 |
| stunnel | 51 | 51 |
| dhcpcd | 52 | 52 |
| svn | 56 | 56 |
| svntest | 57 | |
| git | 58 | 58 |
| games | 60 | 60 |
| kvm | 61 | |
| wireshark | 62 | |
| lightdm | 63 | 63 |
| sddm | 64 | 64 |
| lightdm | 65 | 65 |
| scanner | 70 | |
| colord | 71 | 71 |
| systemd-bus-proxy | 72 | 72 |
| systemd-journal-gateway | 73 | 73 |
| systemd-journal-remote | 74 | 74 |
| systemd-journal-upload | 75 | 75 |
| systemd-network | 76 | 76 |
| systemd-resolve | 77 | 77 |
| systemd-timesync | 78 | 78 |
| systemd-coredump | 79 | 79 |
| uuidd | 80 | 80 |
| systemd-oom | 81 | 81 |
| ldap | 83 | 83 |
| avahi | 84 | 84 |
| avahi-autoipd | 85 | 85 |
| netdev | 86 | |
| ntp | 87 | 87 |
| unbound | 88 | 88 |
| plugdev | 90 | |
| wheel | 97 | |
| anonymous | 98 | |
| nobody | 99 | |
| nogroup | 99 |
One value that is missing is 65534. This value is customarily
assigned to the user nobody and
group nogroup and is
unnecessary.
Last updated on
The shell program /bin/bash
(hereafter referred to as just "the shell") uses a collection
of startup files to help create an environment. Each file has a
specific use and may affect login and interactive environments
differently. The files in the /etc directory generally provide global
settings. If an equivalent file exists in your 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. This shell
invocation normally reads /etc/profile and its private equivalent
~/.bash_profile (or ~/.profile if called as /bin/sh) upon startup.
An interactive non-login shell is normally started at the
command-line using a shell program (e.g., [prompt]$/bin/bash) or by the
/bin/su command.
An interactive non-login shell is also started with a terminal
program such as xterm or konsole from within a
graphical environment. This type of shell invocation normally
copies the parent environment and then reads the user's
~/.bashrc file for additional
startup configuration instructions.
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 these shell invocations, only the environment inherited from the parent shell is used.
The file ~/.bash_logout is not
used for an invocation of the shell. It is read and executed
when a user exits from an interactive login shell.
Many distributions use /etc/bashrc for system wide initialization of
non-login shells. This file is usually called from the user's
~/.bashrc file and is not built
directly into bash itself. This convention
is followed in this section.
For more information see info bash -- Nodes: Bash Startup Files and Interactive Shells.
Most of the instructions below are used to create files
located in the /etc directory
structure which requires you to execute the commands as the
root user. If you elect to
create the files in user's home directories instead, you
should run the commands as an unprivileged user.
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/bash-shell-startup-files
Here is a base /etc/profile.
This file starts by setting up some helper functions and some
basic parameters. It specifies some bash history parameters
and, for security purposes, disables keeping a permanent
history file for the root
user. It also sets a default user prompt. It then calls
small, single purpose scripts in the /etc/profile.d directory to provide most of
the initialization.
For more information on the escape sequences you can use for
your prompt (i.e., the PS1
environment variable) see info
bash -- Node:
Printing a Prompt.
cat > /etc/profile << "EOF"
# Begin /etc/profile
# Written for Beyond Linux From Scratch
# by James Robertson <[email protected]>
# modifications by Dagmar d'Surreal <[email protected]>
# System wide environment variables and startup programs.
# System wide aliases and functions should go in /etc/bashrc. Personal
# environment variables and startup programs should go into
# ~/.bash_profile. Personal aliases and functions should go into
# ~/.bashrc.
# Functions to help us manage paths. Second argument is the name of the
# path variable to be modified (default: PATH)
pathremove () {
local IFS=':'
local NEWPATH
local DIR
local PATHVARIABLE=${2:-PATH}
for DIR in ${!PATHVARIABLE} ; do
if [ "$DIR" != "$1" ] ; then
NEWPATH=${NEWPATH:+$NEWPATH:}$DIR
fi
done
export $PATHVARIABLE="$NEWPATH"
}
pathprepend () {
pathremove $1 $2
local PATHVARIABLE=${2:-PATH}
export $PATHVARIABLE="$1${!PATHVARIABLE:+:${!PATHVARIABLE}}"
}
pathappend () {
pathremove $1 $2
local PATHVARIABLE=${2:-PATH}
export $PATHVARIABLE="${!PATHVARIABLE:+${!PATHVARIABLE}:}$1"
}
export -f pathremove pathprepend pathappend
# Set the initial path
export PATH=/usr/bin
# Attempt to provide backward compatibility with LFS earlier than 11
if [ ! -L /bin ]; then
pathappend /bin
fi
if [ $EUID -eq 0 ] ; then
pathappend /usr/sbin
if [ ! -L /sbin ]; then
pathappend /sbin
fi
unset HISTFILE
fi
# Setup some environment variables.
export HISTSIZE=1000
export HISTIGNORE="&:[bf]g:exit"
# Set some defaults for graphical systems
export XDG_DATA_DIRS=${XDG_DATA_DIRS:-/usr/share/}
export XDG_CONFIG_DIRS=${XDG_CONFIG_DIRS:-/etc/xdg/}
export XDG_RUNTIME_DIR=${XDG_RUNTIME_DIR:-/tmp/xdg-$USER}
# Setup a red prompt for root and a green one for users.
NORMAL="\[\e[0m\]"
RED="\[\e[1;31m\]"
GREEN="\[\e[1;32m\]"
if [[ $EUID == 0 ]] ; then
PS1="$RED\u [ $NORMAL\w$RED ]# $NORMAL"
else
PS1="$GREEN\u [ $NORMAL\w$GREEN ]\$ $NORMAL"
fi
for script in /etc/profile.d/*.sh ; do
if [ -r $script ] ; then
. $script
fi
done
unset script RED GREEN NORMAL
# End /etc/profile
EOF
Now create the /etc/profile.d
directory, where the individual initialization scripts are
placed:
install --directory --mode=0755 --owner=root --group=root /etc/profile.d
Using the bash completion script below is controversial. Not all users like it. It adds many (usually over 1000) lines to the bash environment and makes it difficult to use the 'set' command to examine simple environment variables. Omitting this script does not interfere with the ability of bash to use the tab key for file name completion.
This script imports bash completion scripts, installed by many other BLFS packages, to allow TAB command line completion.
cat > /etc/profile.d/bash_completion.sh << "EOF"
# Begin /etc/profile.d/bash_completion.sh
# Import bash completion scripts
# If the bash-completion package is installed, use its configuration instead
if [ -f /usr/share/bash-completion/bash_completion ]; then
# Check for interactive bash and that we haven't already been sourced.
if [ -n "${BASH_VERSION-}" -a -n "${PS1-}" -a -z "${BASH_COMPLETION_VERSINFO-}" ]; then
# Check for recent enough version of bash.
if [ ${BASH_VERSINFO[0]} -gt 4 ] || \
[ ${BASH_VERSINFO[0]} -eq 4 -a ${BASH_VERSINFO[1]} -ge 1 ]; then
[ -r "${XDG_CONFIG_HOME:-$HOME/.config}/bash_completion" ] && \
. "${XDG_CONFIG_HOME:-$HOME/.config}/bash_completion"
if shopt -q progcomp && [ -r /usr/share/bash-completion/bash_completion ]; then
# Source completion code.
. /usr/share/bash-completion/bash_completion
fi
fi
fi
else
# bash-completions are not installed, use only bash completion directory
if shopt -q progcomp; then
for script in /etc/bash_completion.d/* ; do
if [ -r $script ] ; then
. $script
fi
done
fi
fi
# End /etc/profile.d/bash_completion.sh
EOF
Make sure that the directory exists:
install --directory --mode=0755 --owner=root --group=root /etc/bash_completion.d
For a more complete installation, see https://wiki.linuxfromscratch.org/blfs/wiki/bash-shell-startup-files#bash-completions.
This script uses the ~/.dircolors and /etc/dircolors files to control the
colors of file names in a directory listing. They control
colorized output of things like ls --color. The
explanation of how to initialize these files is at the end
of this section.
cat > /etc/profile.d/dircolors.sh << "EOF"
# Setup for /bin/ls and /bin/grep to support color, the alias is in /etc/bashrc.
if [ -f "/etc/dircolors" ] ; then
eval $(dircolors -b /etc/dircolors)
fi
if [ -f "$HOME/.dircolors" ] ; then
eval $(dircolors -b $HOME/.dircolors)
fi
alias ls='ls --color=auto'
alias grep='grep --color=auto'
EOF
This script adds some useful paths to the PATH and can be used to customize other PATH
related environment variables (e.g. LD_LIBRARY_PATH, etc)
that may be needed for all users.
cat > /etc/profile.d/extrapaths.sh << "EOF"
if [ -d /usr/local/lib/pkgconfig ] ; then
pathappend /usr/local/lib/pkgconfig PKG_CONFIG_PATH
fi
if [ -d /usr/local/bin ]; then
pathprepend /usr/local/bin
fi
if [ -d /usr/local/sbin -a $EUID -eq 0 ]; then
pathprepend /usr/local/sbin
fi
# Set some defaults before other applications add to these paths.
pathappend /usr/share/man MANPATH
pathappend /usr/share/info INFOPATH
EOF
This script sets up the default inputrc configuration file. If the user
does not have individual settings, it uses the global file.
cat > /etc/profile.d/readline.sh << "EOF"
# Setup the INPUTRC environment variable.
if [ -z "$INPUTRC" -a ! -f "$HOME/.inputrc" ] ; then
INPUTRC=/etc/inputrc
fi
export INPUTRC
EOF
Setting the umask value is important for security. Here the default group write permissions are turned off for system users and when the user name and group name are not the same.
cat > /etc/profile.d/umask.sh << "EOF"
# By default, the umask should be set.
if [ "$(id -gn)" = "$(id -un)" -a $EUID -gt 99 ] ; then
umask 002
else
umask 022
fi
EOF
This script sets an environment variable necessary for native language support. A full discussion on determining this variable can be found on the LFS Bash Shell Startup Files page.
cat > /etc/profile.d/i18n.sh << "EOF"
# Set up i18n variables
. /etc/locale.conf
export LANG
EOF
Here is a base /etc/bashrc.
Comments in the file should explain everything you need.
cat > /etc/bashrc << "EOF"
# Begin /etc/bashrc
# Written for Beyond Linux From Scratch
# by James Robertson <[email protected]>
# updated by Bruce Dubbs <[email protected]>
# System wide aliases and functions.
# System wide environment variables and startup programs should go into
# /etc/profile. Personal environment variables and startup programs
# should go into ~/.bash_profile. Personal aliases and functions should
# go into ~/.bashrc
# Provides colored /bin/ls and /bin/grep commands. Used in conjunction
# with code in /etc/profile.
alias ls='ls --color=auto'
alias grep='grep --color=auto'
# Provides prompt for non-login shells, specifically shells started
# in the X environment. [Review the LFS archive thread titled
# PS1 Environment Variable for a great case study behind this script
# addendum.]
NORMAL="\[\e[0m\]"
RED="\[\e[1;31m\]"
GREEN="\[\e[1;32m\]"
if [[ $EUID == 0 ]] ; then
PS1="$RED\u [ $NORMAL\w$RED ]# $NORMAL"
else
PS1="$GREEN\u [ $NORMAL\w$GREEN ]\$ $NORMAL"
fi
unset RED GREEN NORMAL
# End /etc/bashrc
EOF
Here is a base ~/.bash_profile.
If you want each new user to have this file automatically,
just change the output of the command to /etc/skel/.bash_profile and check the
permissions after the command is run. You can then copy
/etc/skel/.bash_profile to the
home directories of already existing users, including
root, and set the owner and
group appropriately.
cat > ~/.bash_profile << "EOF"
# Begin ~/.bash_profile
# Written for Beyond Linux From Scratch
# by James Robertson <[email protected]>
# updated by Bruce Dubbs <[email protected]>
# Personal environment variables and startup programs.
# Personal aliases and functions should go in ~/.bashrc. System wide
# environment variables and startup programs are in /etc/profile.
# System wide aliases and functions are in /etc/bashrc.
if [ -f "$HOME/.bashrc" ] ; then
source $HOME/.bashrc
fi
if [ -d "$HOME/bin" ] ; then
pathprepend $HOME/bin
fi
# Having . in the PATH is dangerous
#if [ $EUID -gt 99 ]; then
# pathappend .
#fi
# End ~/.bash_profile
EOF
Here is a base ~/.profile. The
comments and instructions for using /etc/skel for .bash_profile above also apply here. Only
the target file names are different.
cat > ~/.profile << "EOF"
# Begin ~/.profile
# Personal environment variables and startup programs.
if [ -d "$HOME/bin" ] ; then
pathprepend $HOME/bin
fi
# Set up user specific i18n variables
#export LANG=<ll>_<CC>.<charmap><@modifiers>
# End ~/.profile
EOF
Here is a base ~/.bashrc.
cat > ~/.bashrc << "EOF"
# Begin ~/.bashrc
# Written for Beyond Linux From Scratch
# by James Robertson <[email protected]>
# Personal aliases and functions.
# Personal environment variables and startup programs should go in
# ~/.bash_profile. System wide environment variables and startup
# programs are in /etc/profile. System wide aliases and functions are
# in /etc/bashrc.
if [ -f "/etc/bashrc" ] ; then
source /etc/bashrc
fi
# Set up user specific i18n variables
#export LANG=<ll>_<CC>.<charmap><@modifiers>
# End ~/.bashrc
EOF
This is an empty ~/.bash_logout
that can be used as a template. You will notice that the base
~/.bash_logout does not include
a clear
command. This is because the clear is handled in the
/etc/issue file.
cat > ~/.bash_logout << "EOF"
# Begin ~/.bash_logout
# Written for Beyond Linux From Scratch
# by James Robertson <[email protected]>
# Personal items to perform on logout.
# End ~/.bash_logout
EOF
If you want to use the dircolors capability, then run the
following command. The /etc/skel setup steps shown above also can
be used here to provide a ~/.dircolors file when a new user is set
up. As before, just change the output file name on the
following command and assure the permissions, owner, and
group are correct on the files created and/or copied.
dircolors -p > /etc/dircolors
If you wish to customize the colors used for different file
types, you can edit the /etc/dircolors file. The instructions for
setting the colors are embedded in the file.
Finally, Ian Macdonald has written an excellent collection of tips and tricks to enhance your shell environment. You can read it online at http://www.caliban.org/bash/index.shtml.
Last updated on
The LFS book installs Vim as its text editor. At this point it should be noted that there are a lot of different editing applications out there including Emacs, nano, Joe and many more. Anyone who has been around the Internet (especially usenet) for a short time will certainly have observed at least one flame war, usually involving Vim and Emacs users!
The LFS book creates a basic vimrc file. In this section you'll find an
attempt to enhance this file. At startup, vim reads the global
configuration file (/etc/vimrc)
as well as a user-specific file (~/.vimrc). Either or both can be tailored to
suit the needs of your particular system.
Here is a slightly expanded .vimrc that you can put in ~/.vimrc to provide user specific effects. Of
course, if you put it into /etc/skel/.vimrc instead, it will be made
available to users you add to the system later. You can also
copy the file from /etc/skel/.vimrc to the home directory of
users already on the system, such as root. Be sure to set permissions, owner,
and group if you do copy anything directly from /etc/skel.
" Begin .vimrc
set columns=80
set wrapmargin=8
set ruler
" End .vimrc
Note that the comment tags are " instead of the more usual # or
//. This is correct, the syntax for vimrc is slightly unusual.
Below you'll find a quick explanation of what each of the options in this example file means here:
set columns=80: This simply
sets the number of columns used on the screen.
set wrapmargin=8: This is the
number of characters from the right window border where
wrapping starts.
set ruler: This makes
vim show
the current row and column at the bottom right of the
screen.
More information on the many vim options can be found by
reading the help inside vim itself. Do this by typing
:help in vim to get the general help,
or by typing :help
usr_toc.txt to view the User Manual Table of Contents.
Last updated on
When you first boot up your new LFS system, the logon screen
will be nice and plain (as it should be in a bare-bones
system). Many people however, will want their system to display
some information in the logon message. This can be accomplished
using the file /etc/issue.
The /etc/issue file is a plain
text file which will also accept certain escape sequences (see
below) in order to insert information about the system. There
is also the file issue.net which
can be used when logging on remotely. ssh however, will only use it
if you set the option in the configuration file and will
not interpret the escape
sequences shown below.
One of the most common things which people want to do is clear
the screen at each logon. The easiest way of doing that is to
put a "clear" escape sequence into /etc/issue. A simple way of doing this is to
issue the command clear >
/etc/issue. This will insert the relevant
escape code into the start of the /etc/issue file. Note that if you do this,
when you edit the file, you should leave the characters
(normally '^[[H^[[2J') on the first line alone.
Terminal escape sequences are special codes recognized by the terminal. The ^[ represents an ASCII ESC character. The sequence ESC [ H puts the cursor in the upper left hand corner of the screen and ESC 2 J erases the screen. For more information on terminal escape sequences see http://rtfm.etla.org/xterm/ctlseq.html
The following sequences are recognized by agetty (the program which
usually parses /etc/issue). This
information is from man
agetty where you can find extra information
about the logon process.
The issue file can contain
certain character sequences to display various information. All
issue sequences consist of a
backslash (\) immediately followed by one of the letters
explained below (so \d in
/etc/issue would insert the
current date).
b Insert the baudrate of the current line.
d Insert the current date.
s Insert the system name, the name of the operating system.
l Insert the name of the current tty line.
m Insert the architecture identifier of the machine, e.g., i686.
n Insert the nodename of the machine, also known as the hostname.
o Insert the domainname of the machine.
r Insert the release number of the kernel, e.g., 2.6.11.12.
t Insert the current time.
u Insert the number of current users logged in.
U Insert the string "1 user" or "<n> users" where <n> is the
number of current users logged in.
v Insert the version of the OS, e.g., the build-date etc.Last updated on
Security takes many forms in a computing environment. After some initial discussion, this chapter gives examples of three different types of security: access, prevention and detection.
Access for users is usually handled by login or an application designed to handle the login function. In this chapter, we show how to enhance login by setting policies with PAM modules. Access via networks can also be secured by policies set by iptables, commonly referred to as a firewall. The Network Security Services (NSS) and Netscape Portable Runtime (NSPR) libraries can be installed and shared among the many applications requiring them. For applications that don't offer the best security, you can use the Stunnel package to wrap an application daemon inside an SSL tunnel.
Prevention of breaches, like a trojan, are assisted by applications like GnuPG, specifically the ability to confirm signed packages, which recognizes modifications of the tarball after the packager creates it.
Finally, we touch on detection with a package that stores "signatures" of critical files (defined by the administrator) and then regenerates those "signatures" and compares for files that have been changed.
All software has bugs. Sometimes, a bug can be exploited, for example to allow users to gain enhanced privileges (perhaps gaining a root shell, or simply accessing or deleting other user's files), or to allow a remote site to crash an application (denial of service), or for theft of data. These bugs are labelled as vulnerabilities.
The main place where vulnerabilities get logged is cve.mitre.org. Unfortunately, many vulnerability numbers (CVE-yyyy-nnnn) are initially only labelled as "reserved" when distributions start issuing fixes. Also, some vulnerabilities apply to particular combinations of configure options, or only apply to old versions of packages which have long since been updated in BLFS.
BLFS differs from distributions—there is no BLFS security team, and the editors only become aware of vulnerabilities after they are public knowledge. Sometimes, a package with a vulnerability will not be updated in the book for a long time. Issues can be logged in the Trac system, which might speed up resolution.
The normal way for BLFS to fix a vulnerability is, ideally, to update the book to a new fixed release of the package. Sometimes that happens even before the vulnerability is public knowledge, so there is no guarantee that it will be shown as a vulnerability fix in the Changelog. Alternatively, a sed command, or a patch taken from a distribution, may be appropriate.
The bottom line is that you are responsible for your own security, and for assessing the potential impact of any problems.
The editors now issue Security Advisories for packages in BLFS (and LFS), which can be found at BLFS Security Advisories, and grade the severity according to what upstream reports, or to what is shown at nvd.nist.gov if that has details.
To keep track of what is being discovered, you may wish to follow the security announcements of one or more distributions. For example, Debian has Debian security. Fedora's links on security are at the Fedora wiki. Details of Gentoo linux security announcements are discussed at Gentoo security. Finally, the Slackware archives of security announcements are at Slackware security.
The most general English source is perhaps the Full Disclosure Mailing List, but please read the comment on that page. If you use other languages you may prefer other sites such as heise.de (German) or cert.hr (Croatian). These are not linux-specific. There is also a daily update at lwn.net for subscribers (free access to the data after 2 weeks, but their vulnerabilities database at lwn.net/Vulnerabilities is unrestricted).
For some packages, subscribing to their 'announce' lists will provide prompt news of newer versions.
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/vulnerabilities
Last updated on
Public Key Infrastructure (PKI) is a method to validate the authenticity of an otherwise unknown entity across untrusted networks. PKI works by establishing a chain of trust, rather than trusting each individual host or entity explicitly. In order for a certificate presented by a remote entity to be trusted, that certificate must present a complete chain of certificates that can be validated using the root certificate of a Certificate Authority (CA) that is trusted by the local machine.
Establishing trust with a CA involves validating things like company address, ownership, contact information, etc., and ensuring that the CA has followed best practices, such as undergoing periodic security audits by independent investigators and maintaining an always available certificate revocation list. This is well outside the scope of BLFS (as it is for most Linux distributions). The certificate store provided here is taken from the Mozilla Foundation, who have established very strict inclusion policies described here.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://github.com/djlucas/make-ca/releases/download/v1.7/make-ca-1.7.tar.xz
Download size: 28.5 KB
Download MD5 Sum: e0356f5ae5623f227a3f69b5e8848ec6
Estimated disk space required: 6.6 MB (with all runtime deps)
Estimated build time: 0.1 SBU (with all runtime deps)
p11-kit-0.24.0 (required at runtime to generate certificate stores from trust anchors)
NSS-3.69 (to generate a shared NSSDB)
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/make-ca
The make-ca script will
download and process the certificates included in the
certdata.txt file for use as
trust anchors for the p11-kit-0.24.0 trust module.
Additionally, it will generate system certificate stores used
by BLFS applications (if the recommended and optional
applications are present on the system). Any local
certificates stored in /etc/ssl/local will be imported to both the
trust anchors and the generated certificate stores
(overriding Mozilla's trust). Additionally, any modified
trust values will be copied from the trust anchors to
/etc/ssl/local prior to any
updates, preserving custom trust values that differ from
Mozilla when using the trust utility from
p11-kit to operate on the
trust store.
To install the various certificate stores, first install the
make-ca script into the
correct location. As the root
user:
make install && install -vdm755 /etc/ssl/local
As the root user, after
installing p11-kit-0.24.0, download the certificate
source and prepare for system use with the following command:
If running the script a second time with the same version
of certdata.txt, for
instance, to add additional stores as the requisite
software is installed, add the -r switch to the command
line. If packaging, run make-ca --help to see all
available command line options.
/usr/sbin/make-ca -g
You should periodically update the store with the above
command, either manually, or via a systemd timer. A timer is installed at /usr/lib/systemd/system/update-pki.timer
that, if enabled, will check for updates weekly.
Execute the following commands,
as the root user, to
enable the systemd timer:
systemctl enable update-pki.timer
For most users, no additional configuration is necessary,
however, the default certdata.txt file provided by make-ca is
obtained from the mozilla-release branch, and is modified to
provide a Mercurial revision. This will be the correct
version for most systems. There are several other variants of
the file available for use that might be preferred for one
reason or another, including the files shipped with Mozilla
products in this book. RedHat and OpenSUSE, for instance, use
the version included in NSS-3.69. Additional upstream downloads are
available at the links included in /etc/make-ca.conf.dist. Simply copy the
file to /etc/make-ca.conf and
edit as appropriate.
There are three trust types that are recognized by the
make-ca script, SSL/TLS,
S/Mime, and code signing. For OpenSSL, these are serverAuth, emailProtection, and codeSigning respectively. If
one of the three trust arguments is omitted, the certificate
is neither trusted, nor rejected for that role. Clients that
use OpenSSL or NSS encountering this certificate will
present a warning to the user. Clients using GnuTLS without p11-kit support are not aware of trusted
certificates. To include this CA into the ca-bundle.crt, email-ca-bundle.crt, or objsign-ca-bundle.crt files (the
GnuTLS legacy bundles), it
must have the appropriate trust arguments.
The /etc/ssl/local directory is
available to add additional CA certificates to the system.
For instance, you might need to add an organization or
government CA certificate. Files in this directory must be in
the OpenSSL trusted
certificate format. To create an OpenSSL trusted certificate from a
regular PEM encoded file, you need to add trust arguments to
the openssl
command, and create a new certificate. For example, using the
CAcert
roots, if you want to trust both for all three roles, the
following commands will create appropriate OpenSSL trusted
certificates (run as the root
user after Wget-1.21.1 is installed):
wget http://www.cacert.org/certs/root.crt &&
wget http://www.cacert.org/certs/class3.crt &&
openssl x509 -in root.crt -text -fingerprint -setalias "CAcert Class 1 root" \
-addtrust serverAuth -addtrust emailProtection -addtrust codeSigning \
> /etc/ssl/local/CAcert_Class_1_root.pem &&
openssl x509 -in class3.crt -text -fingerprint -setalias "CAcert Class 3 root" \
-addtrust serverAuth -addtrust emailProtection -addtrust codeSigning \
> /etc/ssl/local/CAcert_Class_3_root.pem &&
/usr/sbin/make-ca -r -f
Occasionally, there may be instances where you don't agree
with Mozilla's inclusion of a particular certificate
authority. If you'd like to override the default trust of a
particular CA, simply create a copy of the existing
certificate in /etc/ssl/local
with different trust arguments. For example, if you'd like to
distrust the "Makebelieve_CA_Root" file, run the following
commands:
openssl x509 -in /etc/ssl/certs/Makebelieve_CA_Root.pem \
-text \
-fingerprint \
-setalias "Disabled Makebelieve CA Root" \
-addreject serverAuth \
-addreject emailProtection \
-addreject codeSigning \
> /etc/ssl/local/Disabled_Makebelieve_CA_Root.pem &&
/usr/sbin/make-ca -r -f
Last updated on
The CrackLib package contains a library used to enforce strong passwords by comparing user selected passwords to words in chosen word lists.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://github.com/cracklib/cracklib/releases/download/v2.9.7/cracklib-2.9.7.tar.bz2
Download MD5 sum: 0d68de25332cee5660850528a385427f
Download size: 592 KB
Estimated disk space required: 4.2 MB
Estimated build time: less than 0.1 SBU
Recommended word list for English-speaking countries (size: 6.7 MB; md5sum: 94e9963e4786294f7fb0f2efd7618551): https://github.com/cracklib/cracklib/releases/download/v2.9.7/cracklib-words-2.9.7.bz2
There are additional word lists available for download, e.g., from http://www.cotse.com/tools/wordlists.htm. CrackLib can utilize as many, or as few word lists you choose to install.
Users tend to base their passwords on regular words of the spoken language, and crackers know that. CrackLib is intended to filter out such bad passwords at the source using a dictionary created from word lists. To accomplish this, the word list(s) for use with CrackLib must be an exhaustive list of words and word-based keystroke combinations likely to be chosen by users of the system as (guessable) passwords.
The default word list recommended above for downloading mostly satisfies this role in English-speaking countries. In other situations, it may be necessary to download (or even create) additional word lists.
Note that word lists suitable for spell-checking are not usable as CrackLib word lists in countries with non-Latin based alphabets, because of “word-based keystroke combinations” that make bad passwords.
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/cracklib
Install CrackLib by running the following commands:
sed -i '/skipping/d' util/packer.c &&
PYTHON=python3 CPPFLAGS=-I/usr/include/python3.9 \
./configure --prefix=/usr \
--disable-static \
--with-default-dict=/usr/lib/cracklib/pw_dict &&
make
Now, as the root user:
make install
Issue the following commands as the root user to install the recommended word
list and create the CrackLib
dictionary. Other word lists (text based, one word per line)
can also be used by simply installing them into /usr/share/dict and adding them to the
create-cracklib-dict
command.
install -v -m644 -D ../cracklib-words-2.9.7.bz2 \
/usr/share/dict/cracklib-words.bz2 &&
bunzip2 -v /usr/share/dict/cracklib-words.bz2 &&
ln -v -sf cracklib-words /usr/share/dict/words &&
echo $(hostname) >> /usr/share/dict/cracklib-extra-words &&
install -v -m755 -d /usr/lib/cracklib &&
create-cracklib-dict /usr/share/dict/cracklib-words \
/usr/share/dict/cracklib-extra-words
If desired, check the proper operation of the library as an unprivileged user by issuing the following command:
make test
If you are installing CrackLib after your LFS system has been completed and you have the Shadow package installed, you must reinstall Shadow-4.9 if you wish to provide strong password support on your system. If you are now going to install the Linux-PAM-1.5.1 package, you may disregard this note as Shadow will be reinstalled after the Linux-PAM installation.
sed -i '/skipping/d' util/packer.c: Remove a meaningless warning.
PYTHON=python3: This forces the
installation of python bindings for Python 3, even if Python
2 is installed.
CPPFLAGS=-I/usr/include/python3.9:
This works around an issue caused by incorrect usage of
Python 3 headers.
--with-default-dict=/lib/cracklib/pw_dict:
This parameter forces the installation of the CrackLib dictionary to the /lib hierarchy.
--disable-static:
This switch prevents installation of static versions of the
libraries.
install -v -m644 -D
...: This command creates the /usr/share/dict directory (if it doesn't
already exist) and installs the compressed word list there.
ln -v -s cracklib-words
/usr/share/dict/words: The word list is
linked to /usr/share/dict/words
as historically, words is the
primary word list in the /usr/share/dict directory. Omit this
command if you already have a /usr/share/dict/words file installed on
your system.
echo $(hostname)
>>...: The value of hostname is echoed to a
file called cracklib-extra-words. This extra file is
intended to be a site specific list which includes easy to
guess passwords such as company or department names, user
names, product names, computer names, domain names, etc.
create-cracklib-dict ...: This command creates the CrackLib dictionary from the word lists. Modify the command to add any additional word lists you have installed.
|
is used to determine if a password is strong |
|
|
is used to format text files (lowercases all words, removes control characters and sorts the lists) |
|
|
creates a database with words read from standard input |
|
|
displays on standard output the database specified |
|
|
is used to create the CrackLib dictionary from the given word list(s) |
|
|
provides a fast dictionary lookup method for strong password enforcement |
Last updated on
cryptsetup is used to set up transparent encryption of block devices using the kernel crypto API.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://www.kernel.org/pub/linux/utils/cryptsetup/v2.3/cryptsetup-2.3.6.tar.xz
Download MD5 sum: 504d1ab22cbc4d1a59a8d8c7ee5ed3bf
Download size: 11 MB
Estimated disk space required: 29 MB (add 113 MB for tests)
Estimated build time: 0.2 SBU (add 14 SBU for tests)
JSON-C-0.15, LVM2-2.03.13, and popt-1.18
libpwquality-1.4.4, argon2, and passwdqc
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/cryptsetup
Encrypted block devices require kernel support. To use it, the appropriate kernel configuration parameters need to be set:
Device Drivers --->
[*] Multiple devices driver support (RAID and LVM) ---> [CONFIG_MD]
<*/M> Device mapper support [CONFIG_BLK_DEV_DM]
<*/M> Crypt target support [CONFIG_DM_CRYPT]
Cryptographic API --->
<*/M> XTS support [CONFIG_CRYPTO_XTS]
<*/M> SHA224 and SHA256 digest algorithm [CONFIG_CRYPTO_SHA256]
<*/M> AES cipher algorithms [CONFIG_CRYPTO_AES]
<*/M> User-space interface for symmetric key cipher algorithms
[CONFIG_CRYPTO_USER_API_SKCIPHER]
For tests:
<*/M> Twofish cipher algorithm [CONFIG_CRYPTO_TWOFISH]Install cryptsetup by running the following commands:
./configure --prefix=/usr && make
To test the result, issue as the root user: make check. Some tests will
fail if appropriate kernel configuration options are not set.
Some additional options that may be needed for tests are:
CONFIG_SCSI_LOWLEVEL, CONFIG_SCSI_DEBUG,
CONFIG_BLK_DEV_DM_BUILTIN, CONFIG_CRYPTO_USER,
CONFIG_CRYPTO_CRYPTD, CONFIG_CRYPTO_LRW, CONFIG_CRYPTO_XTS,
CONFIG_CRYPTO_ESSIV, CONFIG_CRYPTO_CRCT10DIF,
CONFIG_CRYPTO_AES_TI, CONFIG_CRYPTO_AES_NI_INTEL,
CONFIG_CRYPTO_BLOWFISH, CONFIG_CRYPTO_CAST5,
CONFIG_CRYPTO_SERPENT, CONFIG_CRYPTO_SERPENT_SSE2_X86_64,
CONFIG_CRYPTO_SERPENT_AVX_X86_64,
CONFIG_CRYPTO_SERPENT_AVX2_X86_64, and
CONFIG_CRYPTO_TWOFISH_X86_64.
Now, as the root user:
make install
Because of the number of possible configurations, setup of encrypted volumes is beyond the scope of the BLFS book. Please see the configuration guide in the cryptsetup FAQ.
|
is used to setup dm-crypt managed device-mapper mappings |
|
|
is a tool for offline LUKS device re-encryption |
|
|
is a tool to manage dm-integrity (block level integrity) volumes |
|
|
is used to configure dm-verity managed device-mapper mappings. Device-mapper verity target provides read-only transparent integrity checking of block devices using kernel crypto API |
Last updated on
The Cyrus SASL package contains a Simple Authentication and Security Layer, a method for adding authentication support to connection-based protocols. To use SASL, a protocol includes a command for identifying and authenticating a user to a server and for optionally negotiating protection of subsequent protocol interactions. If its use is negotiated, a security layer is inserted between the protocol and the connection.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://github.com/cyrusimap/cyrus-sasl/releases/download/cyrus-sasl-2.1.27/cyrus-sasl-2.1.27.tar.gz
Download MD5 sum: a33820c66e0622222c5aefafa1581083
Download size: 3.9 MB
Estimated disk space required: 26 MB
Estimated build time: 0.1 SBU
Linux-PAM-1.5.1, MIT Kerberos V5-1.19.2, MariaDB-10.6.4 or MySQL, OpenJDK-16.0.2, OpenLDAP-2.5.7, PostgreSQL-13.4, SQLite-3.36.0, krb4, Dmalloc, Pod::POM::View::Restructured, and Sphinx
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/cyrus-sasl
This package does not support parallel build.
First, fix a build failure if Sphinx or docutils-0.17.1 is installed on the system:
patch -Np1 -i ../cyrus-sasl-2.1.27-doc_fixes-1.patch
Install Cyrus SASL by running the following commands:
./configure --prefix=/usr \
--sysconfdir=/etc \
--enable-auth-sasldb \
--with-dbpath=/var/lib/sasl/sasldb2 \
--with-sphinx-build=no \
--with-saslauthd=/var/run/saslauthd &&
make -j1
This package does not come with a test suite. If you are planning on using the GSSAPI authentication mechanism, test it after installing the package using the sample server and client programs which were built in the preceding step. Instructions for performing the tests can be found at https://www.linuxfromscratch.org/hints/downloads/files/cyrus-sasl.txt.
Now, as the root user:
make install && install -v -dm755 /usr/share/doc/cyrus-sasl-2.1.27/html && install -v -m644 saslauthd/LDAP_SASLAUTHD /usr/share/doc/cyrus-sasl-2.1.27 && install -v -m644 doc/legacy/*.html /usr/share/doc/cyrus-sasl-2.1.27/html && install -v -dm700 /var/lib/sasl
--with-dbpath=/var/lib/sasl/sasldb2:
This switch forces the sasldb database to be
created in /var/lib/sasl
instead of /etc.
--with-saslauthd=/var/run/saslauthd:
This switch forces saslauthd to use the FHS
compliant directory /var/run/saslauthd for variable run-time
data.
--enable-auth-sasldb:
This switch enables SASLDB authentication backend.
--with-dblib=gdbm: This switch
forces GDBM to be used
instead of Berkeley DB.
--with-ldap: This switch enables
the OpenLDAP support.
--enable-ldapdb: This switch
enables the LDAPDB authentication backend. There is a
circular dependency with this parameter. See https://wiki.linuxfromscratch.org/blfs/wiki/cyrus-sasl
for a solution to this problem.
--enable-java: This switch
enables compiling of the Java support libraries.
--enable-login: This option
enables unsupported LOGIN authentication.
--enable-ntlm: This option
enables unsupported NTLM authentication.
install -v -m644 ...: These commands install documentation which is not installed by the make install command.
install -v -m700 -d /var/lib/sasl: This directory must exist when starting saslauthd or using the sasldb plugin. If you're not going to be running the daemon or using the plugins, you may omit the creation of this directory.
/etc/saslauthd.conf (for
saslauthd
LDAP configuration) and /etc/sasl2/Appname.conf (where "Appname"
is the application defined name of the application)
See https://www.cyrusimap.org/sasl/sasl/sysadmin.html for information on what to include in the application configuration files.
See file:///usr/share/doc/cyrus-sasl-2.1.27/LDAP_SASLAUTHD for configuring saslauthd with OpenLDAP.
See https://www.cyrusimap.org/sasl/sasl/gssapi.html#gssapi for configuring saslauthd with Kerberos.
If you need to run the saslauthd daemon at
system startup, install the saslauthd.service unit included in the
blfs-systemd-units-20210819
package using the following command:
make install-saslauthd
You'll need to modify /etc/default/saslauthd and modify the
MECHANISM parameter with your
desired authentication mechanism. The default authentication mechanism is
"shadow".
|
is used to list loadable SASL plugins and their properties |
|
|
is the SASL authentication server |
|
|
is used to list the users in the SASL password
database |
|
|
is used to set and delete a user's SASL password
and mechanism specific secrets in the SASL password
database |
|
|
is a test utility for the SASL authentication server |
|
|
is a general purpose authentication library for server and client applications |
Last updated on
The GnuPG package is GNU's tool for secure communication and data storage. It can be used to encrypt data and to create digital signatures. It includes an advanced key management facility and is compliant with the proposed OpenPGP Internet standard as described in RFC2440 and the S/MIME standard as described by several RFCs. GnuPG 2 is the stable version of GnuPG integrating support for OpenPGP and S/MIME.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://www.gnupg.org/ftp/gcrypt/gnupg/gnupg-2.2.29.tar.bz2
Download (FTP): ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-2.2.29.tar.bz2
Download MD5 sum: 5db3334b528cf756b1e583db01319a24
Download size: 6.9 MB
Estimated disk space required: 143 MB (with all tests; add 25 MB for docs)
Estimated build time: 0.4 SBU (using parallelism=4; add 1.5 SBU for tests)
Libassuan-2.5.5, libgcrypt-1.9.4, Libksba-1.6.0, and npth-1.6
GnuTLS-3.7.2 (required to communicate with keyservers using https or hkps protocol) and pinentry-1.2.0 (Run-time requirement for most of the package's functionality)
cURL-7.78.0, Fuse-3.10.4, ImageMagick-7.1.0-4 (for the convert utility, used for generating the documentation), libusb-1.0.24, an MTA, OpenLDAP-2.5.7, SQLite-3.36.0, texlive-20210325 (or install-tl-unx), fig2dev (for generating documentation), and GNU adns
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/gnupg2
By default GnuPG doesn't install the deprecated gpg-zip script, but it is still needed by some programs. Make GnuPG install it with:
sed -e '/noinst_SCRIPTS = gpg-zip/c sbin_SCRIPTS += gpg-zip' \
-i tools/Makefile.in
Install GnuPG by running the following commands:
./configure --prefix=/usr \
--localstatedir=/var \
--sysconfdir=/etc \
--docdir=/usr/share/doc/gnupg-2.2.29 &&
make &&
makeinfo --html --no-split -o doc/gnupg_nochunks.html doc/gnupg.texi &&
makeinfo --plaintext -o doc/gnupg.txt doc/gnupg.texi &&
make -C doc html
If you have texlive-20210325 installed and you wish to create documentation in alternate formats, issue the following commands (fig2dev is needed for the ps format):
make -C doc pdf ps
To test the results, issue: make check.
Note that if you have already installed GnuPG, the instructions below will
overwrite /usr/share/man/man1/gpg-zip.1. Now, as the
root user:
make install &&
install -v -m755 -d /usr/share/doc/gnupg-2.2.29/html &&
install -v -m644 doc/gnupg_nochunks.html \
/usr/share/doc/gnupg-2.2.29/html/gnupg.html &&
install -v -m644 doc/*.texi doc/gnupg.txt \
/usr/share/doc/gnupg-2.2.29 &&
install -v -m644 doc/gnupg.html/* \
/usr/share/doc/gnupg-2.2.29/html
If you created alternate formats of the documentation,
install them using the following command as the root user:
install -v -m644 doc/gnupg.{pdf,dvi,ps} \
/usr/share/doc/gnupg-2.2.29
sed ... tools/Makefile.in: This command is needed to build the gpg-zip program.
--docdir=/usr/share/doc/gnupg-2.2.29:
This switch changes the default docdir to /usr/share/doc/gnupg-2.2.29.
--enable-all-tests: This switch
allows more tests to be run with make check.
--enable-g13: This switch enables
building the g13 program.
|
is used to create and populate a user's
|
|
|
is a wrapper script used to run gpgconf with the
|
|
|
is a tool that takes care of accessing the OpenPGP keyservers |
|
|
is a tool to contact a running dirmngr and test whether a certificate has been revoked |
|
|
is a tool to create, mount or unmount an encrypted file system container (optional) |
|
|
is a daemon used to manage secret (private) keys independently from any protocol. It is used as a backend for gpg and gpgsm as well as for a couple of other utilities |
|
|
is a utility used to communicate with a running gpg-agent |
|
|
is the OpenPGP part of the GNU Privacy Guard (GnuPG). It is a tool used to provide digital encryption and signing services using the OpenPGP standard |
|
|
is a utility used to automatically and reasonably
safely query and modify configuration files in the
|
|
|
is a utility currently only useful for debugging.
Run it with |
|
|
executes the given scheme program or spawns an interactive shell |
|
|
is a tool similar to gpg used to provide digital encryption and signing services on X.509 certificates and the CMS protocol. It is mainly used as a backend for S/MIME mail processing |
|
|
splits an OpenPGP message into packets |
|
|
is a tool to encrypt or sign files into an archive |
|
|
is a verify only version of gpg |
|
|
provides a server for the Web Key Service protocol |
|
|
encrypts or signs files into an archive |
|
|
is used to list, export and import Keybox data |
|
|
is used to listen to a Unix Domain socket created by any of the GnuPG tools |
Last updated on
The GnuTLS package contains libraries and userspace tools which provide a secure layer over a reliable transport layer. Currently the GnuTLS library implements the proposed standards by the IETF's TLS working group. Quoting from the TLS protocol specification:
“The TLS protocol provides communications privacy over the Internet. The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery.”
GnuTLS provides support for TLS 1.3, TLS 1.2, TLS 1.1, TLS 1.0, and SSL 3.0 protocols, TLS extensions, including server name and max record size. Additionally, the library supports authentication using the SRP protocol, X.509 certificates and OpenPGP keys, along with support for the TLS Pre-Shared-Keys (PSK) extension, the Inner Application (TLS/IA) extension and X.509 and OpenPGP certificate handling.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://www.gnupg.org/ftp/gcrypt/gnutls/v3.7/gnutls-3.7.2.tar.xz
Download (FTP): ftp://ftp.gnupg.org/gcrypt/gnutls/v3.7/gnutls-3.7.2.tar.xz
Download MD5 sum: 95c32a1af583ecfcb280648874c0fbd9
Download size: 5.8 MB
Estimated disk space required: 139 MB (add 112 MB for tests)
Estimated build time: 0.9 SBU (add 2.9 SBU for tests; both using parallelism=4)
make-ca-1.7, libunistring-0.9.10, libtasn1-4.17.0, and p11-kit-0.24.0
Doxygen-1.9.2, GTK-Doc-1.33.2, Guile-3.0.7, libidn-1.38 or libidn2-2.3.2, libseccomp-2.5.1, Net-tools-2.10 (used during the test suite), texlive-20210325 or install-tl-unx, Unbound-1.13.2 (to build the DANE library), Valgrind-3.17.0 (used during the test suite), autogen, cmocka and datefudge (used during the test suite if the DANE library is built), and Trousers (Trusted Platform Module support)
Note that if you do not install libtasn1-4.17.0, an older version shipped in the GnuTLS tarball will be used instead.
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/gnutls
Install GnuTLS by running the following commands:
./configure --prefix=/usr \
--docdir=/usr/share/doc/gnutls-3.7.2 \
--disable-guile \
--disable-rpath \
--with-default-trust-store-pkcs11="pkcs11:" &&
make
To test the results, issue: make check.
Now, as the root user:
make install
If you passed --enable-gtk-doc to
the configure
script, the API will automatically be installed. Otherwise,
if desired, you can still install the API documentation to
the /usr/share/gtk-doc/html/gnutls directory
using the following command as the root user:
make -C doc/reference install-data-local
--with-default-trust-store-pkcs11="pkcs11:":
This switch tells gnutls to use the PKCS #11 trust store as
the default trust. Omit this switch if p11-kit-0.24.0 is not
installed.
--disable-guile: This
switch disables GUILE support, since GnuTLS does not support
Guile-2.2.x yet.
--disable-rpath: This
switch prevents building GnuTLS utilities and tests with
hardcoded runtime library search path. Hardcoded rpath is
unneeded for BLFS, and it causes test failures if an old
version of GnuTLS is installed.
--with-default-trust-store-file=/etc/pki/tls/certs/ca-bundle.crt:
This switch tells configure where to find the
legacy CA certificate bundle and to use it instead of PKCS
#11 module by default. Use this if p11-kit-0.24.0 is not
installed.
--enable-gtk-doc: Use this
parameter if GTK-Doc is
installed and you wish to rebuild and install the API
documentation.
--enable-openssl-compatibility:
Use this switch if you wish to build the OpenSSL
compatibility library.
--without-p11-kit: use this
switch if you have not installed p11-kit.
--with-included-unistring: uses
the bundled version of libunistring, instead of the system
one. Use this switch if you have not installed libunistring-0.9.10.
|
is used to generate X.509 certificates, certificate requests, and private keys |
|
|
is a tool used to generate and check DNS resource records for the DANE protocol |
|
|
is a simple client program to set up a TLS connection to some other computer |
|
|
is a simple client program to set up a TLS connection to some other computer and produces very verbose progress results |
|
|
is a simple server program that listens to incoming TLS connections |
|
|
is a program that can parse and print information about OCSP requests/responses, generate requests and verify responses |
|
|
is a program that allows handling data from PKCS #11 smart cards and security modules |
|
|
is a simple program that generates random keys for use with TLS-PSK |
|
|
is a simple program that emulates the programs in the Stanford SRP (Secure Remote Password) libraries using GnuTLS |
|
|
contains the core API functions and X.509 certificate API functions |
Last updated on
The GPGME package is a C library that allows cryptography support to be added to a program. It is designed to make access to public key crypto engines like GnuPG or GpgSM easier for applications. GPGME provides a high-level crypto API for encryption, decryption, signing, signature verification and key management.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://www.gnupg.org/ftp/gcrypt/gpgme/gpgme-1.16.0.tar.bz2
Download (FTP): ftp://ftp.gnupg.org/gcrypt/gpgme/gpgme-1.16.0.tar.bz2
Download MD5 sum: e31b9e0efc5a2e1ec1bbed22e7a082a4
Download size: 1.6 MB
Estimated disk space required: 222 MB
Estimated build time: 0.8 SBU (with parallelism=4; with all bindings, add 0.7 SBU for tests)
Doxygen-1.9.2 and Graphviz-2.48.0 (for API documentation), GnuPG-2.2.29 (required if Qt or SWIG are installed; used during the testsuite), Clisp-2.49, Qt-5.15.2, and/or SWIG-4.0.2 (for language bindings)
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/gpgme
At first, fix an issue building the package with Glibc-2.34 or later:
sed 's/defined(__sun.*$/1/' -i src/posix-io.c
Install GPGME by running the following commands:
./configure --prefix=/usr --disable-gpg-test && make
To test the results, you should have GnuPG-2.2.29 installed and remove the --disable-gpg-test above. Issue: make -k check.
Now, as the root user:
make install
--disable-gpg-test:
if this parameter is not passed to configure, the test
programs are built during make stage, which requires
GnuPG-2.2.29. This parameter is not needed
if GnuPG-2.2.29 is installed.
|
is used to obtain GPGME compilation and linking information |
|
|
outputs GPGME commands in JSON format |
|
|
is an assuan server exposing GPGME operations, such as printing fingerprints and keyids with keyservers |
|
|
contains the GPGME API functions |
|
|
contains the C++ GPGME API functions |
|
|
contains API functions for handling GPG operations in Qt applications |
Last updated on
The Haveged package contains a daemon that generates an unpredictable stream of random numbers and feeds the /dev/random device.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://github.com/jirka-h/haveged/archive/v1.9.14/haveged-1.9.14.tar.gz
Download MD5 sum: f756474201bec9a46b41e8712f79468a
Download size: 488 KB
Estimated disk space required: 21 MB (with tests)
Estimated build time: 0.1 SBU (with tests)
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/haveged
Install Haveged by running the following commands:
./configure --prefix=/usr --disable-static && make
To test the results, issue: make check.
Now, as the root user:
make install && mkdir -pv /usr/share/doc/haveged-1.9.14 && cp -v README /usr/share/doc/haveged-1.9.14
If you want the Haveged
daemon to start automatically when the system is booted,
install the haveged.service
unit included in the blfs-systemd-units-20210819
package (as the root user):
make install-haveged
Last updated on
iptables is a userspace command line program used to configure the Linux 2.4 and later kernel packet filtering ruleset.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): http://www.netfilter.org/projects/iptables/files/iptables-1.8.7.tar.bz2
Download (FTP): ftp://ftp.netfilter.org/pub/iptables/iptables-1.8.7.tar.bz2
Download MD5 sum: 602ba7e937c72fbb7b1c2b71c3b0004b
Download size: 704 KB
Estimated disk space required: 22 MB
Estimated build time: 0.1 SBU
libpcap-1.10.1 (required for nfsypproxy support), bpf-utils (required for Berkeley Packet Filter support), libnfnetlink (required for connlabel support), libnetfilter_conntrack (required for connlabel support), and nftables
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/iptables
A firewall in Linux is accomplished through the netfilter interface. To use iptables to configure netfilter, the following kernel configuration parameters are required:
[*] Networking support ---> [CONFIG_NET]
Networking Options --->
[*] Network packet filtering framework (Netfilter) ---> [CONFIG_NETFILTER]
[*] Advanced netfilter configuration [CONFIG_NETFILTER_ADVANCED]
Core Netfilter Configuration --->
<*/M> Netfilter connection tracking support [CONFIG_NF_CONNTRACK]
<*/M> Netfilter Xtables support (required for ip_tables) [CONFIG_NETFILTER_XTABLES]
<*/M> LOG target support [CONFIG_NETFILTER_XT_TARGET_LOG]
IP: Netfilter Configuration --->
<*/M> IP tables support (required for filtering/masq/NAT) [CONFIG_IP_NF_IPTABLES]Include any connection tracking protocols that will be used, as well as any protocols that you wish to use for match support under the "Core Netfilter Configuration" section. The above options are enough for running Creating a Personal Firewall With iptables below.
The installation below does not include building some
specialized extension libraries which require the raw
headers in the Linux
source code. If you wish to build the additional extensions
(if you aren't sure, then you probably don't), you can look
at the INSTALL file to see an
example of how to change the KERNEL_DIR= parameter to
point at the Linux source
code. Note that if you upgrade the kernel version, you may
also need to recompile iptables and that the BLFS team has
not tested using the raw kernel headers.
Install iptables by running the following commands:
./configure --prefix=/usr \
--disable-nftables \
--enable-libipq &&
make
This package does not come with a test suite.
Now, as the root user:
make install
--disable-nftables:
This switch disables building nftables compatibility.
--enable-libipq: This
switch enables building of libipq.so which can be used by some
packages outside of BLFS.
--enable-nfsynproxy: This switch
enables installation of nfsynproxy SYNPROXY configuration tool.
In the following example configurations, LAN1 is used for the internal LAN interface, and WAN1 is used for the external interace connected to the Internet. You will need to replace these values with appropriate interface names for your system.
A Personal Firewall is designed to let you access all the services offered on the Internet while keeping your computer secure and your data private.
Below is a slightly modified version of Rusty Russell's recommendation from the Linux 2.4 Packet Filtering HOWTO. It is still applicable to the Linux 5.x kernels.
install -v -dm755 /etc/systemd/scripts
cat > /etc/systemd/scripts/iptables << "EOF"
#!/bin/sh
# Begin /etc/systemd/scripts/iptables
# Insert connection-tracking modules
# (not needed if built into the kernel)
modprobe nf_conntrack
modprobe xt_LOG
# Enable broadcast echo Protection
echo 1 > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts
# Disable Source Routed Packets
echo 0 > /proc/sys/net/ipv4/conf/all/accept_source_route
echo 0 > /proc/sys/net/ipv4/conf/default/accept_source_route
# Enable TCP SYN Cookie Protection
echo 1 > /proc/sys/net/ipv4/tcp_syncookies
# Disable ICMP Redirect Acceptance
echo 0 > /proc/sys/net/ipv4/conf/default/accept_redirects
# Do not send Redirect Messages
echo 0 > /proc/sys/net/ipv4/conf/all/send_redirects
echo 0 > /proc/sys/net/ipv4/conf/default/send_redirects
# Drop Spoofed Packets coming in on an interface, where responses
# would result in the reply going out a different interface.
echo 1 > /proc/sys/net/ipv4/conf/all/rp_filter
echo 1 > /proc/sys/net/ipv4/conf/default/rp_filter
# Log packets with impossible addresses.
echo 1 > /proc/sys/net/ipv4/conf/all/log_martians
echo 1 > /proc/sys/net/ipv4/conf/default/log_martians
# be verbose on dynamic ip-addresses (not needed in case of static IP)
echo 2 > /proc/sys/net/ipv4/ip_dynaddr
# disable Explicit Congestion Notification
# too many routers are still ignorant
echo 0 > /proc/sys/net/ipv4/tcp_ecn
# Set a known state
iptables -P INPUT DROP
iptables -P FORWARD DROP
iptables -P OUTPUT DROP
# These lines are here in case rules are already in place and the
# script is ever rerun on the fly. We want to remove all rules and
# pre-existing user defined chains before we implement new rules.
iptables -F
iptables -X
iptables -Z
iptables -t nat -F
# Allow local-only connections
iptables -A INPUT -i lo -j ACCEPT
# Free output on any interface to any ip for any service
# (equal to -P ACCEPT)
iptables -A OUTPUT -j ACCEPT
# Permit answers on already established connections
# and permit new connections related to established ones
# (e.g. port mode ftp)
iptables -A INPUT -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT
# Log everything else.
iptables -A INPUT -j LOG --log-prefix "FIREWALL:INPUT "
# End /etc/systemd/scripts/iptables
EOF
chmod 700 /etc/systemd/scripts/iptables
This script is quite simple, it drops all traffic coming into your computer that wasn't initiated from your computer, but as long as you are simply surfing the Internet you are unlikely to exceed its limits.
If you frequently encounter certain delays at accessing FTP servers, take a look at BusyBox with iptables example number 4.
Even if you have daemons or services running on your system, these will be inaccessible everywhere but from your computer itself. If you want to allow access to services on your machine, such as ssh or ping, take a look at Creating a BusyBox With iptables.
A Network Firewall has two interfaces, one connected to an intranet, in this example LAN1, and one connected to the Internet, here WAN1. To provide the maximum security for the firewall itself, make sure that there are no unnecessary servers running on it such as X11. As a general principle, the firewall itself should not access any untrusted service (think of a remote server giving answers that makes a daemon on your system crash, or even worse, that implements a worm via a buffer-overflow).
install -v -dm755 /etc/systemd/scripts
cat > /etc/systemd/scripts/iptables << "EOF"
#!/bin/sh
# Begin /etc/systemd/scripts/iptables
echo
echo "You're using the example configuration for a setup of a firewall"
echo "from Beyond Linux From Scratch."
echo "This example is far from being complete, it is only meant"
echo "to be a reference."
echo "Firewall security is a complex issue, that exceeds the scope"
echo "of the configuration rules below."
echo "You can find additional information"
echo "about firewalls in Chapter 4 of the BLFS book."
echo "http://www.linuxfromscratch.org/blfs"
echo
# Insert iptables modules (not needed if built into the kernel).
modprobe nf_conntrack
modprobe nf_conntrack_ftp
modprobe xt_conntrack
modprobe xt_LOG
modprobe xt_state
# Enable broadcast echo Protection
echo 1 > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts
# Disable Source Routed Packets
echo 0 > /proc/sys/net/ipv4/conf/all/accept_source_route
# Enable TCP SYN Cookie Protection
echo 1 > /proc/sys/net/ipv4/tcp_syncookies
# Disable ICMP Redirect Acceptance
echo 0 > /proc/sys/net/ipv4/conf/all/accept_redirects
# Don't send Redirect Messages
echo 0 > /proc/sys/net/ipv4/conf/default/send_redirects
# Drop Spoofed Packets coming in on an interface where responses
# would result in the reply going out a different interface.
echo 1 > /proc/sys/net/ipv4/conf/default/rp_filter
# Log packets with impossible addresses.
echo 1 > /proc/sys/net/ipv4/conf/all/log_martians
# Be verbose on dynamic ip-addresses (not needed in case of static IP)
echo 2 > /proc/sys/net/ipv4/ip_dynaddr
# Disable Explicit Congestion Notification
# Too many routers are still ignorant
echo 0 > /proc/sys/net/ipv4/tcp_ecn
# Set a known state
iptables -P INPUT DROP
iptables -P FORWARD DROP
iptables -P OUTPUT DROP
# These lines are here in case rules are already in place and the
# script is ever rerun on the fly. We want to remove all rules and
# pre-existing user defined chains before we implement new rules.
iptables -F
iptables -X
iptables -Z
iptables -t nat -F
# Allow local connections
iptables -A INPUT -i lo -j ACCEPT
iptables -A OUTPUT -o lo -j ACCEPT
# Allow forwarding if the initiated on the intranet
iptables -A FORWARD -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT
iptables -A FORWARD ! -i WAN1 -m conntrack --ctstate NEW -j ACCEPT
# Do masquerading
# (not needed if intranet is not using private ip-addresses)
iptables -t nat -A POSTROUTING -o WAN1 -j MASQUERADE
# Log everything for debugging
# (last of all rules, but before policy rules)
iptables -A INPUT -j LOG --log-prefix "FIREWALL:INPUT "
iptables -A FORWARD -j LOG --log-prefix "FIREWALL:FORWARD "
iptables -A OUTPUT -j LOG --log-prefix "FIREWALL:OUTPUT "
# Enable IP Forwarding
echo 1 > /proc/sys/net/ipv4/ip_forward
# The following sections allow inbound packets for specific examples
# Uncomment the example lines and adjust as necessary
# Allow ping on the external interface
#iptables -A INPUT -p icmp -m icmp --icmp-type echo-request -j ACCEPT
#iptables -A OUTPUT -p icmp -m icmp --icmp-type echo-reply -j ACCEPT
# Reject ident packets with TCP reset to avoid delays with FTP or IRC
#iptables -A INPUT -p tcp --dport 113 -j REJECT --reject-with tcp-reset
# Allow HTTP and HTTPS to 192.168.0.2
#iptables -A PREROUTING -t nat -i WAN1 -p tcp --dport 80 -j DNAT --to 192.168.0.2
#iptables -A PREROUTING -t nat -i WAN1 -p tcp --dport 443 -j DNAT --to 192.168.0.2
#iptables -A FORWARD -p tcp -d 192.168.0.2 --dport 80 -j ACCEPT
#iptables -A FORWARD -p tcp -d 192.168.0.2 --dport 443 -j ACCEPT
# End /etc/systemd/scripts/iptables
EOF
chmod 700 /etc/systemd/scripts/iptables
With this script your intranet should be reasonably secure against external attacks. No one should be able to setup a new connection to any internal service and, if it's masqueraded, makes your intranet invisible to the Internet. Furthermore, your firewall should be relatively safe because there are no services running that a cracker could attack.
This scenario isn't too different from the Creating a Masquerading Router With iptables, but additionally offers some services to your intranet. Examples of this can be when you want to administer your firewall from another host on your intranet or use it as a proxy or a name server.
Outlining specifically how to protect a server that offers services on the Internet goes far beyond the scope of this document. See the references in the section called “Extra Information” for more information.
Be cautious. Every service you have enabled makes your setup more complex and your firewall less secure. You are exposed to the risks of misconfigured services or running a service with an exploitable bug. A firewall should generally not run any extra services. See the introduction to the Creating a Masquerading Router With iptables for some more details.
If you want to add services such as internal Samba or name servers that do not need to access the Internet themselves, the additional statements are quite simple and should still be acceptable from a security standpoint. Just add the following lines into the script before the logging rules.
iptables -A INPUT -i ! WAN1 -j ACCEPT
iptables -A OUTPUT -o ! WAN1 -j ACCEPTIf daemons, such as squid, have to access the Internet themselves, you could open OUTPUT generally and restrict INPUT.
iptables -A INPUT -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT
iptables -A OUTPUT -j ACCEPTHowever, it is generally not advisable to leave OUTPUT unrestricted. You lose any control over trojans who would like to "call home", and a bit of redundancy in case you've (mis-)configured a service so that it broadcasts its existence to the world.
To accomplish this, you should restrict INPUT and OUTPUT on all ports except those that it's absolutely necessary to have open. Which ports you have to open depends on your needs: mostly you will find them by looking for failed accesses in your log files.
Have a Look at the Following Examples:
Squid is caching the web:
iptables -A OUTPUT -p tcp --dport 80 -j ACCEPT
iptables -A INPUT -p tcp --sport 80 -m conntrack --ctstate ESTABLISHED \
-j ACCEPTYour caching name server (e.g., named) does its lookups via UDP:
iptables -A OUTPUT -p udp --dport 53 -j ACCEPTYou want to be able to ping your computer to ensure it's still alive:
iptables -A INPUT -p icmp -m icmp --icmp-type echo-request -j ACCEPT
iptables -A OUTPUT -p icmp -m icmp --icmp-type echo-reply -j ACCEPTIf you are frequently accessing FTP servers or enjoy chatting, you might notice delays because some implementations of these daemons query an identd daemon on your system to obtain usernames. Although there's really little harm in this, having an identd running is not recommended because many security experts feel the service gives out too much additional information.
To avoid these delays you could reject the requests with a 'tcp-reset' response:
iptables -A INPUT -p tcp --dport 113 -j REJECT --reject-with tcp-resetTo log and drop invalid packets (packets that came in after netfilter's timeout or some types of network scans) insert these rules at the top of the chain:
iptables -I INPUT 0 -p tcp -m conntrack --ctstate INVALID \
-j LOG --log-prefix "FIREWALL:INVALID "
iptables -I INPUT 1 -p tcp -m conntrack --ctstate INVALID -j DROPAnything coming from the outside should not have a private address, this is a common attack called IP-spoofing:
iptables -A INPUT -i WAN1 -s 10.0.0.0/8 -j DROP
iptables -A INPUT -i WAN1 -s 172.16.0.0/12 -j DROP
iptables -A INPUT -i WAN1 -s 192.168.0.0/16 -j DROPThere are other addresses that you may also want to drop: 0.0.0.0/8, 127.0.0.0/8, 224.0.0.0/3 (multicast and experimental), 169.254.0.0/16 (Link Local Networks), and 192.0.2.0/24 (IANA defined test network).
If your firewall is a DHCP client, you need to allow those packets:
iptables -A INPUT -i WAN1 -p udp -s 0.0.0.0 --sport 67 \
-d 255.255.255.255 --dport 68 -j ACCEPTTo simplify debugging and be fair to anyone who'd like to access a service you have disabled, purposely or by mistake, you could REJECT those packets that are dropped.
Obviously this must be done directly after logging as the very last lines before the packets are dropped by policy:
iptables -A INPUT -j REJECT
These are only examples to show you some of the
capabilities of the firewall code in Linux. Have a look at
the man page of iptables. There you will find much more
information. The port numbers needed for this can be found
in /etc/services, in case you
didn't find them by trial and error in your log file.
To set up the iptables firewall at boot, install the
iptables.service unit
included in the blfs-systemd-units-20210819
package.
make install-iptables
|
is used to set up, maintain, and inspect the tables of IP packet filter rules in the Linux kernel |
|
|
is a safer way to update iptables remotely |
|
|
is used to interact with iptables using the legacy command set |
|
|
is used to restore a set of legacy iptables rules |
|
|
is used to save a set of legacy iptables rules |
|
|
is used to restore IP Tables from data specified on STDIN. Use I/O redirection provided by your shell to read from a file |
|
|
is used to dump the contents of an IP Table in easily parseable format to STDOUT. Use I/O-redirection provided by your shell to write to a file |
|
|
is used to convert the output of iptables-save to
an XML format. Using the |
|
|
are a set of commands for IPV6 that parallel the iptables commands above |
|
|
(optional) configuration tool. SYNPROXY target makes handling of large SYN floods possible without the large performance penalties imposed by the connection tracking in such cases |
|
|
is a binary that behaves according to the name it is called by |
Last updated on
The purpose of a firewall is to protect a computer or a network against malicious access. In a perfect world every daemon or service, on every machine, is perfectly configured and immune to security flaws, and all users are trusted implicitly to use the equipment as intended. However, this is rarely, if ever, the case. Daemons may be misconfigured, or updates may not have been applied for known exploits against essential services. Additionally, you may wish to choose which services are accessible by certain machines or users, or you may wish to limit which machines or applications are allowed external access. Alternatively, you simply may not trust some of your applications or users. For these reasons, a carefully designed firewall should be an essential part of system security.
While a firewall can greatly limit the scope of the above issues, do not assume that having a firewall makes careful configuration redundant, or that any negligent misconfiguration is harmless. A firewall does not prevent the exploitation of any service you offer outside of it. Despite having a firewall, you need to keep applications and daemons properly configured and up to date.
The word firewall can have several different meanings.
This is a hardware device or software program, intended to secure a home or desktop computer connected to the Internet. This type of firewall is highly relevant for users who do not know how their computers might be accessed via the Internet or how to disable that access, especially if they are always online and connected via broadband links.
An example configuration for a personal firewall is provided at Creating a Personal Firewall With iptables.
This is a system placed between the Internet and an intranet. To minimize the risk of compromising the firewall itself, it should generally have only one role—that of protecting the intranet. Although not completely risk-free, the tasks of doing the routing and IP masquerading (rewriting IP headers of the packets it routes from clients with private IP addresses onto the Internet so that they seem to come from the firewall itself) are commonly considered relatively secure.
An example configuration for a masquerading firewall is provided at Creating a Masquerading Router With iptables.
This is often an old computer you may have retired and nearly forgotten, performing masquerading or routing functions, but offering non-firewall services such as a web-cache or mail. This may be used for home networks, but is not to be considered as secure as a firewall only machine because the combination of server and router/firewall on one machine raises the complexity of the setup.
An example configuration for a BusyBox is provided at Creating a BusyBox With iptables.
This type of firewall performs masquerading or routing, but grants public access to some branch of your network that is physically separated from your regular intranet and is essentially a separate network with direct Internet access. The servers on this network are those which must be easily accessible from both the Internet and intranet. The firewall protects both networks. This type of firewall has a minimum of three network interfaces.
The example configurations provided for iptables-1.8.7 are not intended to be a complete guide to securing systems. Firewalling is a complex issue that requires careful configuration. The configurations provided by BLFS are intended only to give examples of how a firewall works. They are not intended to fit any particular configuration and may not provide complete protection from an attack.
BLFS provides an utility to manage the kernel Netfilter interface, iptables-1.8.7. It has been around since early 2.4 kernels, and has been the standard since. This is likely the set of tools that will be most familiar to existing admins. Other tools have been developped more recently, see the list of further readings below for more details. Here you will find a list of URLs that contain comprehensive information about building firewalls and further securing your system.
www.netfilter.org - Homepage of the netfilter/iptables/nftables projects
Netfilter related FAQ
Netfilter related HOWTO's
nftables HOWTO
en.tldp.org/LDP/nag2/x-087-2-firewall.html
en.tldp.org/HOWTO/Security-HOWTO.html
en.tldp.org/HOWTO/Firewall-HOWTO.html
www.linuxsecurity.com/docs/
www.little-idiot.de/firewall (German & outdated, but very comprehensive)
linux.oreillynet.com/pub/a/linux/2000/03/10/netadmin/ddos.html
staff.washington.edu/dittrich/misc/ddos
www.e-infomax.com/ipmasq
www.circlemud.org/~jelson/writings/security/index.htm
www.securityfocus.com
www.cert.org - tech_tips
security.ittoolbox.com
www.insecure.org/reading.html
Last updated on
The libcap package was installed in LFS, but if Linux-PAM support is desired, the PAM module must be built (after installation of Linux-PAM).
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://www.kernel.org/pub/linux/libs/security/linux-privs/libcap2/libcap-2.53.tar.xz
Download MD5 sum: 094994d4554c6689cf98ae4f717b8e19
Download size: 155 KB
Estimated disk space required: 1.7 MB
Estimated build time: less than 0.1 SBU
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/libcap
If you are upgrading libcap from a previous version, use the instructions in LFS libcap page to upgrade libcap. If Linux-PAM-1.5.1 has been built, the PAM module will automatically be built too.
Install libcap by running the following commands:
make -C pam_cap
This package does not come with a test suite.
Now, as the root user:
install -v -m755 pam_cap/pam_cap.so /usr/lib/security && install -v -m644 pam_cap/capability.conf /etc/security
In order to allow Linux-PAM
to grant privileges based on POSIX capabilites, you need to
add the libcap module to the begining of the /etc/pam.d/system-auth file. Make the
required edits with the following commands:
mv -v /etc/pam.d/system-auth{,.bak} &&
cat > /etc/pam.d/system-auth << "EOF" &&
# Begin /etc/pam.d/system-auth
auth optional pam_cap.so
EOF
tail -n +3 /etc/pam.d/system-auth.bak >> /etc/pam.d/system-auth
Additonally, you'll need to modify the /etc/security/capability.conf file to grant
necessary privileges to users, and utilize the setcap utility to set
capabilities on specific utilities as needed. See
man 8 setcap
and man 3
cap_from_text for additional information.
Last updated on
The Linux PAM package contains Pluggable Authentication Modules used to enable the local system administrator to choose how applications authenticate users.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://github.com/linux-pam/linux-pam/releases/download/v1.5.1/Linux-PAM-1.5.1.tar.xz
Download MD5 sum: 155f2a31d07077b2c63a1f135876c31b
Download size: 952 KB
Estimated disk space required: 37 MB (with tests)
Estimated build time: 0.4 SBU (with tests)
Optional Documentation
Download (HTTP): https://github.com/linux-pam/linux-pam/releases/download/v1.5.1/Linux-PAM-1.5.1-docs.tar.xz
Download MD5 sum: eb03b8191fc886780411054115866ee2
Download size 432 KB
Berkeley DB-5.3.28, libnsl-1.3.0, libtirpc-1.3.2, libaudit, and Prelude
docbook-xml-4.5, docbook-xsl-1.79.2, fop-2.6, libxslt-1.1.34 and either Lynx-2.8.9rel.1 or W3m
Shadow-4.9 and Systemd-249 need to be reinstalled after installing and configuring Linux PAM.
With Linux-PAM-1.4.0 and higher, the pam_cracklib module is not installed by default. To enforce strong passwords, it is recommended to use libpwquality-1.4.4.
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/linux-pam
If you downloaded the documentation, unpack the tarball by issuing the following command.
tar -xf ../Linux-PAM-1.5.1-docs.tar.xz --strip-components=1
If you instead want to regenerate the documentation, fix the configure script so that it detects lynx if installed:
sed -e 's/dummy elinks/dummy lynx/' \
-e 's/-no-numbering -no-references/-force-html -nonumbers -stdin/' \
-i configure
Install Linux PAM by running the following commands:
./configure --prefix=/usr \
--sysconfdir=/etc \
--libdir=/usr/lib \
--enable-securedir=/usr/lib/security \
--docdir=/usr/share/doc/Linux-PAM-1.5.1 &&
make
To test the results, a suitable /etc/pam.d/other configuration file must
exist.
If you have a system with Linux PAM installed and working,
be careful when modifying the files in /etc/pam.d, since your system may become
totally unusable. If you want to run the tests, you do not
need to create another /etc/pam.d/other file. The installed one
can be used for that purpose.
You should also be aware that make install overwrites
the configuration files in /etc/security as well as /etc/environment. In case you have
modified those files, be sure to back them up.
For a first installation, create the configuration file by
issuing the following commands as the root user:
install -v -m755 -d /etc/pam.d &&
cat > /etc/pam.d/other << "EOF"
auth required pam_deny.so
account required pam_deny.so
password required pam_deny.so
session required pam_deny.so
EOF
Now run the tests by issuing make check. Ensure there are no errors produced by the tests before continuing the installation. Note that the checks are quite long. It may be useful to redirect the output to a log file in order to inspect it thoroughly.
Only in case of a first installation, remove the
configuration file created earlier by issuing the following
command as the root user:
rm -fv /etc/pam.d/other
Now, as the root user:
make install && chmod -v 4755 /usr/sbin/unix_chkpwd
--enable-securedir=/usr/lib/security:
This switch sets the installation location for the
PAM modules.
--disable-regenerate-docu : If
the needed dependencies (docbook-xml-4.5, docbook-xsl-1.79.2, libxslt-1.1.34, and Lynx-2.8.9rel.1 or
W3m)
are installed, the manual pages, and the html and text
documentations are (re)generated and installed. Furthermore,
if fop-2.6 is
installed, the PDF documentation is generated and installed.
Use this switch if you do not want to rebuild the
documentation.
chmod -v 4755
/usr/sbin/unix_chkpwd: The unix_chkpwd helper program
must be setuid so that non-root processes can access the shadow
file.
Configuration information is placed in /etc/pam.d/. Below is an example file:
# Begin /etc/pam.d/other
auth required pam_unix.so nullok
account required pam_unix.so
session required pam_unix.so
password required pam_unix.so nullok
# End /etc/pam.d/other
Now set up some generic files. As the root user:
install -vdm755 /etc/pam.d && cat > /etc/pam.d/system-account << "EOF" &&# Begin /etc/pam.d/system-account account required pam_unix.so # End /etc/pam.d/system-accountEOF cat > /etc/pam.d/system-auth << "EOF" &&# Begin /etc/pam.d/system-auth auth required pam_unix.so # End /etc/pam.d/system-authEOF cat > /etc/pam.d/system-session << "EOF"# Begin /etc/pam.d/system-session session required pam_unix.so # End /etc/pam.d/system-sessionEOF cat > /etc/pam.d/system-password << "EOF"# Begin /etc/pam.d/system-password # use sha512 hash for encryption, use shadow, and try to use any previously # defined authentication token (chosen password) set by any prior module password required pam_unix.so sha512 shadow try_first_pass # End /etc/pam.d/system-passwordEOF
If you wish to enable strong password support, install libpwquality-1.4.4, and follow the instructions in that page to configure the pam_pwquality PAM module with strong password support.
Now add a restrictive /etc/pam.d/other configuration file. With
this file, programs that are PAM aware will not run unless
a configuration file specifically for that application is
created.
cat > /etc/pam.d/other << "EOF"
# Begin /etc/pam.d/other
auth required pam_warn.so
auth required pam_deny.so
account required pam_warn.so
account required pam_deny.so
password required pam_warn.so
password required pam_deny.so
session required pam_warn.so
session required pam_deny.so
# End /etc/pam.d/other
EOF
The PAM man page (man pam) provides a good starting point for descriptions of fields and allowable entries. The Linux-PAM System Administrators' Guide is recommended for additional information.
You should now reinstall the Shadow-4.9 and Systemd-249 packages.
|
displays and modifies the authentication failure record files |
|
|
is a helper binary that creates home directories |
|
|
is a helper program used to configure a private namespace for a user session |
|
|
is a helper program that transfers password hashes from passwd or shadow to opasswd |
|
|
is used to check if the default timestamp is valid |
|
|
is a helper binary that verifies the password of the current user |
|
|
is a helper binary that updates the password of a given user |
|
|
provides the interfaces between applications and the PAM modules |
Last updated on
liboauth is a collection of POSIX-C functions implementing the OAuth Core RFC 5849 standard. Liboauth provides functions to escape and encode parameters according to OAuth specification and offers high-level functionality to sign requests or verify OAuth signatures as well as perform HTTP requests.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://downloads.sourceforge.net/liboauth/liboauth-1.0.3.tar.gz
Download MD5 sum: 689b46c2b3ab1a39735ac33f714c4f7f
Download size: 496 KB
Estimated disk space required: 3.5 MB
Estimated build time: less than 0.1 SBU
Required patch for use with openssl: https://www.linuxfromscratch.org/patches/blfs/11.0/liboauth-1.0.3-openssl-1.1.0-3.patch
NSS-3.69 and Doxygen-1.9.2 (to build documentation)
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/liboauth
Apply a patch for the current version of openssl:
patch -Np1 -i ../liboauth-1.0.3-openssl-1.1.0-3.patch
Install liboauth by running the following commands:
./configure --prefix=/usr --disable-static && make
If you wish to build the documentation (needs Doxygen-1.9.2), issue:
make dox
To test the results, issue: make check.
Now, as the root user:
make install
If you have previously built the documentation, install it by
running the following commands as the root user:
install -v -dm755 /usr/share/doc/liboauth-1.0.3 && cp -rv doc/html/* /usr/share/doc/liboauth-1.0.3
--disable-static:
This switch prevents installation of static versions of the
libraries.
--enable-nss: Use this switch if
you want to use Mozilla NSS instead of OpenSSL.
Last updated on
The libpwquality package provides common functions for password quality checking and also scoring them based on their apparent randomness. The library also provides a function for generating random passwords with good pronounceability.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://github.com/libpwquality/libpwquality/releases/download/libpwquality-1.4.4/libpwquality-1.4.4.tar.bz2
Download MD5 sum: 1fe43f6641dbf1e1766e2a02cf68a9c3
Download size: 420 KB
Estimated disk space required: 4.1 MB
Estimated build time: less than 0.1 SBU
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/libpwquality
Install libpwquality by running the following commands:
./configure --prefix=/usr \
--disable-static \
--with-securedir=/usr/lib/security \
--with-python-binary=python3 &&
make
This package does not come with a test suite.
Now, as the root user:
make install
--with-python-binary=python3:
This parameter gives the location of the Python binary. The default is python, and requires Python-2.7.18.
libpwquality is intended to
be a functional replacement for the now-obsolete pam_cracklib.so PAM module. To configure
the system to use the pam_pwquality module, execute the following
commands as the root user:
mv /etc/pam.d/system-password{,.orig} &&
cat > /etc/pam.d/system-password << "EOF"
# Begin /etc/pam.d/system-password
# check new passwords for strength (man pam_pwquality)
password required pam_pwquality.so authtok_type=UNIX retry=1 difok=1 \
minlen=8 dcredit=0 ucredit=0 \
lcredit=0 ocredit=0 minclass=1 \
maxrepeat=0 maxsequence=0 \
maxclassrepeat=0 geoscheck=0 \
dictcheck=1 usercheck=1 \
enforcing=1 badwords="" \
dictpath=/usr/lib/cracklib/pw_dict
# use sha512 hash for encryption, use shadow, and use the
# authentication token (chosen password) set by pam_pwquality
# above (or any previous modules)
password required pam_unix.so sha512 shadow use_authtok
# End /etc/pam.d/system-password
EOF
Last updated on
MIT Kerberos V5 is a free implementation of Kerberos 5. Kerberos is a network authentication protocol. It centralizes the authentication database and uses kerberized applications to work with servers or services that support Kerberos allowing single logins and encrypted communication over internal networks or the Internet.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://kerberos.org/dist/krb5/1.19/krb5-1.19.2.tar.gz
Download MD5 sum: eb51b7724111e1a458a8c9a261d45a31
Download size: 8.3 MB
Estimated disk space required: 95 MB (add 24 MB for tests)
Estimated build time: 0.4 SBU (Using parallelism=4; add 1.6 SBU for tests)
BIND Utilities-9.16.20, GnuPG-2.2.29 (to authenticate the package), keyutils-1.6.1, OpenLDAP-2.5.7, Valgrind-3.17.0 (used during the testsuite), yasm-1.3.0, libedit, cmocka, pyrad, and resolv_wrapper
Some sort of time synchronization facility on your system (like ntp-4.2.8p15) is required since Kerberos won't authenticate if there is a time difference between a kerberized client and the KDC server.
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/mitkrb
Build MIT Kerberos V5 by running the following commands:
cd src &&
sed -i -e 's@\^u}@^u cols 300}@' tests/dejagnu/config/default.exp &&
sed -i -e '/eq 0/{N;s/12 //}' plugins/kdb/db2/libdb2/test/run.test &&
sed -i '/t_iprop.py/d' tests/Makefile.in &&
./configure --prefix=/usr \
--sysconfdir=/etc \
--localstatedir=/var/lib \
--runstatedir=/run \
--with-system-et \
--with-system-ss \
--with-system-verto=no \
--enable-dns-for-realm &&
make
To test the build, issue as the root user: make -k -j1 check. If you
have a former version of MIT Kerberos V5 installed, it may
happen that the test suite may pick up the installed versions
of the libraries, rather than the newly built ones. If so, it
is better to run the tests after the installation. Some tests
may fail with the latest version of dejagnu and glibc.
Now, as the root user:
make install && install -v -dm755 /usr/share/doc/krb5-1.19.2 && cp -vfr ../doc/* /usr/share/doc/krb5-1.19.2
The first sed increases the width of the virtual terminal used for some tests to prevent some spurious text in the output which is taken as a failure. The second sed removes a test that is known to fail. The third sed removes a test that is known to hang.
--localstatedir=/var/lib: This
option is used so that the Kerberos variable runtime data is
located in /var/lib instead of
/usr/var.
--runstatedir=/run:
This option is used so that the Kerberos runtime state
information is located in /run
instead of the deprecated /var/run.
--with-system-et:
This switch causes the build to use the system-installed
versions of the error-table support software.
--with-system-ss:
This switch causes the build to use the system-installed
versions of the subsystem command-line interface software.
--with-system-verto=no: This
switch fixes a bug in the package: it does not recognize its
own verto library installed previously. This is not a
problem, if reinstalling the same version, but if you are
updating, the old library is used as system's one, instead of
installing the new version.
--enable-dns-for-realm: This
switch allows realms to be resolved using the DNS server.
--with-ldap: Use this switch if
you want to compile the OpenLDAP database backend module.
You should consider installing some sort of password
checking dictionary so that you can configure the
installation to only accept strong passwords. A
suitable dictionary to use is shown in the CrackLib-2.9.7 instructions. Note
that only one file can be used, but you can concatenate
many files into one. The configuration file shown below
assumes you have installed a dictionary to /usr/share/dict/words.
Create the Kerberos configuration file with the following
commands issued by the root user:
cat > /etc/krb5.conf << "EOF"
# Begin /etc/krb5.conf
[libdefaults]
default_realm = <EXAMPLE.ORG>
encrypt = true
[realms]
<EXAMPLE.ORG> = {
kdc = <belgarath.example.org>
admin_server = <belgarath.example.org>
dict_file = /usr/share/dict/words
}
[domain_realm]
.<example.org> = <EXAMPLE.ORG>
[logging]
kdc = SYSLOG:INFO:AUTH
admin_server = SYSLOG:INFO:AUTH
default = SYSLOG:DEBUG:DAEMON
# End /etc/krb5.conf
EOF
You will need to substitute your domain and proper
hostname for the occurrences of the <belgarath> and
<example.org>
names.
default_realm should be the
name of your domain changed to ALL CAPS. This isn't
required, but both Heimdal and MIT recommend it.
encrypt = true provides
encryption of all traffic between kerberized clients and
servers. It's not necessary and can be left off. If you
leave it off, you can encrypt all traffic from the client
to the server using a switch on the client program
instead.
The [realms] parameters tell
the client programs where to look for the KDC
authentication services.
The [domain_realm] section
maps a domain to a realm.
Create the KDC database:
kdb5_util create -r <EXAMPLE.ORG> -s
Now you should populate the database with principals
(users). For now, just use your regular login name or
root.
kadmin.localkadmin.local:add_policy dict-onlykadmin.local:addprinc -policy dict-only<loginname>
The KDC server and any machine running kerberized server daemons must have a host key installed:
kadmin.local:addprinc -randkey host/<belgarath.example.org>
After choosing the defaults when prompted, you will have to export the data to a keytab file:
kadmin.local:ktadd host/<belgarath.example.org>
This should have created a file in /etc named krb5.keytab (Kerberos 5). This file
should have 600 (root rw
only) permissions. Keeping the keytab files from public
access is crucial to the overall security of the Kerberos
installation.
Exit the kadmin program (use quit or exit) and return back to the shell prompt. Start the KDC daemon manually, just to test out the installation:
/usr/sbin/krb5kdc
Attempt to get a ticket with the following command:
kinit <loginname>
You will be prompted for the password you created. After you get your ticket, you can list it with the following command:
klist
Information about the ticket should be displayed on the screen.
To test the functionality of the keytab file, issue the
following command as the root user:
ktutilktutil:rkt /etc/krb5.keytabktutil:l
This should dump a list of the host principal, along with the encryption methods used to access the principal.
Create an empty ACL file that can be modified later:
touch /var/lib/krb5kdc/kadm5.acl
At this point, if everything has been successful so far, you can feel fairly confident in the installation and configuration of the package.
For additional information consult the documentation for krb5-1.19.2 on which the above instructions are based.
If you want to start Kerberos services at boot, install the
krb5.service unit included in
the blfs-systemd-units-20210819
package using the following command:
make install-krb5
|
is a GSSAPI test client |
|
|
is a GSSAPI test server |
|
|
is a host keytable manipulation utility |
|
|
is an utility used to make modifications to the Kerberos database |
|
|
is an utility similar to kadmin, but if the database is db2, the local client kadmin.local, is intended to run directly on the master KDC without Kerberos authentication |
|
|
is a server for administrative access to a Kerberos database |
|
|
allows an administrator to manage realms, Kerberos services and ticket policies |
|
|
is the KDC database utility |
|
|
removes the current set of tickets |
|
|
is used to authenticate to the Kerberos server as a principal and acquire a ticket granting ticket that can later be used to obtain tickets for other services |
|
|
reads and displays the current tickets in the credential cache |
|
|
is a program for changing Kerberos 5 passwords |
|
|
takes a principal database in a specified format and converts it into a stream of database records |
|
|
receives a database sent by kprop and writes it as a local database |
|
|
displays the contents of the KDC database update log to standard output |
|
|
gives information on how to link programs against libraries |
|
|
is the Kerberos 5 server |
|
|
sends a problem report (PR) to a central support site |
|
|
is the super user program using Kerberos protocol.
Requires a properly configured |
|
|
makes the specified credential cache the primary cache for the collection, if a cache collection is available |
|
|
is a program for managing Kerberos keytabs |
|
|
prints keyversion numbers of Kerberos principals |
|
|
is used to contact a sample server and authenticate to it using Kerberos 5 tickets, then display the server's response |
|
|
is a simple UDP-based sample client program, for demonstration |
|
|
is a simple UDP-based server application, for demonstration |
|
|
is the sample Kerberos 5 server |
|
|
is another sample client |
|
|
is another sample server |
|
|
contains the Generic Security Service Application Programming Interface (GSSAPI) functions which provides security services to callers in a generic fashion, supportable with a range of underlying mechanisms and technologies and hence allowing source-level portability of applications to different environments |
|
|
contains the administrative authentication and password checking functions required by Kerberos 5 client-side programs |
|
|
contains the administrative authentication and password checking functions required by Kerberos 5 servers |
|
|
is a Kerberos 5 authentication/authorization database access library |
|
|
contains the internal support library for RADIUS functionality |
|
|
is an all-purpose Kerberos 5 library |
Last updated on
The Nettle package contains a low-level cryptographic library that is designed to fit easily in many contexts.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://ftp.gnu.org/gnu/nettle/nettle-3.7.3.tar.gz
Download (FTP): ftp://ftp.gnu.org/gnu/nettle/nettle-3.7.3.tar.gz
Download MD5 sum: a60273d0fab9c808646fcf5e9edc2e8f
Download size: 2.3 MB
Estimated disk space required: 87 MB (with tests)
Estimated build time: 0.4 SBU (with tests)
Valgrind-3.17.0 (optional for the tests)
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/nettle
Install Nettle by running the following commands:
./configure --prefix=/usr --disable-static && make
To test the results, issue: make check.
Now, as the root user:
make install &&
chmod -v 755 /usr/lib/lib{hogweed,nettle}.so &&
install -v -m755 -d /usr/share/doc/nettle-3.7.3 &&
install -v -m644 nettle.html /usr/share/doc/nettle-3.7.3
--disable-static:
This switch prevents installation of static versions of the
libraries.
|
calculates a hash value using a specified algorithm |
|
|
outputs a sequence of pseudorandom (non-cryptographic) bytes, using Knuth's lagged fibonacci generator. The stream is useful for testing, but should not be used to generate cryptographic keys or anything else that needs real randomness |
|
|
is a password-based key derivation function that takes a password or a passphrase as input and returns a strengthened password, which is protected against pre-computation attacks by using salting and other expensive computations. |
|
|
converts private and public RSA keys from PKCS #1 format to sexp format |
|
|
converts an s-expression to a different encoding |
Last updated on
The Network Security Services (NSS) package is a set of libraries designed to support cross-platform development of security-enabled client and server applications. Applications built with NSS can support SSL v2 and v3, TLS, PKCS #5, PKCS #7, PKCS #11, PKCS #12, S/MIME, X.509 v3 certificates, and other security standards. This is useful for implementing SSL and S/MIME or other Internet security standards into an application.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://archive.mozilla.org/pub/security/nss/releases/NSS_3_69_RTM/src/nss-3.69.tar.gz
Download MD5 sum: df451e99d09589da6c3d4f103de877bc
Download size: 79 MB
Estimated disk space required: 305 MB (add 122 MB for tests)
Estimated build time: 5.8 SBU (with parallelism=4, add 17 SBU for tests)
SQLite-3.36.0 and p11-kit-0.24.0 (runtime)
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/nss
Install NSS by running the following commands:
patch -Np1 -i ../nss-3.69-standalone-1.patch && cd nss && make BUILD_OPT=1 \ NSPR_INCLUDE_DIR=/usr/include/nspr \ USE_SYSTEM_ZLIB=1 \ ZLIB_LIBS=-lz \ NSS_ENABLE_WERROR=0 \ $([ $(uname -m) = x86_64 ] && echo USE_64=1) \ $([ -f /usr/include/sqlite3.h ] && echo NSS_USE_SYSTEM_SQLITE=1)
To run the tests, execute the following commands (1 test is known to fail):
cd tests && HOST=localhost DOMSUF=localdomain ./all.sh cd ../
Some information about the tests:
HOST=localhost and DOMSUF=localdomain are required Without these variables, a FQDN is required to specified and this generic way should work for everyone.
The tests take an extremely long time to run. If desired there is information in the all.sh script about running subsets of the total test suite.
When interrupting the tests, the test suite fails to spin down test servers that are run. This leads to an infinite loop in the tests where the test suite tries to kill a server that doesn't exist anymore because it pulls the wrong PID.
Test suite results (in HTML format!) can be found at ../../test_results/security/localhost.1/results.html
Now, as the root user:
cd ../dist &&
install -v -m755 Linux*/lib/*.so /usr/lib &&
install -v -m644 Linux*/lib/{*.chk,libcrmf.a} /usr/lib &&
install -v -m755 -d /usr/include/nss &&
cp -v -RL {public,private}/nss/* /usr/include/nss &&
chmod -v 644 /usr/include/nss/* &&
install -v -m755 Linux*/bin/{certutil,nss-config,pk12util} /usr/bin &&
install -v -m644 Linux*/lib/pkgconfig/nss.pc /usr/lib/pkgconfig
BUILD_OPT=1: This
option is passed to make so that the build is
performed with no debugging symbols built into the binaries
and the default compiler optimizations are used.
NSPR_INCLUDE_DIR=/usr/include/nspr:
This option sets the location of the nspr headers.
USE_SYSTEM_ZLIB=1:
This option is passed to make to ensure that the
libssl3.so library is linked to
the system installed zlib
instead of the in-tree version.
ZLIB_LIBS=-lz: This
option provides the linker flags needed to link to the system
zlib.
$([ $(uname -m) = x86_64 ]
&& echo USE_64=1): The USE_64=1 option is required on x86_64, otherwise
make will try
(and fail) to create 32-bit objects. The [ $(uname -m) =
x86_64 ] test ensures it has no effect on a 32 bit system.
([ -f /usr/include/sqlite3.h ]
&& echo NSS_USE_SYSTEM_SQLITE=1):
This tests if sqlite is
installed and if so it echos the option
NSS_USE_SYSTEM_SQLITE=1 to make so that libsoftokn3.so will link against the system
version of sqlite.
NSS_DISABLE_GTESTS=1: If you
don't need to run NSS test suite, append this option to
make command,
to prevent the compilation of tests and save some build time.
If p11-kit-0.24.0 is installed, the
p11-kit trust module
(/usr/lib/pkcs11/p11-kit-trust.so) can be
used as a drop-in replacement for /usr/lib/libnssckbi.so to transparently
make the system CAs available to NSS aware applications, rather than the
static list provided by /usr/lib/libnssckbi.so. As the root user, execute the following
commands:
ln -sfv ./pkcs11/p11-kit-trust.so /usr/lib/libnssckbi.so
Additionally, for dependent applications that do not use the
internal database (/usr/lib/libnssckbi.so), the /usr/sbin/make-ca script, included on the
make-ca-1.7 page can generate a system wide
NSS DB with the -n
switch, or by modifying the /etc/make-ca.conf file.
|
is the Mozilla Certificate Database Tool. It is a command-line utility that can create and modify the Netscape Communicator cert8.db and key3.db database files. It can also list, generate, modify, or delete certificates within the cert8.db file and create or change the password, generate new public and private key pairs, display the contents of the key database, or delete key pairs within the key3.db file |
|
|
is used to determine the NSS library settings of the installed NSS libraries |
|
|
is a tool for importing certificates and keys from pkcs #12 files into NSS or exporting them. It can also list certificates and keys in such files |
Last updated on
The OpenSSH package contains ssh clients and the sshd daemon. This is useful for encrypting authentication and subsequent traffic over a network. The ssh and scp commands are secure implementations of telnet and rcp respectively.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-8.7p1.tar.gz
Download MD5 sum: f545230799f131aecca04da56e61990a
Download size: 1.7 MB
Estimated disk space required: 48 MB (add 18 MB for tests)
Estimated build time: 0.3 SBU (Using parallelism=4; running the tests takes 20+ minutes, irrespective of processor speed)
GDB-10.2 (for tests), Linux-PAM-1.5.1, X Window System, MIT Kerberos V5-1.19.2, libedit, LibreSSL Portable, OpenSC, and libsectok
OpenJDK-16.0.2, Net-tools-2.10, and Sysstat-12.5.4
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/OpenSSH
OpenSSH runs as two
processes when connecting to other computers. The first
process is a privileged process and controls the issuance of
privileges as necessary. The second process communicates with
the network. Additional installation steps are necessary to
set up the proper environment, which are performed by issuing
the following commands as the root user:
install -v -m700 -d /var/lib/sshd &&
chown -v root:sys /var/lib/sshd &&
groupadd -g 50 sshd &&
useradd -c 'sshd PrivSep' \
-d /var/lib/sshd \
-g sshd \
-s /bin/false \
-u 50 sshd
Install OpenSSH by running the following commands:
./configure --prefix=/usr \
--sysconfdir=/etc/ssh \
--with-md5-passwords \
--with-privsep-path=/var/lib/sshd \
--with-default-path=/usr/bin \
--with-superuser-path=/usr/sbin:/usr/bin \
--with-pid-dir=/run
make
The testsuite requires an installed copy of scp to complete the
multiplexing tests. To run the test suite, first copy the
scp program to
/usr/bin, making sure that you
backup any existing copy first.
To test the results, issue: make -j1 tests.
Now, as the root user:
make install &&
install -v -m755 contrib/ssh-copy-id /usr/bin &&
install -v -m644 contrib/ssh-copy-id.1 \
/usr/share/man/man1 &&
install -v -m755 -d /usr/share/doc/openssh-8.7p1 &&
install -v -m644 INSTALL LICENCE OVERVIEW README* \
/usr/share/doc/openssh-8.7p1
--sysconfdir=/etc/ssh: This
prevents the configuration files from being installed in
/usr/etc.
--with-md5-passwords:
This enables the use of MD5 passwords.
--with-default-path=/usr/bin
and --with-superuser-path=/usr/sbin:/usr/bin:
These set PATH consistent with LFS
and BLFS Shadow package.
--with-pid-dir=/run:
This prevents OpenSSH from
refering to deprecated /var/run.
--with-pam: This parameter
enables Linux-PAM support in
the build.
--with-xauth=/usr/bin/xauth: Set
the default location for the xauth binary for X
authentication. Change the location if xauth will be installed to
a different path. This can also be controlled from
sshd_config with the
XAuthLocation keyword. You can omit this switch if
Xorg is already installed.
--with-kerberos5=/usr: This
option is used to include Kerberos 5 support in the build.
--with-libedit: This option
enables line editing and history features for sftp.
~/.ssh/*, /etc/ssh/ssh_config, and /etc/ssh/sshd_config
There are no required changes to any of these files.
However, you may wish to view the /etc/ssh/ files and make any changes
appropriate for the security of your system. One
recommended change is that you disable root login via ssh. Execute the
following command as the root user to disable root login via ssh:
echo "PermitRootLogin no" >> /etc/ssh/sshd_config
If you want to be able to log in without typing in your password, first create ~/.ssh/id_rsa and ~/.ssh/id_rsa.pub with ssh-keygen and then copy ~/.ssh/id_rsa.pub to ~/.ssh/authorized_keys on the remote computer that you want to log into. You'll need to change REMOTE_USERNAME and REMOTE_HOSTNAME for the username and hostname of the remote computer and you'll also need to enter your password for the ssh-copy-id command to succeed:
ssh-keygen && ssh-copy-id -i ~/.ssh/id_rsa.pubREMOTE_USERNAME@REMOTE_HOSTNAME
Once you've got passwordless logins working it's actually
more secure than logging in with a password (as the private
key is much longer than most people's passwords). If you
would like to now disable password logins, as the
root user:
echo "PasswordAuthentication no" >> /etc/ssh/sshd_config && echo "ChallengeResponseAuthentication no" >> /etc/ssh/sshd_config
If you added Linux-PAM
support and you want ssh to use it then you will need to
add a configuration file for sshd and enable use of LinuxPAM. Note, ssh only uses PAM to
check passwords, if you've disabled password logins these
commands are not needed. If you want to use PAM, issue the
following commands as the root user:
sed 's@d/login@d/sshd@g' /etc/pam.d/login > /etc/pam.d/sshd && chmod 644 /etc/pam.d/sshd && echo "UsePAM yes" >> /etc/ssh/sshd_config
Additional configuration information can be found in the man pages for sshd, ssh and ssh-agent.
To start the SSH server at system boot, install the
sshd.service unit included in
the blfs-systemd-units-20210819
package.
make install-sshd
|
is a file copy program that acts like rcp except it uses an encrypted protocol |
|
|
is an FTP-like program that works over the SSH1 and SSH2 protocols |
|
|
is an rlogin/rsh-like client program except it uses an encrypted protocol |
|
|
is a daemon that listens for ssh login requests |
|
|
is a tool which adds keys to the ssh-agent |
|
|
is an authentication agent that can store private keys |
|
|
is a script that enables logins on remote machines using local keys |
|
|
is a key generation tool |
|
|
is a utility for gathering public host keys from a number of hosts |
Last updated on
The p11-kit package provides a way to load and enumerate PKCS #11 (a Cryptographic Token Interface Standard) modules.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://github.com/p11-glue/p11-kit/releases/download/0.24.0/p11-kit-0.24.0.tar.xz
Download MD5 sum: 8ccf11c4a2e2e505b8e516d8549e64a5
Download size: 816 KB
Estimated disk space required: 56 MB (with tests)
Estimated build time: 0.2 SBU (add 0.6 SBU for tests)
libtasn1-4.17.0 and make-ca-1.7 (runtime)
GTK-Doc-1.33.2, libxslt-1.1.34, and NSS-3.69 (runtime)
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/p11-kit
Prepare the distribution specific anchor hook:
sed '20,$ d' -i trust/trust-extract-compat &&
cat >> trust/trust-extract-compat << "EOF"
# Copy existing anchor modifications to /etc/ssl/local
/usr/libexec/make-ca/copy-trust-modifications
# Generate a new trust store
/usr/sbin/make-ca -f -g
EOF
Install p11-kit by running the following commands:
mkdir p11-build &&
cd p11-build &&
meson --prefix=/usr \
--buildtype=release \
-Dtrust_paths=/etc/pki/anchors &&
ninja
To test the results, issue: ninja test.
Now, as the root user:
ninja install &&
ln -sfv /usr/libexec/p11-kit/trust-extract-compat \
/usr/bin/update-ca-certificates
--buildtype=release:
Specify a buildtype suitable for stable releases of the
package, as the default may produce unoptimized binaries.
-Dtrust_paths=/etc/pki/anchors:
this switch sets the location of trusted certificates used by
libp11-kit.so.
-Dhash_impl=freebl: Use this
switch if you want to use the Freebl library from
NSS for SHA1 and MD5
hashing.
-Dgtk_doc=true: Use this switch
if you have installed GTK-Doc-1.33.2 and libxslt-1.1.34 and wish
to rebuild the documentation and generate manual pages.
The p11-kit trust module
(/usr/lib/pkcs11/p11-kit-trust.so) can be
used as a drop-in replacement for /usr/lib/libnssckbi.so to transparently
make the system CAs available to NSS aware applications, rather than the
static list provided by /usr/lib/libnssckbi.so. As the root user, execute the following
commands:
ln -sfv ./pkcs11/p11-kit-trust.so /usr/lib/libnssckbi.so
|
is a command line tool that can be used to perform operations on PKCS#11 modules configured on the system |
|
|
is a command line tool to examine and modify the shared trust policy store |
|
|
is a command line tool to both extract local
certificates from an updated anchor store, and
regenerate all anchors and certificate stores on
the system. This is done unconditionally on BLFS
using the |
|
|
contains functions used to coordinate initialization and finalization of any PKCS#11 module |
|
|
is the PKCS#11 proxy module |
Last updated on
Polkit is a toolkit for defining and handling authorizations. It is used for allowing unprivileged processes to communicate with privileged processes.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://www.freedesktop.org/software/polkit/releases/polkit-0.119.tar.gz
Download MD5 sum: b945e683eb5d633745864af6c5746726
Download size: 1.3 MB
Estimated disk space required: 23 MB (add 2 MB for tests)
Estimated build time: 0.2 SBU (Using parallelism=4; add 0.3 SBU for tests)
Since systemd-logind uses PAM to register user sessions, it is a good idea to build Polkit with PAM support so systemd-logind can track Polkit sessions.
D-Bus Python-1.2.18 and dbusmock-0.23.1 (for tests), docbook-xml-4.5, docbook-xsl-1.79.2, GTK-Doc-1.33.2, and libxslt-1.1.34
One polkit authentication agent for using polkit in the graphical environment: polkit-kde-agent in Plasma-5.22.4 for KDE, the agent built in gnome-shell-40.4 for GNOME3, polkit-gnome-0.105 for XFCE, and lxpolkit in LXSession-0.5.5 for LXDE.
If libxslt-1.1.34 is installed, then
docbook-xml-4.5 and docbook-xsl-1.79.2 are
required. If you have installed libxslt-1.1.34, but
you do not want to install any of the DocBook packages
mentioned, you will need to use --disable-man-pages in the instructions
below.
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/polkit
There should be a dedicated user and group to take control of
the polkitd
daemon after it is started. Issue the following commands as
the root user:
groupadd -fg 27 polkitd &&
useradd -c "PolicyKit Daemon Owner" -d /etc/polkit-1 -u 27 \
-g polkitd -s /bin/false polkitd
When building Polkit with systemd logind support, the configure script explicitly checks if system is booted using systemd. This can cause problems if building the package in chroot, where the configure would fail to detect systemd. To workaround the problem, simply run the following command:
sed -i "s:/sys/fs/cgroup/systemd/:/sys:g" configure
Install Polkit by running the following commands:
./configure --prefix=/usr \
--sysconfdir=/etc \
--localstatedir=/var \
--disable-static \
--with-os-type=LFS &&
make
To test the results, first ensure that the system D-Bus daemon is running. Then run make check.
Now, as the root user:
make install
--disable-static:
This switch prevents installation of static versions of the
libraries.
--with-authfw=shadow: This switch
enables the package to use the Shadow rather than the Linux PAM Authentication framework. Use
it if you have not installed Linux
PAM.
--enable-gtk-doc: Use this
parameter if GTK-Doc is
installed and you wish to rebuild and install the API
documentation.
If you did not build Polkit with Linux PAM support, you can skip this section.
If you have built Polkit
with Linux PAM support,
you need to modify the default PAM configuration file which
was installed by default to get Polkit to work correctly with BLFS.
Issue the following commands as the root user to create the configuration
file for Linux PAM:
cat > /etc/pam.d/polkit-1 << "EOF"
# Begin /etc/pam.d/polkit-1
auth include system-auth
account include system-account
password include system-password
session include system-session
# End /etc/pam.d/polkit-1
EOF
|
is used to obtain information about registered PolicyKit actions |
|
|
is used to check whether a process is authorized for action |
|
|
is an example program to test the pkexec command |
|
|
allows an authorized user to execute a command as another user |
|
|
is used to start a textual authentication agent for the subject |
|
|
provides the org.freedesktop.PolicyKit1 D-Bus service on the system message bus |
|
|
contains the Polkit authentication agent API functions |
|
|
contains the Polkit authorization API functions |
Last updated on
The Polkit GNOME package provides an Authentication Agent for Polkit that integrates well with the GNOME Desktop environment.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://download.gnome.org/sources/polkit-gnome/0.105/polkit-gnome-0.105.tar.xz
Download (FTP): ftp://ftp.acc.umu.se/pub/gnome/sources/polkit-gnome/0.105/polkit-gnome-0.105.tar.xz
Download MD5 sum: 50ecad37c8342fb4a52f590db7530621
Download size: 305 KB
Estimated disk space required: 5.0 MB
Estimated build time: 0.1 SBU
AccountsService-0.6.55, GTK+-3.24.30, and Polkit-0.119
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/polkit-gnome
First, apply some fixes that allow for the proper user icon to be used, as well as some security fixes:
patch -Np1 -i ../polkit-gnome-0.105-consolidated_fixes-1.patch
Install Polkit GNOME by running the following commands:
./configure --prefix=/usr && make
This package does not come with a test suite.
Now, as the root user:
make install
For the authentification framework to work, polkit-gnome-authentification-agent-1 needs to be started. However, make install did not install a startup file for the Polkit GNOME so you have to create it by yourself.
Issue the following commands as the root user to create a startup file for
Polkit GNOME:
mkdir -p /etc/xdg/autostart &&
cat > /etc/xdg/autostart/polkit-gnome-authentication-agent-1.desktop << "EOF"
[Desktop Entry]
Name=PolicyKit Authentication Agent
Comment=PolicyKit Authentication Agent
Exec=/usr/libexec/polkit-gnome-authentication-agent-1
Terminal=false
Type=Application
Categories=
NoDisplay=true
OnlyShowIn=GNOME;XFCE;Unity;
AutostartCondition=GNOME3 unless-session gnome
EOF
Last updated on
Shadow was indeed installed in LFS and there is no reason to reinstall it unless you installed CrackLib or Linux-PAM after your LFS system was completed. If you have installed CrackLib after LFS, then reinstalling Shadow will enable strong password support. If you have installed Linux-PAM, reinstalling Shadow will allow programs such as login and su to utilize PAM.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://github.com/shadow-maint/shadow/releases/download/v4.9/shadow-4.9.tar.xz
Download MD5 sum: 126924090caf72f3de7e9261fd4e10ac
Download size: 1.6 MB
Estimated disk space required: 40 MB
Estimated build time: 0.3 SBU
Linux-PAM-1.5.1 or CrackLib-2.9.7
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/shadow
The installation commands shown below are for installations where Linux-PAM has been installed and Shadow is being reinstalled to support the Linux-PAM installation.
If you are reinstalling Shadow to provide strong password
support using the CrackLib
library without using Linux-PAM, ensure you add the
--with-libcrack
parameter to the configure script below
and also issue the following command:
sed -i 's@DICTPATH.*@DICTPATH\t/lib/cracklib/pw_dict@' etc/login.defs
Reinstall Shadow by running the following commands:
sed -i 's/groups$(EXEEXT) //' src/Makefile.in &&
find man -name Makefile.in -exec sed -i 's/groups\.1 / /' {} \; &&
find man -name Makefile.in -exec sed -i 's/getspnam\.3 / /' {} \; &&
find man -name Makefile.in -exec sed -i 's/passwd\.5 / /' {} \; &&
sed -e 's@#ENCRYPT_METHOD DES@ENCRYPT_METHOD SHA512@' \
-e 's@/var/spool/mail@/var/mail@' \
-e '/PATH=/{s@/sbin:@@;s@/bin:@@}' \
-i etc/login.defs &&
sed -i.orig '/$(LIBTCB)/i $(LIBPAM) \\' libsubid/Makefile.am &&
sed -i "224s/rounds/min_rounds/" libmisc/salt.c &&
autoreconf -fiv &&
./configure --sysconfdir=/etc --with-group-name-max-length=32 &&
make
This package does not come with a test suite.
Now, as the root user:
make exec_prefix=/usr install
sed -i 's/groups$(EXEEXT) //' src/Makefile.in: This sed is used to suppress the installation of the groups program as the version from the Coreutils package installed during LFS is preferred.
find man -name Makefile.in -exec ... {} \;: This command is used to suppress the installation of the groups man pages so the existing ones installed from the Coreutils package are not replaced.
sed -e 's@#ENCRYPT_METHOD
DES@ENCRYPT_METHOD SHA512@' -e 's@/var/spool/mail@/var/mail@'
-e '/PATH=/{s@/sbin:@@;s@/bin:@@}' -i
etc/login.defs: Instead of using the default
'DES' method, this command modifies the installation to use
the more secure 'SHA512' method of hashing passwords, which
also allows passwords longer than eight characters. It also
changes the obsolete /var/spool/mail location for user mailboxes
that Shadow uses by default
to the /var/mail location. It
also changes the default path to be consistent with that set
in LFS.
sed ... libmisc/salt.c and sed ... libsubid/Makefile.am: Fix a couple of errors that were found after the package was released.
--with-group-name-max-length=32:
The maximum user name is 32 characters. Make the maximum
group name the same.
Shadow's stock configuration
for the useradd
utility may not be desirable for your installation. One
default parameter causes useradd to create a mailbox
file for any newly created user. useradd will make the group
ownership of this file to the mail group with 0660 permissions. If you
would prefer that these mailbox files are not created by
useradd, issue
the following command as the root user:
sed -i 's/yes/no/' /etc/default/useradd
The rest of this page is devoted to configuring Shadow to work properly with Linux-PAM. If you do not have Linux-PAM installed, and you reinstalled Shadow to support strong passwords via the CrackLib library, no further configuration is required.
Configuring your system to use Linux-PAM can be a complex task. The information below will provide a basic setup so that Shadow's login and password functionality will work effectively with Linux-PAM. Review the information and links on the Linux-PAM-1.5.1 page for further configuration information. For information specific to integrating Shadow, Linux-PAM and libpwquality, you can visit the following link:
The login
program currently performs many functions which
Linux-PAM modules should
now handle. The following sed command will
comment out the appropriate lines in /etc/login.defs, and stop login from performing
these functions (a backup file named /etc/login.defs.orig is also created to
preserve the original file's contents). Issue the
following commands as the root user:
install -v -m644 /etc/login.defs /etc/login.defs.orig &&
for FUNCTION in FAIL_DELAY \
FAILLOG_ENAB \
LASTLOG_ENAB \
MAIL_CHECK_ENAB \
OBSCURE_CHECKS_ENAB \
PORTTIME_CHECKS_ENAB \
QUOTAS_ENAB \
CONSOLE MOTD_FILE \
FTMP_FILE NOLOGINS_FILE \
ENV_HZ PASS_MIN_LEN \
SU_WHEEL_ONLY \
CRACKLIB_DICTPATH \
PASS_CHANGE_TRIES \
PASS_ALWAYS_WARN \
CHFN_AUTH ENCRYPT_METHOD \
ENVIRON_FILE
do
sed -i "s/^${FUNCTION}/# &/" /etc/login.defs
done
As mentioned previously in the Linux-PAM instructions, Linux-PAM has two supported methods
for configuration. The commands below assume that you've
chosen to use a directory based configuration, where each
program has its own configuration file. You can
optionally use a single /etc/pam.conf configuration file by
using the text from the files below, and supplying the
program name as an additional first field for each line.
As the root user, create
the following Linux-PAM
configuration files in the /etc/pam.d/ directory (or add the
contents to the /etc/pam.conf file) using the following
commands:
cat > /etc/pam.d/login << "EOF"
# Begin /etc/pam.d/login
# Set failure delay before next prompt to 3 seconds
auth optional pam_faildelay.so delay=3000000
# Check to make sure that the user is allowed to login
auth requisite pam_nologin.so
# Check to make sure that root is allowed to login
# Disabled by default. You will need to create /etc/securetty
# file for this module to function. See man 5 securetty.
#auth required pam_securetty.so
# Additional group memberships - disabled by default
#auth optional pam_group.so
# include system auth settings
auth include system-auth
# check access for the user
account required pam_access.so
# include system account settings
account include system-account
# Set default environment variables for the user
session required pam_env.so
# Set resource limits for the user
session required pam_limits.so
# Display date of last login - Disabled by default
#session optional pam_lastlog.so
# Display the message of the day - Disabled by default
#session optional pam_motd.so
# Check user's mail - Disabled by default
#session optional pam_mail.so standard quiet
# include system session and password settings
session include system-session
password include system-password
# End /etc/pam.d/login
EOF
cat > /etc/pam.d/passwd << "EOF"
# Begin /etc/pam.d/passwd
password include system-password
# End /etc/pam.d/passwd
EOF
cat > /etc/pam.d/su << "EOF"
# Begin /etc/pam.d/su
# always allow root
auth sufficient pam_rootok.so
# Allow users in the wheel group to execute su without a password
# disabled by default
#auth sufficient pam_wheel.so trust use_uid
# include system auth settings
auth include system-auth
# limit su to users in the wheel group
auth required pam_wheel.so use_uid
# include system account settings
account include system-account
# Set default environment variables for the service user
session required pam_env.so
# include system session settings
session include system-session
# End /etc/pam.d/su
EOF
cat > /etc/pam.d/chage << "EOF"
# Begin /etc/pam.d/chage
# always allow root
auth sufficient pam_rootok.so
# include system auth, account, and session settings
auth include system-auth
account include system-account
session include system-session
# Always permit for authentication updates
password required pam_permit.so
# End /etc/pam.d/chage
EOF
for PROGRAM in chfn chgpasswd chpasswd chsh groupadd groupdel \
groupmems groupmod newusers useradd userdel usermod
do
install -v -m644 /etc/pam.d/chage /etc/pam.d/${PROGRAM}
sed -i "s/chage/$PROGRAM/" /etc/pam.d/${PROGRAM}
done
At this point, you should do a simple test to see if
Shadow is working as
expected. Open another terminal and log in as a user,
then su
to root. If you do not
see any errors, then all is well and you should proceed
with the rest of the configuration. If you did receive
errors, stop now and double check the above
configuration files manually. One obvious reason for an
error is if the user is not in group wheel. You may want to run (as
root): usermod -a -G wheel <user>.
Any other error is the sign of an error in the above
procedure. You can also run the test suite from the
Linux-PAM package to
assist you in determining the problem. If you cannot
find and fix the error, you should recompile
Shadow adding the
--without-libpam switch to
the configure command in
the above instructions (also move the /etc/login.defs.orig backup file to
/etc/login.defs). If you
fail to do this and the errors remain, you will be
unable to log into your system.
Instead of using the /etc/login.access file for controlling
access to the system, Linux-PAM uses the pam_access.so module along with the
/etc/security/access.conf
file. Rename the /etc/login.access file using the
following command:
[ -f /etc/login.access ] && mv -v /etc/login.access{,.NOUSE}
Instead of using the /etc/limits file for limiting usage of
system resources, Linux-PAM uses the pam_limits.so module along with the
/etc/security/limits.conf
file. Rename the /etc/limits file using the following
command:
[ -f /etc/limits ] && mv -v /etc/limits{,.NOUSE}
Be sure to test the login capabilities of the system before logging out. Errors in the configuration can cause a permanent lockout requiring a boot from an external source to correct the problem.
A list of the installed files, along with their short descriptions can be found at ../../../../lfs/view/11.0-systemd/chapter08/shadow.html#contents-shadow.
Last updated on
The ssh-askpass is a generic executable name for many packages, with similar names, that provide a interactive X service to grab password for packages requiring administrative privileges to be run. It prompts the user with a window box where the necessary password can be inserted. Here, we choose Damien Miller's package distributed in the OpenSSH tarball.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-8.7p1.tar.gz
Download (FTP): ftp://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-8.7p1.tar.gz
Download MD5 sum: f545230799f131aecca04da56e61990a
Download size: 1.7 MB
Estimated disk space required: 9.8 MB
Estimated build time: less than 0.1 SBU
GTK+-2.24.33, Sudo-1.9.7p2 (runtime), Xorg Libraries, and X Window System (runtime)
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/ssh-askpass
Install ssh-askpass by running the following commands:
cd contrib && make gnome-ssh-askpass2
Now, as the root user:
install -v -d -m755 /usr/libexec/openssh/contrib && install -v -m755 gnome-ssh-askpass2 /usr/libexec/openssh/contrib && ln -sv -f contrib/gnome-ssh-askpass2 /usr/libexec/openssh/ssh-askpass
The use of /usr/libexec/openssh/contrib and a symlink is justified by the eventual necessity of a different program for that service.
As the root user, configure
Sudo-1.9.7p2 to use ssh-askpass:
cat >> /etc/sudo.conf << "EOF" &&
# Path to askpass helper program
Path askpass /usr/libexec/openssh/ssh-askpass
EOF
chmod -v 0644 /etc/sudo.conf
If a given graphical <application> requires administrative privileges, use sudo -A <application> from an x-terminal, from a Window Manager menu and/or replace "Exec=<application> ..." by "Exec=sudo -A <application> ..." in the <application>.desktop file.
Last updated on
The stunnel package contains a program that allows you to encrypt arbitrary TCP connections inside SSL (Secure Sockets Layer) so you can easily communicate with clients over secure channels. stunnel can be used to add SSL functionality to commonly used Inetd daemons such as POP-2, POP-3, and IMAP servers, along with standalone daemons such as NNTP, SMTP, and HTTP. stunnel can also be used to tunnel PPP over network sockets without changes to the server package source code.
This package is known to build and work properly using an LFS-11.0 platform.
Download (FTP): ftp://ftp.stunnel.org/stunnel/archive/5.x/stunnel-5.60.tar.gz
Download MD5 sum: d68ef1c93a1e44df9455e1185d7b7742
Download size: 964 KB
Estimated disk space required: 7.2 MB
Estimated build time: 0.1 SBU
netcat (required for tests), tcpwrappers, and TOR
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/stunnel
The stunnel
daemon will be run in a chroot jail by an
unprivileged user. Create the new user and group using the
following commands as the root user:
groupadd -g 51 stunnel &&
useradd -c "stunnel Daemon" -d /var/lib/stunnel \
-g stunnel -s /bin/false -u 51 stunnel
A signed SSL Certificate and a Private Key is necessary to
run the stunnel daemon. After the
package is installed, there are instructions to generate
them. However, if you own or have already created a signed
SSL Certificate you wish to use, copy it to /etc/stunnel/stunnel.pem before starting
the build (ensure only root
has read and write access). The .pem file must be formatted as shown
below:
-----BEGIN PRIVATE KEY-----
<many encrypted lines of private key>
-----END PRIVATE KEY-----
-----BEGIN CERTIFICATE-----
<many encrypted lines of certificate>
-----END CERTIFICATE-----
-----BEGIN DH PARAMETERS-----
<encrypted lines of dh parms>
-----END DH PARAMETERS-----Install stunnel by running the following commands:
./configure --prefix=/usr \
--sysconfdir=/etc \
--localstatedir=/var &&
make
If you have installed the optional netcat application, the regression tests can be run with make check.
Now, as the root user:
make docdir=/usr/share/doc/stunnel-5.60 install
Install the included systemd unit by running the following
command as the root user:
install -v -m644 tools/stunnel.service /usr/lib/systemd/system
If you do not already have a signed SSL Certificate and
Private Key, create the stunnel.pem file in the /etc/stunnel directory using the command
below. You will be prompted to enter the necessary
information. Ensure you reply to the
Common Name (FQDN of your server) [localhost]:prompt with the name or IP address you will be using to access the service(s).
To generate a certificate, as the root user, issue:
make cert
make docdir=... install: This command installs the package and changes the documentation installation directory to standard naming conventions.
As the root user, create
the directory used for the .pid file created when the stunnel daemon starts:
install -v -m750 -o stunnel -g stunnel -d /var/lib/stunnel/run && chown stunnel:stunnel /var/lib/stunnel
Next, create a basic /etc/stunnel/stunnel.conf configuration
file using the following commands as the root user:
cat > /etc/stunnel/stunnel.conf << "EOF"
; File: /etc/stunnel/stunnel.conf
; Note: The pid and output locations are relative to the chroot location.
pid = /run/stunnel.pid
chroot = /var/lib/stunnel
client = no
setuid = stunnel
setgid = stunnel
cert = /etc/stunnel/stunnel.pem
;debug = 7
;output = stunnel.log
;[https]
;accept = 443
;connect = 80
;; "TIMEOUTclose = 0" is a workaround for a design flaw in Microsoft SSL
;; Microsoft implementations do not use SSL close-notify alert and thus
;; they are vulnerable to truncation attacks
;TIMEOUTclose = 0
EOF
Finally, add the service(s) you wish to encrypt to the configuration file. The format is as follows:
[<service>]
accept = <hostname:portnumber>
connect = <hostname:portnumber>
If you use stunnel to
encrypt a daemon started from [x]inetd, you may need to
disable that daemon in the /etc/[x]inetd.conf file and enable a
corresponding <service>_stunnel
service. You may have to add an appropriate entry in
/etc/services as well.
For a full explanation of the commands and syntax used in the configuration file, issue man stunnel.
Last updated on
The Sudo package allows a
system administrator to give certain users (or groups of
users) the ability to run some (or all) commands as
root or another user while
logging the commands and arguments.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://www.sudo.ws/dist/sudo-1.9.7p2.tar.gz
Download (FTP): ftp://ftp.sudo.ws/pub/sudo/sudo-1.9.7p2.tar.gz
Download MD5 sum: d6f8217bfd16649236e100c49e0a7cc4
Download size: 4.0 MB
Estimated disk space required: 43 MB (add 13 MB for tests)
Estimated build time: 0.4 SBU (add 0.1 SBU for tests)
Linux-PAM-1.5.1, MIT Kerberos V5-1.19.2, OpenLDAP-2.5.7, MTA (that provides a sendmail command), AFS, FWTK, and Opie
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/sudo
Install Sudo by running the following commands:
./configure --prefix=/usr \
--libexecdir=/usr/lib \
--with-secure-path \
--with-all-insults \
--with-env-editor \
--docdir=/usr/share/doc/sudo-1.9.7p2 \
--with-passprompt="[sudo] password for %p: " &&
make
To test the results, issue: env LC_ALL=C make check 2>&1 | tee make-check.log. Check the results with grep failed make-check.log.
Now, as the root user:
make install && ln -sfv libsudo_util.so.0.0.0 /usr/lib/sudo/libsudo_util.so.0
--libexecdir=/usr/lib: This
switch controls where private programs are installed.
Everything in that directory is a library, so they belong
under /usr/lib instead of
/usr/libexec.
--with-secure-path:
This switch transparently adds /sbin and /usr/sbin directories to the PATH environment variable.
--with-all-insults:
This switch includes all the sudo insult sets.
--with-env-editor:
This switch enables use of the environment variable EDITOR
for visudo.
--with-passprompt:
This switch sets the password prompt. The %p will be expanded to the name
of the user whose password is being requested.
--without-pam: This switch avoids
building Linux-PAM support
when Linux-PAM is installed
on the system.
There are many options to sudo's configure command. Check the configure --help output for a complete list.
ln -sfv libsudo_util...: Works around a bug in the installation process, which links to the previously installed version (if there is one) instead of the new one.
The sudoers file can be quite
complicated. It is composed of two types of entries:
aliases (basically variables) and user specifications
(which specify who may run what). The installation installs
a default configuration that has no privileges installed
for any user.
A couple of common configuration changes are to set the
path for the super user and to allow members of the wheel
group to execute all commands after providing their own
credientials. Use the following commands to create the
/etc/sudoers.d/sudo
configuration file as the root user:
cat > /etc/sudoers.d/sudo << "EOF"
Defaults secure_path="/usr/sbin:/usr/bin"
%wheel ALL=(ALL) ALL
EOF
For details, see man sudoers.
The Sudo developers
highly recommend using the visudo program to edit
the sudoers file. This will
provide basic sanity checking like syntax parsing and
file permission to avoid some possible mistakes that
could lead to a vulnerable configuration.
If PAM is installed on the
system, Sudo is built with
PAM support. In that case,
issue the following command as the root user to create the PAM configuration file:
cat > /etc/pam.d/sudo << "EOF"
# Begin /etc/pam.d/sudo
# include the default auth settings
auth include system-auth
# include the default account settings
account include system-account
# Set default environment variables for the service user
session required pam_env.so
# include system session defaults
session include system-session
# End /etc/pam.d/sudo
EOF
chmod 644 /etc/pam.d/sudo
|
converts between sudoers file formats |
|
|
executes a command as another user as permitted by
the |
|
|
is a sudo event and I/O log server |
|
|
sends sudo I/O logs to the log server |
|
|
is a symlink to sudo that implies
the |
|
|
is used to play back or list the output logs created by sudo |
|
|
allows for safer editing of the |
Last updated on
The Tripwire package contains programs used to verify the integrity of the files on a given system.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://github.com/Tripwire/tripwire-open-source/releases/download/2.4.3.7/tripwire-open-source-2.4.3.7.tar.gz
Download MD5 sum: a5cf1bc2f235f5d8ca458f00548db6ee
Download size: 980 KB
Estimated disk space required: 29 MB
Estimated build time: 1.6 SBU (scripting install)
An MTA
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/tripwire
Compile Tripwire by running the following commands:
sed -e '/^CLOBBER/s/false/true/' \
-e 's|TWDB="${prefix}|TWDB="/var|' \
-e '/TWMAN/ s|${prefix}|/usr/share|' \
-e '/TWDOCS/s|${prefix}/doc/tripwire|/usr/share/doc/tripwire-2.4.3.7|' \
-i installer/install.cfg &&
find . -name Makefile.am | xargs \
sed -i 's/^[[:alpha:]_]*_HEADERS.*=/noinst_HEADERS =/' &&
sed '/dist/d' -i man/man?/Makefile.am &&
autoreconf -fi &&
./configure --prefix=/usr --sysconfdir=/etc/tripwire &&
make CPPFLAGS=-std=c++11
The default configuration is to use a local MTA. If you
don't have an MTA installed and have no wish to install
one, modify install/install.cfg to use an SMTP server
instead. Otherwise the install will fail.
This package does not come with a test suite.
Now, as the root user:
make install && cp -v policy/*.txt /usr/share/doc/tripwire-2.4.3.7
During make install, several questions are asked, including passwords. If you want to make a script, you have to apply a sed before running make install:
sed -i -e 's@installer/install.sh@& -n -s<site-password>-l<local-password>@' Makefile
Of course, you should do this with dummy passwords and change them later.
Another issue when scripting is that the installer exits when the standard input is not a terminal. You may disable this behavior with the following sed:
sed '/-t 0/,+3d' -i installer/install.sh
sed ...
installer/install.cfg: This command tells the
package to install the program database and reports in
/var/lib/tripwire and sets the
proper location for man pages and documentation.
find ..., sed ..., and autoreconf -fi: The build system is unusable as is, and has to be modified for the build to succeed.
CPPFLAGS=-std=c++11: Setting the
C++ preprocessor flags to version 11 is necessary to prevent
a confict with the default version which is c++17 in recent
version of gcc.
make install:
This command creates the Tripwire security keys as well as
installing the binaries. There are two keys: a site key and a
local key which are stored in /etc/tripwire/.
cp -v policy/*.txt /usr/doc/tripwire-2.4.3.7: This command installs the tripwire sample policy files with the other tripwire documentation.i
Tripwire uses a policy
file to determine which files are integrity checked. The
default policy file (/etc/tripwire/twpol.txt) is for a default
installation and will need to be updated for your system.
Policy files should be tailored to each individual
distribution and/or installation. Some example policy files
can be found in /usr/share/doc/tripwire/.
If desired, copy the policy file you'd like to try into
/etc/tripwire/ instead of
using the default policy file, twpol.txt. It is, however, recommended
that you edit your policy file. Get ideas from the examples
above and read /usr/share/doc/tripwire/policyguide.txt
for additional information. twpol.txt is a good policy file for
learning about Tripwire as
it will note any changes to the file system and can even be
used as an annoying way of keeping track of changes for
uninstallation of software.
After your policy file has been edited to your satisfaction
you may begin the configuration steps (perform as the
root) user:
twadmin --create-polfile --site-keyfile /etc/tripwire/site.key \
/etc/tripwire/twpol.txt &&
tripwire --init
Depending on your system and the contents of the policy file, the initialization phase above can take a relatively long time.
Tripwire will identify file changes in the critical system files specified in the policy file. Using Tripwire while making frequent changes to these directories will flag all these changes. It is most useful after a system has reached a configuration that the user considers stable.
To use Tripwire after creating a policy file to run a report, use the following command:
tripwire --check > /etc/tripwire/report.txt
View the output to check the integrity of your files. An automatic integrity report can be produced by using a cron facility to schedule the runs.
Reports are stored in binary and, if desired, encrypted.
View reports, as the root
user, with:
twprint --print-report -r /var/lib/tripwire/report/<report-name.twr>
After you run an integrity check, you should examine the
report (or email) and then modify the Tripwire database to reflect the
changed files on your system. This is so that Tripwire will not continually notify
you hat files you intentionally changed are a security
violation. To do this you must first ls -l
/var/lib/tripwire/report/ and note the name
of the newest file which starts with your system name as
presented by the command uname -n and ends in
.twr. These files were
created during report creation and the most current one is
needed to update the Tripwire database of your system. As
the root user, type in the
following command making the appropriate report name:
tripwire --update --twrfile /var/lib/tripwire/report/<report-name.twr>
You will be placed into Vim with a copy of the report in front of you. If all the changes were good, then just type :wq and after entering your local key, the database will be updated. If there are files which you still want to be warned about, remove the 'x' before the filename in the report and type :wq.
|
is a signature gathering utility that displays the hash function values for the specified files |
|
|
is the main file integrity checking program |
|
|
administrative and utility tool used to perform certain administrative functions related to Tripwire files and configuration options |
|
|
prints Tripwire database and report files in clear text format |
Last updated on
The volume_key package provides a library for manipulating storage volume encryption keys and storing them separately from volumes to handle forgotten passphrases.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://github.com/felixonmars/volume_key/archive/volume_key-0.3.12.tar.gz
Download MD5 sum: d1c76f24e08ddd8c1787687d0af5a814
Download size: 196 KB
Estimated disk space required: 11 MB
Estimated build time: 0.2 SBU
cryptsetup-2.3.6, GLib-2.68.4, GPGME-1.16.0, and NSS-3.69
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/volume_key
Install volume_key by running the following commands:
This package expands to the directory volume_key-volume_key-0.3.12.
autoreconf -fiv &&
./configure --prefix=/usr \
--without-python &&
make
This package does not come with a functioning test suite.
Now, as the root user:
make install
--without-python:
This parameter prevents building the Python 2 bindings, if Python-2.7.18 is
installed.
--without-python3: Use this
option if you do not want to build the Python 3 bindings. In this case,
SWIG-4.0.2 is not needed.
Last updated on
Journaling file systems reduce the time needed to recover a file system that was not unmounted properly. While this can be extremely important in reducing downtime for servers, it has also become popular for desktop environments. This chapter contains other journaling file systems you can use instead of the default LFS extended file system (ext2/3/4). It also provides introductory material on managing disk arrays.
The only purpose of an initramfs is to mount the root filesystem. The initramfs is a complete set of directories that you would find on a normal root filesystem. It is bundled into a single cpio archive and compressed with one of several compression algorithms.
At boot time, the boot loader loads the kernel and the initramfs image into memory and starts the kernel. The kernel checks for the presence of the initramfs and, if found, mounts it as / and runs /init. The init program is typically a shell script. Note that the boot process takes longer, possibly significantly longer, if an initramfs is used.
For most distributions, kernel modules are the biggest reason to have an initramfs. In a general distribution, there are many unknowns such as file system types and disk layouts. In a way, this is the opposite of LFS where the system capabilities and layout are known and a custom kernel is normally built. In this situation, an initramfs is rarely needed.
There are only four primary reasons to have an initramfs in the LFS environment: loading the rootfs from a network, loading it from an LVM logical volume, having an encrypted rootfs where a password is required, or for the convenience of specifying the rootfs as a LABEL or UUID. Anything else usually means that the kernel was not configured properly.
If you do decide to build an initramfs, the following scripts will provide a basis to do it. The scripts will allow specifying a rootfs via partition UUID or partition LABEL or a rootfs on an LVM logical volume. They do not support an encrypted root file system or mounting the rootfs over a network card. For a more complete capability see the LFS Hints or dracut.
To install these scripts, run the following commands as the
root user:
cat > /usr/sbin/mkinitramfs << "EOF"
#!/bin/bash
# This file based in part on the mkinitramfs script for the LFS LiveCD
# written by Alexander E. Patrakov and Jeremy Huntwork.
copy()
{
local file
if [ "$2" = "lib" ]; then
file=$(PATH=/usr/lib type -p $1)
else
file=$(type -p $1)
fi
if [ -n "$file" ] ; then
cp $file $WDIR/usr/$2
else
echo "Missing required file: $1 for directory $2"
rm -rf $WDIR
exit 1
fi
}
if [ -z $1 ] ; then
INITRAMFS_FILE=initrd.img-no-kmods
else
KERNEL_VERSION=$1
INITRAMFS_FILE=initrd.img-$KERNEL_VERSION
fi
if [ -n "$KERNEL_VERSION" ] && [ ! -d "/usr/lib/modules/$1" ] ; then
echo "No modules directory named $1"
exit 1
fi
printf "Creating $INITRAMFS_FILE... "
binfiles="sh cat cp dd killall ls mkdir mknod mount "
binfiles="$binfiles umount sed sleep ln rm uname"
binfiles="$binfiles readlink basename"
# Systemd installs udevadm in /bin. Other udev implementations have it in /sbin
if [ -x /usr/bin/udevadm ] ; then binfiles="$binfiles udevadm"; fi
sbinfiles="modprobe blkid switch_root"
# Optional files and locations
for f in mdadm mdmon udevd udevadm; do
if [ -x /usr/sbin/$f ] ; then sbinfiles="$sbinfiles $f"; fi
done
# Add lvm if present (cannot be done with the others because it
# also needs dmsetup
if [ -x /usr/sbin/lvm ] ; then sbinfiles="$sbinfiles lvm dmsetup"; fi
unsorted=$(mktemp /tmp/unsorted.XXXXXXXXXX)
DATADIR=/usr/share/mkinitramfs
INITIN=init.in
# Create a temporary working directory
WDIR=$(mktemp -d /tmp/initrd-work.XXXXXXXXXX)
# Create base directory structure
mkdir -p $WDIR/{dev,run,sys,proc,usr/{bin,lib/{firmware,modules},sbin}}
mkdir -p $WDIR/etc/{modprobe.d,udev/rules.d}
touch $WDIR/etc/modprobe.d/modprobe.conf
ln -s usr/bin $WDIR/bin
ln -s usr/lib $WDIR/lib
ln -s usr/sbin $WDIR/sbin
ln -s lib $WDIR/lib64
# Create necessary device nodes
mknod -m 640 $WDIR/dev/console c 5 1
mknod -m 664 $WDIR/dev/null c 1 3
# Install the udev configuration files
if [ -f /etc/udev/udev.conf ]; then
cp /etc/udev/udev.conf $WDIR/etc/udev/udev.conf
fi
for file in $(find /etc/udev/rules.d/ -type f) ; do
cp $file $WDIR/etc/udev/rules.d
done
# Install any firmware present
cp -a /usr/lib/firmware $WDIR/usr/lib
# Copy the RAID configuration file if present
if [ -f /etc/mdadm.conf ] ; then
cp /etc/mdadm.conf $WDIR/etc
fi
# Install the init file
install -m0755 $DATADIR/$INITIN $WDIR/init
if [ -n "$KERNEL_VERSION" ] ; then
if [ -x /usr/bin/kmod ] ; then
binfiles="$binfiles kmod"
else
binfiles="$binfiles lsmod"
sbinfiles="$sbinfiles insmod"
fi
fi
# Install basic binaries
for f in $binfiles ; do
ldd /usr/bin/$f | sed "s/\t//" | cut -d " " -f1 >> $unsorted
copy /usr/bin/$f bin
done
for f in $sbinfiles ; do
ldd /usr/sbin/$f | sed "s/\t//" | cut -d " " -f1 >> $unsorted
copy $f sbin
done
# Add udevd libraries if not in /usr/sbin
if [ -x /usr/lib/udev/udevd ] ; then
ldd /usr/lib/udev/udevd | sed "s/\t//" | cut -d " " -f1 >> $unsorted
elif [ -x /usr/lib/systemd/systemd-udevd ] ; then
ldd /usr/lib/systemd/systemd-udevd | sed "s/\t//" | cut -d " " -f1 >> $unsorted
fi
# Add module symlinks if appropriate
if [ -n "$KERNEL_VERSION" ] && [ -x /usr/bin/kmod ] ; then
ln -s kmod $WDIR/usr/bin/lsmod
ln -s kmod $WDIR/usr/bin/insmod
fi
# Add lvm symlinks if appropriate
# Also copy the lvm.conf file
if [ -x /usr/sbin/lvm ] ; then
ln -s lvm $WDIR/usr/sbin/lvchange
ln -s lvm $WDIR/usr/sbin/lvrename
ln -s lvm $WDIR/usr/sbin/lvextend
ln -s lvm $WDIR/usr/sbin/lvcreate
ln -s lvm $WDIR/usr/sbin/lvdisplay
ln -s lvm $WDIR/usr/sbin/lvscan
ln -s lvm $WDIR/usr/sbin/pvchange
ln -s lvm $WDIR/usr/sbin/pvck
ln -s lvm $WDIR/usr/sbin/pvcreate
ln -s lvm $WDIR/usr/sbin/pvdisplay
ln -s lvm $WDIR/usr/sbin/pvscan
ln -s lvm $WDIR/usr/sbin/vgchange
ln -s lvm $WDIR/usr/sbin/vgcreate
ln -s lvm $WDIR/usr/sbin/vgscan
ln -s lvm $WDIR/usr/sbin/vgrename
ln -s lvm $WDIR/usr/sbin/vgck
# Conf file(s)
cp -a /etc/lvm $WDIR/etc
fi
# Install libraries
sort $unsorted | uniq | while read library ; do
# linux-vdso and linux-gate are pseudo libraries and do not correspond to a file
# libsystemd-shared is in /lib/systemd, so it is not found by copy, and
# it is copied below anyway
if [[ "$library" == linux-vdso.so.1 ]] ||
[[ "$library" == linux-gate.so.1 ]] ||
[[ "$library" == libsystemd-shared* ]]; then
continue
fi
copy $library lib
done
if [ -d /usr/lib/udev ]; then
cp -a /usr/lib/udev $WDIR/usr/lib
fi
if [ -d /usr/lib/systemd ]; then
cp -a /usr/lib/systemd $WDIR/usr/lib
fi
if [ -d /usr/lib/elogind ]; then
cp -a /usr/lib/elogind $WDIR/usr/lib
fi
# Install the kernel modules if requested
if [ -n "$KERNEL_VERSION" ]; then
find \
/usr/lib/modules/$KERNEL_VERSION/kernel/{crypto,fs,lib} \
/usr/lib/modules/$KERNEL_VERSION/kernel/drivers/{block,ata,md,firewire} \
/usr/lib/modules/$KERNEL_VERSION/kernel/drivers/{scsi,message,pcmcia,virtio} \
/usr/lib/modules/$KERNEL_VERSION/kernel/drivers/usb/{host,storage} \
-type f 2> /dev/null | cpio --make-directories -p --quiet $WDIR
cp /usr/lib/modules/$KERNEL_VERSION/modules.{builtin,order} \
$WDIR/usr/lib/modules/$KERNEL_VERSION
depmod -b $WDIR $KERNEL_VERSION
fi
( cd $WDIR ; find . | cpio -o -H newc --quiet | gzip -9 ) > $INITRAMFS_FILE
# Prepare early loading of microcode if available
if ls /usr/lib/firmware/intel-ucode/* >/dev/null 2>&1 ||
ls /usr/lib/firmware/amd-ucode/* >/dev/null 2>&1; then
# first empty WDIR to reuse it
rm -r $WDIR/*
DSTDIR=$WDIR/kernel/x86/microcode
mkdir -p $DSTDIR
if [ -d /usr/lib/firmware/amd-ucode ]; then
cat /usr/lib/firmware/amd-ucode/microcode_amd*.bin > $DSTDIR/AuthenticAMD.bin
fi
if [ -d /usr/lib/firmware/intel-ucode ]; then
cat /usr/lib/firmware/intel-ucode/* > $DSTDIR/GenuineIntel.bin
fi
( cd $WDIR; find . | cpio -o -H newc --quiet ) > microcode.img
cat microcode.img $INITRAMFS_FILE > tmpfile
mv tmpfile $INITRAMFS_FILE
rm microcode.img
fi
# Remove the temporary directories and files
rm -rf $WDIR $unsorted
printf "done.\n"
EOF
chmod 0755 /usr/sbin/mkinitramfs
mkdir -p /usr/share/mkinitramfs &&
cat > /usr/share/mkinitramfs/init.in << "EOF"
#!/bin/sh
PATH=/usr/bin:/usr/sbin
export PATH
problem()
{
printf "Encountered a problem!\n\nDropping you to a shell.\n\n"
sh
}
no_device()
{
printf "The device %s, which is supposed to contain the\n" $1
printf "root file system, does not exist.\n"
printf "Please fix this problem and exit this shell.\n\n"
}
no_mount()
{
printf "Could not mount device %s\n" $1
printf "Sleeping forever. Please reboot and fix the kernel command line.\n\n"
printf "Maybe the device is formatted with an unsupported file system?\n\n"
printf "Or maybe filesystem type autodetection went wrong, in which case\n"
printf "you should add the rootfstype=... parameter to the kernel command line.\n\n"
printf "Available partitions:\n"
}
do_mount_root()
{
mkdir /.root
[ -n "$rootflags" ] && rootflags="$rootflags,"
rootflags="$rootflags$ro"
case "$root" in
/dev/* ) device=$root ;;
UUID=* ) eval $root; device="/dev/disk/by-uuid/$UUID" ;;
PARTUUID=*) eval $root; device="/dev/disk/by-partuuid/$PARTUUID" ;;
LABEL=* ) eval $root; device="/dev/disk/by-label/$LABEL" ;;
"" ) echo "No root device specified." ; problem ;;
esac
while [ ! -b "$device" ] ; do
no_device $device
problem
done
if ! mount -n -t "$rootfstype" -o "$rootflags" "$device" /.root ; then
no_mount $device
cat /proc/partitions
while true ; do sleep 10000 ; done
else
echo "Successfully mounted device $root"
fi
}
do_try_resume()
{
case "$resume" in
UUID=* ) eval $resume; resume="/dev/disk/by-uuid/$UUID" ;;
LABEL=*) eval $resume; resume="/dev/disk/by-label/$LABEL" ;;
esac
if $noresume || ! [ -b "$resume" ]; then return; fi
ls -lH "$resume" | ( read x x x x maj min x
echo -n ${maj%,}:$min > /sys/power/resume )
}
init=/sbin/init
root=
rootdelay=
rootfstype=auto
ro="ro"
rootflags=
device=
resume=
noresume=false
mount -n -t devtmpfs devtmpfs /dev
mount -n -t proc proc /proc
mount -n -t sysfs sysfs /sys
mount -n -t tmpfs tmpfs /run
read -r cmdline < /proc/cmdline
for param in $cmdline ; do
case $param in
init=* ) init=${param#init=} ;;
root=* ) root=${param#root=} ;;
rootdelay=* ) rootdelay=${param#rootdelay=} ;;
rootfstype=*) rootfstype=${param#rootfstype=} ;;
rootflags=* ) rootflags=${param#rootflags=} ;;
resume=* ) resume=${param#resume=} ;;
noresume ) noresume=true ;;
ro ) ro="ro" ;;
rw ) ro="rw" ;;
esac
done
# udevd location depends on version
if [ -x /sbin/udevd ]; then
UDEVD=/sbin/udevd
elif [ -x /lib/udev/udevd ]; then
UDEVD=/lib/udev/udevd
elif [ -x /lib/systemd/systemd-udevd ]; then
UDEVD=/lib/systemd/systemd-udevd
else
echo "Cannot find udevd nor systemd-udevd"
problem
fi
${UDEVD} --daemon --resolve-names=never
udevadm trigger
udevadm settle
if [ -f /etc/mdadm.conf ] ; then mdadm -As ; fi
if [ -x /sbin/vgchange ] ; then /sbin/vgchange -a y > /dev/null ; fi
if [ -n "$rootdelay" ] ; then sleep "$rootdelay" ; fi
do_try_resume # This function will not return if resuming from disk
do_mount_root
killall -w ${UDEVD##*/}
exec switch_root /.root "$init" "$@"
EOF
LVM2-2.03.13 and/or mdadm-4.1 must be installed before generating the initramfs, if the system partition uses them.
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/initramfs
To build an initramfs, run the following as the root user:
mkinitramfs [KERNEL VERSION]
The optional argument is the directory where the appropriate
kernel modules are located. This must be a subdirectory of
/lib/modules. If no modules are
specified, then the initramfs is named initrd.img-no-kmods. If a kernel
version is specified, the initrd is named initrd.img-$KERNEL_VERSION and is
only appropriate for the specific kernel specified. The
output file will be placed in the current directory.
If early loading of microcode is needed (see the
section called “Microcode updates for CPUs”),
you can install the appropriate blob or container in
/lib/firmware. It will be
automatically added to the initrd when running mkinitramfs.
After generating the initrd, copy it to the /boot directory.
Now edit /boot/grub/grub.cfg
and add a new menuentry. Below are several examples.
# Generic initramfs and root fs identified by UUID
menuentry "LFS Dev (LFS-7.0-Feb14) initrd, Linux 3.0.4"
{
linux /vmlinuz-3.0.4-lfs-20120214 root=UUID=54b934a9-302d-415e-ac11-4988408eb0a8 ro
initrd /initrd.img-no-kmods
}
# Generic initramfs and root fs on LVM partition
menuentry "LFS Dev (LFS-7.0-Feb18) initrd lvm, Linux 3.0.4"
{
linux /vmlinuz-3.0.4-lfs-20120218 root=/dev/mapper/myroot ro
initrd /initrd.img-no-kmods
}
# Specific initramfs and root fs identified by LABEL
menuentry "LFS Dev (LFS-7.1-Feb20) initrd label, Linux 3.2.6"
{
linux /vmlinuz-3.2.6-lfs71-120220 root=LABEL=lfs71 ro
initrd /initrd.img-3.2.6-lfs71-120220
}
Finally, reboot the system and select the desired system.
Last updated on
The btrfs-progs package contains administration and debugging tools for the B-tree file system (btrfs).
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://www.kernel.org/pub/linux/kernel/people/kdave/btrfs-progs/btrfs-progs-v5.13.1.tar.xz
Download MD5 sum: 8ca78d6e62179ef177597422e27a58fc
Download size: 2.1 MB
Estimated disk space required: 54 MB (up to 2.7 GB are used during tests)
Estimated build time: 0.2 SBU (add 5.9 SBU for tests, but will be longer on slow disks)
asciidoc-9.1.0 and xmlto-0.0.28 (both required to generate man pages)
LVM2-2.03.13 (dmsetup is used in tests) and reiserfsprogs-3.6.27 (for tests)
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/btrfs-progs
Enable the following option in the kernel configuration and recompile the kernel:
File systems --->
<*/M> Btrfs filesystem support [CONFIG_BTRFS_FS]In addition to the above and to the options required for LVM2-2.03.13 and reiserfsprogs-3.6.27, the following options must be enabled for running tests:
File systems --->
[*] Btrfs POSIX Access Control Lists [CONFIG_BTRFS_FS_POSIX_ACL]
[*] ReiserFS extended attributes [CONFIG_REISERFS_FS_XATTR]
[*] ReiserFS POSIX Access Control Lists [CONFIG_REISERFS_FS_POSIX_ACL]Install btrfs-progs by running the following commands:
./configure --prefix=/usr && make
Some tests require grep built with perl regular expressions. To obtain this, rebuild grep with the LFS Chapter 8 instructions after installing PCRE-8.45.
Before running tests, build a support program:
make fssum
To test the results, issue (as the root user):
pushd tests ./fsck-tests.sh ./mkfs-tests.sh ./cli-tests.sh ./convert-tests.sh ./misc-tests.sh ./fuzz-tests.sh popd
If the above mentioned kernel options are not enabled, some tests fail, and prevent all the remaining tests to run, because the test disk image is not cleanly unmounted.
Install the package as the root user:
make install
--disable-documentation: This
option is needed if the recommended dependencies are not
installed.
|
is the main interface into btrfs filesystem operations |
|
|
converts from an ext2/3/4 or reiserfs filesystem to btrfs |
|
|
is a filter to find btrfs root |
|
|
maps btrfs logical extent to physical extent |
|
|
overwrites the primary superblock with a backup copy |
|
|
tunes various filesystem parameters |
|
|
does nothing, but is present for consistency with fstab |
|
|
creates a btrfs file system |
Last updated on
The dosfstools package contains various utilities for use with the FAT family of file systems.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://github.com/dosfstools/dosfstools/releases/download/v4.2/dosfstools-4.2.tar.gz
Download MD5 sum: 49c8e457327dc61efab5b115a27b087a
Download size: 314 KB
Estimated disk space required: 3.5 MB
Estimated build time: less than 0.1 SBU
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/dosfstools
Enable the following option in the kernel configuration and recompile the kernel:
File systems --->
<DOS/FAT/EXFAT/NT Filesystems --->
<*/M> MSDOS fs support [CONFIG_MSDOS_FS]
<*/M> VFAT (Windows-95) fs support [CONFIG_VFAT_FS]Install dosfstools by running the following commands:
./configure --prefix=/usr \
--enable-compat-symlinks \
--mandir=/usr/share/man \
--docdir=/usr/share/doc/dosfstools-4.2 &&
make
This package does not come with a test suite.
Now, as the root user:
make install
--enable-compat-symlinks: This
switch creates the dosfsck,
dosfslabel, fsck.msdos, fsck.vfat, mkdosfs, mkfs.msdos, and mkfs.vfat symlinks required by some
programs.
Last updated on
FUSE (Filesystem in Userspace) is a simple interface for userspace programs to export a virtual filesystem to the Linux kernel. Fuse also aims to provide a secure method for non privileged users to create and mount their own filesystem implementations.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://github.com/libfuse/libfuse/releases/download/fuse-3.10.4/fuse-3.10.4.tar.xz
Download MD5 sum: 55b87e9ed691c2fa698e491241985b4a
Download size: 2.7 MB
Estimated disk space required: 150 MB
Estimated build time: 0.1 SBU (add 0.4 SBU for tests)
Doxygen-1.9.2 (to rebuild the API documentation) and pytest (required for tests)
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/fuse
Enable the following options in the kernel configuration and recompile the kernel if necessary:
File systems --->
<*/M> FUSE (Filesystem in Userspace) support [CONFIG_FUSE_FS]Character devices in user space should be enabled too for running the tests:
File systems --->
<*/M> FUSE (Filesystem in Userspace) support [CONFIG_FUSE_FS]
<*/M> Character device in Userspace support [CONFIG_CUSE]Install Fuse by running the following commands:
sed -i '/^udev/,$ s/^/#/' util/meson.build && mkdir build && cd build && meson --prefix=/usr --buildtype=release .. && ninja
The API documentation is included in the package, but if you have Doxygen-1.9.2 installed and wish to rebuild it, issue:
pushd .. && doxygen doc/Doxyfile && popd
To test the results, run (as the root user):
python3 -m pytest test/
The pytest Python module is required for the tests.
Now, as the root user:
ninja install &&
chmod u+s /usr/bin/fusermount3 &&
install -v -m755 -d /usr/share/doc/fuse-3.10.4 &&
install -v -m644 ../doc/{README.NFS,kernel.txt} \
/usr/share/doc/fuse-3.10.4 &&
cp -Rv ../doc/html /usr/share/doc/fuse-3.10.4
sed ... util/meson.build: This command disables the installation of a boot script and udev rule that are not needed.
--buildtype=release:
Specify a buildtype suitable for stable releases of the
package, as the default may produce unoptimized binaries.
Some options regarding mount policy can be set in the file
/etc/fuse.conf. To install
the file run the following command as the root user:
cat > /etc/fuse.conf << "EOF"
# Set the maximum number of FUSE mounts allowed to non-root users.
# The default is 1000.
#
#mount_max = 1000
# Allow non-root users to specify the 'allow_other' or 'allow_root'
# mount options.
#
#user_allow_other
EOF
Additional information about the meaning of the configuration options are found in the man page.
Last updated on
The jfsutils package contains administration and debugging tools for the jfs file system.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): http://jfs.sourceforge.net/project/pub/jfsutils-1.1.15.tar.gz
Download MD5 sum: 8809465cd48a202895bc2a12e1923b5d
Download size: 532 KB
Estimated disk space required: 8.9 MB
Estimated build time: 0.1 SBU
Required patch to fix issues exposed by GCC 10 and later: https://www.linuxfromscratch.org/patches/blfs/11.0/jfsutils-1.1.15-gcc10_fix-1.patch
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/jfs
Enable the following option in the kernel configuration and recompile the kernel:
File systems --->
<*/M> JFS filesystem support [CONFIG_JFS_FS]First, fix some issues exposed by GCC 10 and later:
patch -Np1 -i ../jfsutils-1.1.15-gcc10_fix-1.patch
Install jfsutils by running the following commands:
sed -i "/unistd.h/a#include <sys/types.h>" fscklog/extract.c && sed -i "/ioctl.h/a#include <sys/sysmacros.h>" libfs/devices.c && ./configure && make
This package does not come with a test suite.
Now, as the root user:
make install
sed ...: Fixes building with glibc 2.28.
|
is used to replay the JFS transaction log, check a JFS formatted device for errors, and fix any errors found |
|
|
is a hard link to fsck.jfs |
|
|
constructs an JFS file system |
|
|
is a hard link to mkfs.jfs |
|
|
is a program which can be used to perform various low-level actions on a JFS formatted device |
|
|
extracts a JFS fsck service log into a file and/or formats and displays the extracted file |
|
|
dumps the contents of the journal log from the specified JFS formatted device into output file ./jfslog.dmp |
|
|
adjusts tunable file system parameters on JFS file systems |
Last updated on
The LVM2 package is a set of tools that manage logical partitions. It allows spanning of file systems across multiple physical disks and disk partitions and provides for dynamic growing or shrinking of logical partitions, mirroring and low storage footprint snapshots.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://sourceware.org/ftp/lvm2/LVM2.2.03.13.tgz
Download (FTP): ftp://sourceware.org/pub/lvm2/LVM2.2.03.13.tgz
Download MD5 sum: c4be18fcb94c84c26f71ff4235917c28
Download size: 2.5 MB
Estimated disk space required: 37 MB (add 18 MB for tests; transient files can grow up to around 800 MB in the /tmp directory during tests)
Estimated build time: 0.2 SBU (using parallelism=4; add 9 to 48 SBU for tests, depending on disk speed)
mdadm-4.1, reiserfsprogs-3.6.27, Valgrind-3.17.0, Which-2.21, xfsprogs-5.13.0 (all five may be used, but are not required, for tests), thin-provisioning-tools, and vdo
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/lvm2
Enable the following options in the kernel configuration and recompile the kernel:
There are several other Device Mapper options in the kernel beyond those listed below. In order to get reasonable results if running the regression tests, all must be enabled either internally or as a module. The tests will all time out if Magic SysRq key is not enabled.
Device Drivers --->
[*] Multiple devices driver support (RAID and LVM) ---> [CONFIG_MD]
<*/M> Device mapper support [CONFIG_BLK_DEV_DM]
<*/M> Crypt target support [CONFIG_DM_CRYPT]
<*/M> Snapshot target [CONFIG_DM_SNAPSHOT]
<*/M> Thin provisioning target [CONFIG_DM_THIN_PROVISIONING]
<*/M> Cache target (EXPERIMENTAL) [CONFIG_DM_CACHE]
<*/M> Mirror target [CONFIG_DM_MIRROR]
<*/M> Zero target [CONFIG_DM_ZERO]
<*/M> I/O delaying target [CONFIG_DM_DELAY]
[*] Block devices --->
<*/M> RAM block device support [CONFIG_BLK_DEV_RAM]
Kernel hacking --->
Generic Kernel Debugging Instruments --->
[*] Magic SysRq key [CONFIG_MAGIC_SYSRQ]Install LVM2 by running the following commands:
PATH+=:/usr/sbin \
./configure --prefix=/usr \
--enable-cmdlib \
--enable-pkgconfig \
--enable-udev_sync &&
make
The tests use udev for
logical volume synchronization, so the LVM udev rules and
some utilities need to be installed before running the tests.
If you are installing LVM2
for the first time, and do not want to install the full
package before running the tests, the minimal set of
utilities can be installed by running the following
instructions as the root
user:
make -C tools install_tools_dynamic && make -C udev install && make -C libdm install
To test the results, issue, as the root user:
make S=shell/thin-flags.sh check_local
The S=... option allows to skip tests. The shell/thin-flags.sh test has been reported to freeze the computer. Other targets are available and can be listed with make -C test help. The test timings are very dependent on the speed of the disk(s), and on the number of enabled kernel options.
The tests do not implement the “expected fail” possibility, and a small number of test failures is expected by upstream. More failures may happen because some kernel options are missing. For example, the lack of the dm-delay device mapper target explains some failures. Some tests may fail if there is insufficient free space available in the partition with the /tmp directory. At least one test fails if 16 TB is not available. Some tests are flagged “warned” if thin-provisioning-tools are not installed. A workaround is to add the following flags to configure:
--with-thin-check= \
--with-thin-dump= \
--with-thin-repair= \
--with-thin-restore= \
--with-cache-check= \
--with-cache-dump= \
--with-cache-repair= \
--with-cache-restore= \
Some tests may hang. They can be removed if necessary, for example: rm test/shell/lvconvert-raid-reshape.sh. The tests generate a lot of kernel messages, which may clutter your terminal. You can disable them by issuing dmesg -D before running the tests (do not forget to issue dmesg -E when tests are done).
The checks create device nodes in the /tmp directory. The tests will fail if /tmp is mounted with the nodev option.
Now, as the root user:
make install make install_systemd_units
PATH+=:/usr/sbin: The path
must contain /usr/sbin for
proper system tool detection by the configure script. This
instruction ensures that PATH is properly set even if you
build as an unprivileged user.
--enable-cmdlib: This
switch enables building of the shared command library. It is
required when building the event daemon.
--enable-pkgconfig:
This switch enables installation of pkg-config support files.
--enable-udev_sync:
This switch enables synchronisation with Udev processing.
--enable-dmeventd: This switch
enables building of the Device
Mapper event daemon.
make install_systemd_units: This is needed to install a unit that activates logical volumes at boot. It is not installed by default.
|
is a utility to deactivate block devices |
|
|
(optional) is the Device Mapper event daemon |
|
|
is a low level logical volume management tool |
|
|
is a utility used to resize or check filesystem on a device |
|
|
provides the command-line tools for LVM2. Commands are implemented via sympolic links to this program to manage physical devices (pv*), volume groups (vg*) and logical volumes (lv*) |
|
|
is a tool used to dump various information concerning LVM2 |
|
|
is used to import a duplicated VG (e.g. hardware snapshot) |
|
|
contains the Device Mapper API functions |
Last updated on
LVM manages disk drives. It allows multiple drives and partitions to be combined into larger volume groups, assists in making backups through a snapshot, and allows for dynamic volume resizing. It can also provide mirroring similar to a RAID 1 array.
A complete discussion of LVM is beyond the scope of this introduction, but basic concepts are presented below.
To run any of the commands presented here, the LVM2-2.03.13 package must
be installed. All commands must be run as the root user.
Management of disks with lvm is accomplished using the following concepts:
These are physical disks or partitions such as /dev/sda3 or /dev/sdb.
These are named groups of physical volumes that can be manipulated by the administrator. The number of physical volumes that make up a volume group is arbitrary. Physical volumes can be dynamically added or removed from a volume group.
Volume groups may be subdivided into logical volumes. Each logical volume can then be individually formatted as if it were a regular Linux partition. Logical volumes may be dynamically resized by the administrator according to need.
To give a concrete example, suppose that you have two 2 TB
disks. Also suppose a really large amount of space is required
for a very large database, mounted on /srv/mysql. This is what the initial set of
partitions would look like:
Partition Use Size Partition Type
/dev/sda1 /boot 100MB 83 (Linux)
/dev/sda2 / 10GB 83 (Linux)
/dev/sda3 swap 2GB 82 (Swap)
/dev/sda4 LVM remainder 8e (LVM)
/dev/sdb1 swap 2GB 82 (Swap)
/dev/sdb2 LVM remainder 8e (LVM)First initialize the physical volumes:
pvcreate /dev/sda4 /dev/sdb2
A full disk can be used as part of a physical volume, but beware that the pvcreate command will destroy any partition information on that disk.
Next create a volume group named lfs-lvm:
vgcreate lfs-lvm /dev/sda4 /dev/sdb2
The status of the volume group can be checked by running the command vgscan. Now create the logical volumes. Since there is about 3900 GB available, leave about 900 GB free for expansion. Note that the logical volume named mysql is larger than any physical disk.
lvcreate --name mysql --size 2500G lfs-lvm lvcreate --name home --size 500G lfs-lvm
Finally the logical volumes can be formatted and mounted. In this example, the jfs file system (jfsutils-1.1.15) is used for demonstration purposes.
mkfs -t ext4 /dev/lfs-lvm/home mkfs -t jfs /dev/lfs-lvm/mysql mount /dev/lfs-lvm/home /home mkdir -p /srv/mysql mount /dev/lfs-lvm/mysql /srv/mysql
It may be needed to activate those logical volumes, for them to
appear in /dev. They can all be
activated at the same time by issuing, as the root user:
vgchange -a y
A LVM logical volume can host a root filesystem, but requires
the use of an initramfs (initial RAM file system). The
initramfs proposed in the section called “About
initramfs” allows to pass the lvm volume in the
root= switch of the
kernel command line.
If not using an initramfs, there is a race condition in
systemd preventing mounting
logical volumes through /etc/fstab. You must create a “mount”
unit (see systemd.mount(5)) as in the following example, which
mounts the /home directory
automatically at boot:
cat > /etc/systemd/system/home.mount << EOF
[Unit]
Description=Mount the lvm volume /dev/lfs-lvm/home to /home
[Mount]
What=/dev/lfs-lvm/home
Where=/home
Type=ext4
Options=default
[Install]
WantedBy=multi-user.target
EOF
The name of the unit must be the name of the mount point with the `/' character replaced by `-', omitting the leading one.
Next the unit must be enabled with:
systemctl enable home.mount
For more information about LVM, see the LVM HOWTO and the lvm man pages. A good in-depth guide is available from RedHat®, although it makes sometimes reference to proprietary tools.
Last updated on
The storage technology known as RAID (Redundant Array of Independent Disks) combines multiple physical disks into a logical unit. The drives can generally be combined to provide data redundancy or to extend the size of logical units beyond the capability of the physical disks or both. The technology also allows for providing hardware maintenance without powering down the system.
The types of RAID organization are described in the RAID Wiki.
Note that while RAID provides protection against disk failures, it is not a substitute for backups. A file deleted is still deleted on all the disks of a RAID array. Modern backups are generally done via rsync-3.2.3.
There are three major types of RAID implementation: Hardware RAID, BIOS-based RAID, and Software RAID.
Hardware based RAID provides capability through proprietary hardware and data layouts. The control and configuration is generally done via firmware in conjunction with executable programs made available by the device manufacturer. The capabilities are generally supplied via a PCI card, although there are some instances of RAID components integrated in to the motherboard. Hardware RAID may also be available in a stand-alone enclosure.
One advantage of hardware-based RAID is that the drives are offered to the operating system as a logical drive and no operating system dependent configuration is needed.
Disadvantages include difficulties in transferring drives from one system to another, updating firmware, or replacing failed RAID hardware.
Some computers offter a hardware-like RAID implementation in the system BIOS. Sometime this is referred to as 'fake' RAID as the capabilites are generally incorporated into firmware without any hardware acceleration.
The advantages and disadvantages of BIOS-based RAID are generally the same as hardware RAID with the additional disadvantage that there is no hardware acceleration.
In some cases, BIOS-based RAID firmware is enabled by default (e.g. some DELL systems). If software RAID is desired, this option must be explicitly disabled in the BIOS.
Software based RAID is the most flexible form of RAID. It is easy to install and update and provides full capability on all or part of any drives available to the system. In BLFS, the RAID software is found in mdadm-4.1.
Configuring a RAID device is straight forward using
mdadm. Generally devices are
created in the /dev directory
as /dev/mdx where x is an integer.
The first step in creating a RAID array is to use
partitioning software such as fdisk or parted-3.4 to define
the partitions needed for the array. Usually, there will be
one partition on each drive participating in the RAID array,
but that is not strictly necessary. For this example, there
will be four disk drives: /dev/sda, /dev/sdb, /dev/sdc, and /dev/sdd. They will be partitioned as
follows:
Partition Size Type Use
sda1: 100 MB fd Linux raid auto /boot (RAID 1) /dev/md0
sda2: 10 GB fd Linux raid auto / (RAID 1) /dev/md1
sda3: 2 GB 83 Linux swap swap
sda4 300 GB fd Linux raid auto /home (RAID 5) /dev/md2
sdb1: 100 MB fd Linux raid auto /boot (RAID 1) /dev/md0
sdb2: 10 GB fd Linux raid auto / (RAID 1) /dev/md1
sdb3: 2 GB 83 Linux swap swap
sdb4 300 GB fd Linux raid auto /home (RAID 5) /dev/md2
sdc1: 12 GB fd Linux raid auto /usr/src (RAID 0) /dev/md3
sdc2: 300 GB fd Linux raid auto /home (RAID 5) /dev/md2
sdd1: 12 GB fd Linux raid auto /usr/src (RAID 0) /dev/md3
sdd2: 300 GB fd Linux raid auto /home (RAID 5) /dev/md2
In this arrangement, a separate boot partition is created as
the first small RAID array and a root filesystem as the
secong RAID array, both mirrored. The third partition is a
large (about 1TB) array for the /home directory. This provides an ability
to stripe data across multiple devices, improving speed for
both reading and writing large files. Finally, a fourth array
is created that concatenates two partitions into a larger
device.
All mdadm commands must be
run as the root user.
To create these RAID arrays the commands are:
/sbin/mdadm -Cv /dev/md0 --level=1 --raid-devices=2 /dev/sda1 /dev/sdb1
/sbin/mdadm -Cv /dev/md1 --level=1 --raid-devices=2 /dev/sda2 /dev/sdb2
/sbin/mdadm -Cv /dev/md3 --level=0 --raid-devices=2 /dev/sdc1 /dev/sdd1
/sbin/mdadm -Cv /dev/md2 --level=5 --raid-devices=4 \
/dev/sda4 /dev/sdb4 /dev/sdc2 /dev/sdd2
The devices created can be examined by device. For example,
to see the details of /dev/md1,
use /sbin/mdadm --detail
/dev/md1:
Version : 1.2
Creation Time : Tue Feb 7 17:08:45 2012
Raid Level : raid1
Array Size : 10484664 (10.00 GiB 10.74 GB)
Used Dev Size : 10484664 (10.00 GiB 10.74 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent
Update Time : Tue Feb 7 23:11:53 2012
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Name : core2-blfs:0 (local to host core2-blfs)
UUID : fcb944a4:9054aeb2:d987d8fe:a89121f8
Events : 17
Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
From this point, the partitions can be formated with the
filesystem of choice (e.g. ext3, ext4, xfsprogs-5.13.0,
reiserfsprogs-3.6.27, etc). The
formatted partitions can then be mounted. The /etc/fstab file can use the devices created
for mounting at boot time and the linux command line in
/boot/grub/grub.cfg can specify
root=/dev/md1.
The swap devices should be specified in the /etc/fstab file as normal. The kernel
normally stripes swap data across multiple swap files and
should not be made part of a RAID array.
For further options and management details of RAID devices,
refer to man
mdadm.
Additional details for monitoring RAID arrays and dealing with problems can be found at the Linux RAID Wiki.
Last updated on
The mdadm package contains administration tools for software RAID.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://www.kernel.org/pub/linux/utils/raid/mdadm/mdadm-4.1.tar.xz
Download MD5 sum: 51bf3651bd73a06c413a2f964f299598
Download size: 432 KB
Estimated disk space required: 4.9 MB (10 MB with tests)
Estimated build time: 0.1 SBU (tests take about an hour, only partially processor dependent)
A MTA
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/mdadm
Kernel versions in series 4.1 through 4.4.1 have a broken RAID implementation. Use a kernel with version at or above 4.4.2.
Enable the following options in the kernel configuration and recompile the kernel, if necessary. Only the RAID types desired are required.
Device Drivers --->
[*] Multiple devices driver support (RAID and LVM) ---> [CONFIG_MD]
<*> RAID support [CONFIG_BLK_DEV_MD]
[*] Autodetect RAID arrays during kernel boot [CONFIG_MD_AUTODETECT]
<*/M> Linear (append) mode [CONFIG_MD_LINEAR]
<*/M> RAID-0 (striping) mode [CONFIG_MD_RAID0]
<*/M> RAID-1 (mirroring) mode [CONFIG_MD_RAID1]
<*/M> RAID-10 (mirrored striping) mode [CONFIG_MD_RAID10]
<*/M> RAID-4/RAID-5/RAID-6 mode [CONFIG_MD_RAID456]Fix a build error introduced by gcc-7.1:
sed 's@-Werror@@' -i Makefile
Build mdadm by running the following command:
make
If you wish to run the tests, ensure that your kernel supports RAID and that a version of mdadm is not already running. As many as 9 out of 124 tests may fail.
The tests edit values in /proc and run tests on software raid devices. They shouldn't be run on systems with active software RAID devices.
Run the tests as the root
user:
./test --keep-going --logdir=test-logs --save-logs
Now, as the root user:
make BINDIR=/usr/sbin install
make everything: This optional target creates extra programs, particularly a statically-linked version of mdadm. This needs to be manually installed.
--keep-going: Run the
tests to the end, even if one or more tests fail.
--logdir=test-logs:
Defines the directory where test logs are saved.
--save-logs:
Instructs the test suite to save the logs.
--tests=:
Optional comma separated list of tests to be executed (all
tests, if this option is not passed).
<test1,test2,...>
Last updated on
The Ntfs-3g package contains a stable, read-write open source driver for NTFS partitions. NTFS partitions are used by most Microsoft operating systems. Ntfs-3g allows you to mount NTFS partitions in read-write mode from your Linux system. It uses the FUSE kernel module to be able to implement NTFS support in user space. The package also contains various utilities useful for manipulating NTFS partitions.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://tuxera.com/opensource/ntfs-3g_ntfsprogs-2021.8.22.tgz
Download MD5 sum: 90da343e78877d388eb34cefae6799ae
Download size: 1.3 MB
Estimated disk space required: 22 MB
Estimated build time: 0.2 SBU
fuse 2.x (this disables user mounts)
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/ntfs-3g
Enable the following options in the kernel configuration and recompile the kernel if necessary:
File systems --->
<*/M> FUSE (Filesystem in Userspace) support [CONFIG_FUSE_FS]Install Ntfs-3g by running the following commands:
./configure --prefix=/usr \
--disable-static \
--with-fuse=internal \
--docdir=/usr/share/doc/ntfs-3g-2021.8.22 &&
make
This package does not come with a test suite.
Now, as the root user:
make install && ln -sv ../bin/ntfs-3g /usr/sbin/mount.ntfs && ln -sv ntfs-3g.8 /usr/share/man/man8/mount.ntfs.8
If you want ordinary users to be able to mount NTFS
partitions you'll need to set mount.ntfs with the root user
ID. Note: it is probably unsafe to do this on a computer that
needs to be secure (like a server). As the root user:
chmod -v 4755 /usr/bin/ntfs-3g
--disable-static:
This switch prevents installation of static versions of the
libraries.
--with-fuse=internal:
This switch dynamically forces ntfs-3g to use an internal copy of the
fuse-2.x library. This is
required if you wish to allow users to mount NTFS partitions.
--disable-ntfsprogs: Disables
installation of various utilities used to manipulate NTFS
partitions.
ln -sv ../bin/ntfs-3g /usr/sbin/mount.ntfs: Creating /sbin/mount.ntfs makes mount default to using Ntfs-3g to mount NTFS partitions.
chmod -v 4755 /usr/bin/ntfs-3g: Making mount.ntfs setuid root allows non root users to mount NTFS partitions.
To mount a Windows partition at boot time, put a line like this in /etc/fstab:
/dev/sda1 /mnt/windows auto defaults 0 0
To allow users to mount a usb stick with an NTFS filesystem on it, put a line similar to this (change sdc1 to whatever a usb stick would be on your system) in /etc/fstab:
/dev/sdc1 /mnt/usb auto user,noauto,umask=0,utf8 0 0
In order for a user to be able to mount the usb stick, they
will need to be able to write to /mnt/usb, so as the root user:
chmod -v 777 /mnt/usb
|
is similar to ntfs-3g but uses the Fuse low-level interface |
|
|
is a symlink to mkntfs |
|
|
creates an NTFS file system |
|
|
is a symlink to lowntfs-3g |
|
|
mounts an NTFS filesystem |
|
|
is a symbolic link to ntfs-3g |
|
|
is an NTFS driver, which can create, remove, rename, move files, directories, hard links, and streams. It can also read and write files, including streams, sparse files and transparently compressed files. It can also handle special files like symbolic links, devices, and FIFOs; moreover it provides standard management of file ownership and permissions, including POSIX ACLs |
|
|
tests if an NTFS volume is mountable read only or read-write, and exits with a status value accordingly. The volume can be a block device or image file |
|
|
identifies files in a specified region of an NTFS volume |
|
|
copies a file to an NTFS volume |
|
|
fixes common errors and forces Windows to check an NTFS partition |
|
|
lists directory contents on an NTFS filesystem |
|
|
prints NTFS files and streams on the standard output |
|
|
clones an NTFS filesystem |
|
|
compares two NTFS filesystems and shows the differences |
|
|
dumps a file's attributes |
|
|
displays or changes the label on an ntfs file system |
|
|
resizes an NTFS filesystem without data loss |
|
|
recovers a deleted file from an NTFS volume |
|
|
contains the Ntfs-3g API functions |
Last updated on
The gptfdisk package is a set of programs for creation and maintenance of GUID Partition Table (GPT) disk drives. A GPT partitioned disk is required for drives greater than 2 TB and is a modern replacement for legacy PC-BIOS partitioned disk drives that use a Master Boot Record (MBR). The main program, gdisk, has an inteface similar to the classic fdisk program.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://downloads.sourceforge.net/gptfdisk/gptfdisk-1.0.8.tar.gz
Download MD5 sum: 74684c4eb0e6d5a1839e4bb0bba36fa2
Download size: 208 KB
Estimated disk space required: 2.5 MB
Estimated build time: less than 0.1 SBU (0.2 SBU for tests)
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/gptdisk
The gptfdisk package comes
with a rudimentary Makefile.
First we update it to provide a simple build and install
interface and fix the location of a header file. Install
gptfdisk by running the
following commands:
patch -Np1 -i ../gptfdisk-1.0.8-convenience-1.patch && sed -i 's|ncursesw/||' gptcurses.cc && sed -i 's|sbin|usr/sbin|' Makefile && make
To test the results, issue: make test.
Now, as the root user:
make install
patch -Np1 ...:
This patch modifies the Makefile file so that it provides an
“install” target.
Last updated on
The Parted package is a disk partitioning and partition resizing tool.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://ftp.gnu.org/gnu/parted/parted-3.4.tar.xz
Download (FTP): ftp://ftp.gnu.org/gnu/parted/parted-3.4.tar.xz
Download MD5 sum: 357d19387c6e7bc4a8a90fe2d015fe80
Download size: 1.7 MB
Estimated disk space required: 34 MB (additional 3 MB for the tests and additional 2 MB for optional PDF and Postscript documentation)
Estimated build time: 0.3 SBU (additional 2.5 SBU for the tests)
LVM2-2.03.13 (device-mapper, required if building udisks)
dosfstools-4.2, Pth-2.0.7, texlive-20210325 (or install-tl-unx), and Digest::CRC (for tests)
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/parted
Install Parted by running the following commands:
./configure --prefix=/usr --disable-static && make && make -C doc html && makeinfo --html -o doc/html doc/parted.texi && makeinfo --plaintext -o doc/parted.txt doc/parted.texi
If you have texlive-20210325 installed and wish to create PDF and Postcript documentation issue the following commands:
texi2pdf -o doc/parted.pdf doc/parted.texi && texi2dvi -o doc/parted.dvi doc/parted.texi && dvips -o doc/parted.ps doc/parted.dvi
To test the results, issue, as the root user:
make check
Many tests are skipped if not run as the root user.
Now, as the root user:
make install &&
install -v -m755 -d /usr/share/doc/parted-3.4/html &&
install -v -m644 doc/html/* \
/usr/share/doc/parted-3.4/html &&
install -v -m644 doc/{FAT,API,parted.{txt,html}} \
/usr/share/doc/parted-3.4
Install the optional PDF and Postscript documentation by
issuing the following command as the root user:
install -v -m644 doc/FAT doc/API doc/parted.{pdf,ps,dvi} \
/usr/share/doc/parted-3.4
--disable-static:
This switch prevents installation of static versions of the
libraries.
--disable-device-mapper: This
option disables device mapper support. Add this parameter if
you have not installed LVM2.
Last updated on
The reiserfsprogs package contains various utilities for use with the Reiser file system.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://www.kernel.org/pub/linux/kernel/people/jeffm/reiserfsprogs/v3.6.27/reiserfsprogs-3.6.27.tar.xz
Download MD5 sum: 90c139542725efc6da3a6b1709695395
Download size: 439 KB
Estimated disk space required: 13 MB
Estimated build time: 0.2 SBU
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/reiser
Enable the following option in the kernel configuration and recompile the kernel:
File systems --->
<*/M> Reiserfs support [CONFIG_REISERFS_FS]Install reiserfsprogs by running the following commands:
sed -i '/parse_time.h/i #define _GNU_SOURCE' lib/parse_time.c && autoreconf -fiv && ./configure --prefix=/usr && make
This package does not come with a test suite.
Now, as the root user:
make install
sed ...: Ensure a variable is defined for use with recent include files.
|
can sometimes help to solve problems with ReiserFS file systems. If it is called without options, it prints the super block of any ReiserFS file system found on the device |
|
|
creates a ReiserFS file system |
|
|
is used to check or repair a ReiserFS file system |
|
|
is used for tuning the ReiserFS journal. WARNING: Don't use this utility without first reading the man page thoroughly |
|
|
is used to resize an unmounted ReiserFS file system |
Last updated on
The smartmontools package contains utility programs (smartctl, smartd) to control/monitor storage systems using the Self-Monitoring, Analysis and Reporting Technology System (S.M.A.R.T.) built into most modern ATA and SCSI disks.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://downloads.sourceforge.net/smartmontools/smartmontools-7.2.tar.gz
Download MD5 sum: e8d134c69ae4959a05cb56b31172ffb1
Download size: 972 KB
Estimated disk space required: 24 MB
Estimated build time: 0.2 SBU
cURL-7.78.0 or Lynx-2.8.9rel.1 or Wget-1.21.1 (download tools), and GnuPG-2.2.29 (encrypted hard disks)
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/smartmontools
Install smartmontools by running the following commands:
./configure --prefix=/usr \
--sysconfdir=/etc \
--docdir=/usr/share/doc/smartmontools-7.2 &&
make
This package does not come with a test suite.
Now, as the root user:
make install
See the embedded comments in /etc/smartd.conf for detailed
instructions on customizing the smartd darmon.
Last updated on
The Sshfs package contains a filesystem client based on the SSH File Transfer Protocol. This is useful for mounting a remote computer that you have ssh access to as a local filesystem. This allows you to drag and drop files or run shell commands on the remote files as if they were on your local computer.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://github.com/libfuse/sshfs/releases/download/sshfs-3.7.2/sshfs-3.7.2.tar.xz
Download MD5 sum: 86dcc81a1381c3e6863c97e684501bb6
Download size: 52 KB
Estimated disk space required: 0.9 MB
Estimated build time: less than 0.1 SBU
Fuse-3.10.4, GLib-2.68.4, and OpenSSH-8.7p1.
docutils-0.17.1 (required to build the man page)
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/sshfs
Install Sshfs by running the following commands:
mkdir build &&
cd build &&
meson --prefix=/usr --buildtype=release .. &&
ninja
This package does not come with a test suite.
Now, as the root user:
ninja install
To mount an ssh server you need to be able to log into the server. For example, to mount your remote home folder to the local ~/examplepath (the directory must exist and you must have permissions to write to it):
sshfs example.com:/home/userid ~/examplepath
When you've finished work and want to unmount it again:
fusermount3 -u ~/example
You can also mount an sshfs
filesystem at boot by adding an entry similar to the
following in the /etc/fstab
file:
[email protected]:/path /media/path fuse.sshfs _netdev,IdentityFile=/home/userid/.ssh/id_rsa 0 0See man 1 sshfs and man 8 mount.fuse3 for all available mount options.
Last updated on
The xfsprogs package contains administration and debugging tools for the XFS file system.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://www.kernel.org/pub/linux/utils/fs/xfs/xfsprogs/xfsprogs-5.13.0.tar.xz
Download MD5 sum: 86777a5762f2e524bb9acfdead5a9045
Download size: 1.2 MB
Estimated disk space required: 50 MB
Estimated build time: 0.3 SBU (Using parallelism=4)
ICU-69.1 (for unicode name scanning in xfs_scrub)
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/xfs
Enable the following options in the kernel configuration and recompile the kernel:
File systems --->
<*/M> XFS filesystem support [CONFIG_XFS_FS]Install xfsprogs by running the following commands:
make DEBUG=-DNDEBUG \
INSTALL_USER=root \
INSTALL_GROUP=root
This package does not come with a test suite.
Now, as the root user:
make PKG_DOC_DIR=/usr/share/doc/xfsprogs-5.13.0 install &&
make PKG_DOC_DIR=/usr/share/doc/xfsprogs-5.13.0 install-dev &&
rm -rfv /usr/lib/libhandle.{a,la}
make DEBUG=-DNDEBUG: Turns off debugging symbols.
INSTALL_USER=root
INSTALL_GROUP=root: This sets the owner and group
of the installed files.
OPTIMIZER="...": Adding this
parameter to the end of the make command overrides the
default optimization settings.
|
simply exits with a zero status, since XFS partitions are checked at mount time |
|
|
constructs an XFS file system |
|
|
changes the parameters of an XFS file system |
|
|
prints block mapping for an XFS file |
|
|
copies the contents of an XFS file system to one or more targets in parallel |
|
|
for each directory argument, estimates the space that directory would take if it were copied to an XFS filesystem (does not cross mount points) |
|
|
is used to debug an XFS file system |
|
|
suspends access to an XFS file system |
|
|
applicable only to XFS filesystems, improves the organization of mounted filesystems, the reorganization algorithm operates on one file at a time, compacting or othewise improving the layout of the file extents (contiguous blocks of file data) |
|
|
expands an XFS file system |
|
|
is equivalent to invoking xfs_growfs, but specifying that no change to the file system is to be made |
|
|
is a debugging tool like xfs_db, but is aimed at examining the regular file I/O path rather than the raw XFS volume itself |
|
|
prints the log of an XFS file system |
|
|
restores an XFS metadump image to a filesystem image |
|
|
copies XFS filesystem metadata to a file |
|
|
creates an XFS file, padded with zeroes by default |
|
|
generates pathnames from inode numbers for an XFS file system |
|
|
is a utility for reporting and editing various aspects of filesystem quotas |
|
|
repairs corrupt or damaged XFS file systems |
|
|
copies a file to the real-time partition on an XFS file system |
|
|
checks and repairs the contents of a mounted XFS file system |
|
|
scrubs all mounted XFS file systems |
|
|
reports and controls free space usage in an XFS file system |
|
|
contains XFS-specific functions that provide a way to perform certain filesystem operations without using a file descriptor to access filesystem objects |
Last updated on
The efivar package provides tools and libraries to manipulate EFI variables.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://github.com/rhboot/efivar/releases/download/37/efivar-37.tar.bz2
Download MD5 sum: 9f067275c5f7aafdd75bfb364280ac9c
Download size: 108 KB
Estimated disk space required: 2.75 MB
Estimated build time: less than 0.1 SBU
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/efivar
First, apply a patch to fix an issue building with GCC 9 or later:
patch -Np1 -i ../efivar-37-gcc_9-1.patch
Build efivar with the following commands:
make CFLAGS="-O2 -Wno-stringop-truncation"
The test suite of this package is dangerous. Running it may trigger firmware bugs and make your system unusable without using some special hardware to reprogram the firmware.
Now, as the root user:
make install LIBDIR=/usr/lib
CFLAGS="-O2
-Wno-stringop-truncation": This option overrides
the default compiler flags to avoid a build failure.
LIBDIR=/usr/lib: This
option overrides the default library directory of the package
(/usr/lib64, which is not used
by LFS.)
Last updated on
The efibootmgr package provides tools and libraries to manipulate EFI variables.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://github.com/rhboot/efibootmgr/archive/17/efibootmgr-17.tar.gz
Download MD5 sum: 6ae315936d9bc8613b3a4cb8a4064128
Download size: 44 KB
Estimated disk space required: 592 KB
Estimated build time: less than 0.1 SBU
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/efibootmgr
At first, fix an outdated hotfix declaration causing compilation failure:
sed -e '/extern int efi_set_verbose/d' -i src/efibootmgr.c
Build efibootmgr with the following commands:
make EFIDIR=LFS EFI_LOADER=grubx64.efi
This package does not have a test suite.
Now, as the root user:
make install EFIDIR=LFS
EFIDIR=LFS: This
option specifies the distro's subdirectory name under
/boot/efi/EFI. The building
system of this package needs it to be set explicitly.
EFI_LOADER=grubx64.efi: This
option specifies the name of the default EFI boot loader. It
is set to match the EFI boot loader provided by GRUB .
Last updated on
The GRUB package provides GRand Unified Bootloader. In this page it will be built with UEFI support, which is not enabled for GRUB built in LFS.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://ftp.gnu.org/gnu/grub/grub-2.06.tar.xz
Download MD5 sum: cf0fd928b1e5479c8108ee52cb114363
Download size: 6.3 MB
Estimated disk space required: 185 MB
Estimated build time: 0.9 SBU
Unicode font data used to display GRUB menu
Download (HTTP): https://unifoundry.com/pub/unifont/unifont-13.0.06/font-builds/unifont-13.0.06.pcf.gz
Download MD5 sum: 4fbc33c8d8d25985f1bcdd4d28bc2420
Download size: 1.3 MB
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/grub-efi
First, install font data as the root user:
mkdir -pv /usr/share/fonts/unifont && gunzip -c ../unifont-13.0.06.pcf.gz > /usr/share/fonts/unifont/unifont.pcf
Unset any environment variables which may affect the build:
unset {C,CPP,CXX,LD}FLAGS
Don't try “tuning” this package with custom compilation flags: this package is a bootloader, with low-level operations in the source code which is likely to be broken by some aggressive optimizations.
Build GRUB with the following commands:
./configure --prefix=/usr \
--sysconfdir=/etc \
--disable-efiemu \
--enable-grub-mkfont \
--with-platform=efi \
--disable-werror &&
make
This package does not have a test suite providing meaningful results.
Now, as the root user:
make install && mv -v /etc/bash_completion.d/grub /usr/share/bash-completion/completions
--enable-grub-mkfont:
Build the tool named grub-mkfont to generate the
font file for the boot loader from the font data we've
installed.
If the recommended dependency FreeType-2.11.0 is not installed, it is possible to omit this option and build GRUB. However, if grub-mkfont is not built, or the unicode font data is not avaliable at the time GRUB is built, GRUB won't install any font for the boot loader. The GRUB boot menu will be displayed using a coarse font and the early stage of kernel initialization will be in “blind mode” — you can't see any kernel messages before the graphics card driver is initialized. It will be very difficult to diagnose some boot issues, especially if the graphics driver is built as module.
--with-platform=efi:
Ensures building GRUB with EFI enabled.
Using GRUB to make the LFS system bootable on UEFI platform will be discussed in Using GRUB to Set Up the Boot Process with UEFI.
See the page for GRUB in LFS book.
Last updated on
BLFS does not have the essential packages to support Secure Boot. To set up the boot process with GRUB for UEFI installed in BLFS, Secure Boot must be turned off from the configuration interface of the firmware. Read the documentation provided by the manufacturer of your system to find out how.
Ensure that an emergency boot disk is ready to “rescue” the system in case the
system becomes un-bootable. To make an emergency boot disk
with GRUB for an EFI based system, find a spare USB flash
drive and create a vfat file
system on it. Install dosfstools-4.2 first, then as the
root user:
The following command will erase all directories and files
in the partition. Make sure your USB flash drive contains
no data which will be needed, and change sdx1 to the device node
corresponding to the first partition of the USB flash
drive. Be careful not to overwrite your hard drive with a
typo!
mkfs.vfat /dev/sdx1
Still as the root user, use
the fdisk
utility to set the first parition of the USB flash drive to
be an “EFI
system” partition (change sdx to the device node
corresponding to your USB flash drive):
fdisk /dev/sdxWelcome to fdisk (util-linux 2.36.2). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Command (m for help):tSelected partition 1 Hex code or alias (type L to list all):efChanged type of partition 'Linux' to 'EFI (FAT-12/16/32)'. Command (m for help):wThe partition table has been altered. Calling ioctl() to re-read partition table. Syncing disks.
Still as the root user,
create a mount point for the EFI partition on the USB flash
drive and mount it:
mkdir -pv /mnt/rescue && mount -v -t vfat /dev/sdx1 /mnt/rescue
Install GRUB for EFI on the partition:
grub-install --removable --efi-directory=/mnt/rescue --boot-directory=/mnt/rescue/grub
Unmount the partition:
umount /mnt/rescue
Now the USB flash drive can be used as a emergency boot disk on x86-64 UEFI platform. It will boot the system and show the GRUB shell. Then you can type commands to boot your operating systems on the hard drive. To learn how to select the boot device, read the manual of your motherboard or laptop.
Enable the following options in the kernel configuration and recompile the kernel if necessary:
Processor type and features --->
[*] EFI runtime service support [CONFIG_EFI]
[*] EFI stub support [CONFIG_EFI_STUB]
Firmware Drivers --->
EFI (Extensible Firmware Interface) Support --->
< > EFI Variable Support via sysfs [CONFIG_EFI_VARS]
[*] Export efi runtime maps to sysfs [CONFIG_EFI_RUNTIME_MAP]
Enable the block layer --->
Partition Types --->
[*] Advanced partition selection [CONFIG_PARTITION_ADVANCED]
[*] EFI GUID Partition support [CONFIG_EFI_PARTITION]
Device Drivers --->
Graphics support --->
Frame buffer Devices --->
Support for frame buffer devices ---> [CONFIG_FB]
[*] EFI-based Framebuffer support [CONFIG_FB_EFI]
Console display driver support --->
[*] Framebuffer Console support [CONFIG_FRAMEBUFFER_CONSOLE]
File systems --->
Pseudo filesystems --->
<*/M> EFI Variable filesystem [CONFIG_EFIVAR_FS]The meaning of the configure options:
CONFIG_EFI_STUB
Although the EFI stub is designed to boot a kernel directly from the UEFI firmware (without a bootloader like GRUB), GRUB needs the kernel to be loaded to support the EFI handover protocol enabled by this option.
CONFIG_EFI_VARS
Don't use this deprecated option because of a 1024-byte
variable size limit. Its function is replaced by
CONFIG_EFIVAR_FS.
CONFIG_FB_EFI and
CONFIG_FRAMEBUFFER_CONSOLE
The combination of these two options allows the kernel to print debug messages (along with Tux logos) at the early stage of the boot process with UEFI.
On EFI based system, the bootloaders are installed in a
special FAT32 partition called an EFI System Partition (ESP). If
your system supports EFI, and a recent version of Linux
distribution or Windows is pre-installed, it's likely that
the ESP is already created. As the root user, list all the partitions on
your hard drive (replace sda with the device
corresponding to the appropriate hard drive):
fdisk -l /dev/sda
The “Type” column of the ESP should be
EFI System.
If the system or the hard drive is new, or it's a first time
install an UEFI booted OS on the system, the ESP may not
exist. In that case, create a new partition, make a
vfat file system on it, and
set the partition type to “EFI
system”. See the instructions for the
emergency boot device above as a reference.
Some (old) UEFI implementations may demand the ESP to be the first partition on the disk.
Now, as the root user, create
the mount point for the ESP, and mount it (replace
sda1 with the
device node corresponding to the ESP):
mkdir -pv /boot/efi && mount -v -t vfat /dev/sda1 /boot/efi
Add an entry for the ESP in /etc/fstab, so it will be mounted
automatically during system boot:
cat >> /etc/fstab << EOF
/dev/sda1 /boot/efi vfat defaults 0 1
EOF
The installation of GRUB on a UEFI platform requires that the
EFI Variable file system, efivarfs, to be mounted. As the
root user, mount it if it's
not already mounted:
mountpoint /sys/firmware/efi/efivars || mount -v -t efivarfs efivarfs /sys/firmware/efi/efivars
If the system is booted with UEFI and systemd, efivarfs will be mounted automatically.
However in the LFS chroot environment it still needs to be
mounted manually.
If the system is not booted with UEFI, the directory
/sys/firmware/efi will be
missing. In this case you should boot the system in UEFI
mode with the emergency boot disk created as above.
On UEFI based systems, GRUB works by installing an EFI
application (a special kind of executable) into /boot/efi/EFI/[id]/grubx64.efi, where
/boot/efi is the mount point of
the ESP, and [id] is replaced
with an identifier specified in the grub-install command line.
GRUB will create an entry in the EFI variables containing the
path EFI/[id]/grubx64.efi so the
EFI firmware can find grubx64.efi and load it.
grubx64.efi is very lightweight
(136 KB with GRUB-2.06~rc1) so it will not use much space in
the ESP. A typical ESP size is 100 MB (for Windows boot
manager, which uses about 50 MB in the ESP). Once
grubx64.efi loaded by the
firmware, it will load GRUB modules in the boot partition.
The default location is /boot/grub.
As the root user, install the
GRUB files into /boot/efi/EFI/LFS/grubx64.efi and
/boot/grub. Then set up the
boot entry in the EFI variables:
grub-install --bootloader-id=LFS --recheck
If the installation is successful, the output should be:
Installing for x86_64-efi platform.
Installation finished. No error reported.Issue efibootmgr to recheck the EFI boot configuration. An example of the output is:
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0005,0000,0002,0001,0003,0004
Boot0000* ARCH
Boot0001* UEFI:CD/DVD Drive
Boot0002* Windows Boot Manager
Boot0003* UEFI:Removable Device
Boot0004* UEFI:Network Device
Boot0005* LFS
Note that 0005 is the first in
the BootOrder, and Boot0005 is LFS. This means that on the next boot, the
version of GRUB installed by LFS will be used to boot the
system.
Generate /boot/grub/grub.cfg to
configure the boot menu of GRUB:
cat > /boot/grub/grub.cfg << EOF
# Begin /boot/grub/grub.cfg
set default=0
set timeout=5
insmod part_gpt
insmod ext2
set root=(hd0,2)
if loadfont /boot/grub/fonts/unicode.pf2; then
set gfxmode=auto
insmod all_video
terminal_output gfxterm
fi
menuentry "GNU/Linux, Linux 5.10.17-lfs-10.1" {
linux /boot/vmlinuz-5.10.17-lfs-10.1 root=/dev/sda2 ro
}
menuentry "Firmware Setup" {
fwsetup
}
EOF
(hd0,2), sda2, and 5.10.17-lfs-10.1 should be replaced to match
your configuration.
From GRUB's perspective, the files are relative to the
partition are used. If you used a separate /boot partition,
remove /boot from the above paths (to kernel and to
unicode.pf2). You will also
need to change the set root line to point to the boot
partition.
The Firmware Setup entry can be
used to enter the configuration interface provided by the
firmware (sometimes called “BIOS
configuration”).
Add a menu entry for Windows into grub.cfg:
cat >> /boot/grub/grub.cfg << EOF
# Begin Windows addition
menuentry "Windows 10" {
insmod fat
insmod chain
set root=(hd0,1)
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
}
EOF
(hd0,1) should be replaced with
the GRUB designated name for the ESP. The chainloader directive can be used to tell
GRUB to run another EFI executable, in this case the Windows
Boot Manager. You may put more usable tools in EFI executable
format (for example, an EFI shell) into the ESP and create
GRUB entries for them.
Last updated on
This chapter is referenced in the LFS book for those wishing to use other editors on their LFS system. You're also shown how some LFS installed programs benefit from being recompiled after GUI libraries have been installed.
Bluefish is a GTK+ text editor targeted towards programmers and web designers, with many options to write websites, scripts and programming code. Bluefish supports many programming and markup languages, and it focuses on editing dynamic and interactive websites.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://www.bennewitz.com/bluefish/stable/source/bluefish-2.2.12.tar.bz2
Download MD5 sum: 33dd8262c4d8a564a517f8c98c0cce19
Download size: 4.0 MB
Estimated disk space required: 69 MB
Estimated build time: 0.4 SBU
GTK+-2.24.33 or GTK+-3.24.30 (If both are installed, configure defaults to using GTK+ 3)
desktop-file-utils-0.26 (for updating the desktop database)
enchant-2.3.1 (for spell checking), Gucharmap-13.0.8, PCRE-8.45 and Jing
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/bluefish
Install Bluefish by running the following commands:
./configure --prefix=/usr --docdir=/usr/share/doc/bluefish-2.2.12 && make
This package does not come with a test suite.
Now, as the root user:
make install
This package installs icon files into the /usr/share/icons/hicolor hierarchy and
desktop files into the /usr/share/applications hierarchy. You
can improve system performance and memory usage by updating
/usr/share/icons/hicolor/icon-theme.cache
and /usr/share/applications/mimeinfo.cache.
To perform the update you must have desktop-file-utils-0.26 (for
the desktop cache) and issue the following commands as the
root user:
gtk-update-icon-cache -t -f --include-image-data /usr/share/icons/hicolor && update-desktop-database
Last updated on
Ed is a line-oriented text editor. It is used to create, display, modify and otherwise manipulate text files, both interactively and via shell scripts. Ed isn't something which many people use. It's described here because it can be used by the patch program if you encounter an ed-based patch file. This happens rarely because diff-based patches are preferred these days.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://ftp.gnu.org/gnu/ed/ed-1.17.tar.lz
Download (FTP): ftp://ftp.gnu.org/gnu/ed/ed-1.17.tar.lz
Download MD5 sum: 894748c9bbf35cb7c599f5317b1a8cdb
Download size: 68 KB
Estimated disk space required: 1.2 MB
Estimated build time: less than 0.1 SBU
libarchive-3.5.2 (for bsdtar)
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/ed
Install Ed by running the following commands:
./configure --prefix=/usr --bindir=/bin && make
To test the results, issue: make check.
Now, as the root user:
make install
Last updated on
The Emacs package contains an extensible, customizable, self-documenting real-time display editor.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://ftp.gnu.org/gnu/emacs/emacs-27.2.tar.xz
Download (FTP): ftp://ftp.gnu.org/gnu/emacs/emacs-27.2.tar.xz
Download MD5 sum: 4c3d9ff35b2ab2fe518dc7eb3951e128
Download size: 43 MB
Estimated disk space required: 620 MB
Estimated build time: 0.6 SBU (Using parallelism=4)
HarfBuzz-2.9.0, giflib-5.2.1, GnuTLS-3.7.2, jansson-2.13.1, and libtiff-4.3.0
X Window System, alsa-lib-1.2.5.1, Cairo-1.17.4, dbus-1.12.20, GConf-3.2.6, gobject-introspection-1.68.0, gsettings-desktop-schemas-40.0, GPM-1.20.7, GTK+-2.24.33 or GTK+-3.24.30, ImageMagick-7.1.0-4, Little CMS-2.12, libjpeg-turbo-2.1.1, libpng-1.6.37, librsvg-2.50.7, libxml2-2.9.12, MIT Kerberos V5-1.19.2, Valgrind-3.17.0, intlfonts, libungif, libotf, and m17n-lib - to correctly display such complex scripts as Indic and Khmer, and also for scripts that require Arabic shaping support (Arabic and Farsi), mailutils, and libXaw3d
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/emacs
First, work around a portability bug in glibc 2.34, which no longer defines SIGSTKSZ.
sed -e '/SIGSTKSZ/ s|^.*$|static max_align_t sigsegv_stack[\
(64 * 1024 + sizeof (max_align_t) - 1) / sizeof (max_align_t)];|' \
-i src/sysdep.c
Install Emacs by running the following commands:
./configure --prefix=/usr && make
This package does not come with a test suite. If make succeeds, you can test the result by running src/emacs -Q, which is the program that will be installed, with its auxiliary files. This should start and display the application opening screen.
Now, as the root user:
make install && chown -v -R root:root /usr/share/emacs/27.2
This package installs icon files into the /usr/share/icons/hicolor hierarchy and
you can improve system performance and memory usage by
updating /usr/share/icons/hicolor/index.theme. To
perform the update you must have GTK+-2.24.33 or GTK+-3.24.30
installed and issue the following command as the
root user:
gtk-update-icon-cache -qtf /usr/share/icons/hicolor
--with-imagemagick: Use this if
you have installed ImageMagick-7.1.0-4 and wish to
link against it.
--with-gif=no: Use this if you
have not installed giflib-5.2.1 or libungif.
--with-tiff=no: Use this if you
have not installed libtiff-4.3.0.
--with-gnutls=no: Use this if you
have not installed GnuTLS-3.7.2.
--without-harfbuzz: Use this if
you have not installed HarfBuzz-2.9.0.
--with-json=no: Use this if you
have not installed jansson-2.13.1.
Last updated on
The Gedit package contains a lightweight UTF-8 text editor for the GNOME Desktop.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://download.gnome.org/sources/gedit/40/gedit-40.1.tar.xz
Download (FTP): ftp://ftp.acc.umu.se/pub/gnome/sources/gedit/40/gedit-40.1.tar.xz
Download MD5 sum: e5cacbf3918f74dd2964fa4e174c82f3
Download size: 6.5 MB
Estimated disk space required: 55 MB (with tests)
Estimated build time: 0.3 SBU (using parallelism=4; with tests)
git-2.33.0, gsettings-desktop-schemas-40.0, gspell-1.8.4, gtksourceview4-4.8.1, itstool-2.0.6, libpeas-1.30.0, and tepl-6.00.0
Gvfs-1.48.1 (runtime), ISO Codes-4.7.0, and PyGObject-3.40.1 (Python 3 module)
GTK-Doc-1.33.2, Vala-0.52.5, and zeitgeist
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/gedit
Install Gedit by running the following commands:
mkdir build && cd build && meson --prefix=/usr --buildtype=release .. && ninja
To test the results, issue: ninja test.
Now, as the root user:
ninja install
If you installed the package to your system using a
“DESTDIR” method, /usr/share/glib-2.0/schemas/gschemas.compiled
was not updated/created. Create (or update) the file using
the following command as the root user:
glib-compile-schemas /usr/share/glib-2.0/schemas
--buildtype=release:
Specify a buildtype suitable for stable releases of the
package, as the default may produce unoptimized binaries.
-Duser_documentation=false:
This switch disables generating the user documentation. Omit
this switch if you have GTK-Doc-1.33.2 installed and wish
to generate the user documentation.
-Dgtk_doc=true: Use this option
to build the reference manual (needs GTK-Doc-1.33.2).
Last updated on
JOE (Joe's own editor) is a small text editor capable of emulating WordStar, Pico, and Emacs.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://downloads.sourceforge.net/joe-editor/joe-4.6.tar.gz
Download MD5 sum: 9017484e6116830d846678b625ea5c43
Download size: 1.8 MB
Estimated disk space required: 22 MB
Estimated build time: 0.2 SBU
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/joe
Install JOE by running the following commands:
./configure --prefix=/usr \
--sysconfdir=/etc \
--docdir=/usr/share/doc/joe-4.6 &&
make
This package does not come with a test suite.
Now, as the root user:
make install &&
install -vm 755 joe/util/{stringify,termidx,uniproc} /usr/bin
|
is a symbolic link to joe used to launch Emacs emulation mode |
|
|
is a small text editor capable of emulating WordStar, Pico, and Emacs |
|
|
is a symbolic link to joe used to launch Pico emulation mode |
|
|
is a symbolic link to joe used to launch WordStar emulation mode |
|
|
is a symbolic link to joe that restricts JOE to editing only files which are specified on the command-line |
|
|
is a program used by joe to convert rc and .jsf files into a C file (see /usr/share/doc/joe-4.6/util/README) |
|
|
is a program used by joe to generate the termcap index file (see /usr/share/doc/joe-4.6/util/README) |
|
|
is a program used by joe to generate joe's unicode database file unicat.c from Blocks.txt CaseFolding.txt EastAsianWidth.txt and UnicodeData.txt (find them at /usr/share/doc/joe-4.6/util; see usr/share/doc/joe-4.6/util/README) |
Last updated on
The Kate package contains an advanced KF5 based graphical text editor.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://download.kde.org/stable/release-service/21.08.0/src/kate-21.08.0.tar.xz
Download MD5 sum: 5c04c4b3f078c08536fed1bd862934bd
Download size: 6.9 MB
Estimated disk space required: 99 MB
Estimated build time: 1.0 SBU (using parallelism=4)
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/kate5
Install Kate by running the following commands:
mkdir build &&
cd build &&
cmake -DCMAKE_INSTALL_PREFIX=$KF5_PREFIX \
-DCMAKE_BUILD_TYPE=Release \
-DBUILD_TESTING=OFF \
-Wno-dev .. &&
make
This package does not come with a test suite.
Now, as the root user:
make install
Last updated on
Mousepad is a simple GTK+ 3 text editor for the Xfce desktop environment.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://archive.xfce.org/src/apps/mousepad/0.5/mousepad-0.5.6.tar.bz2
Download MD5 sum: 96fa4d1cb7a522104d7dd41943c8b382
Download size: 896 KB
Estimated disk space required: 16 MB
Estimated build time: 0.1 SBU
DConf-0.40.0 (runtime) and dbus-glib-0.112
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/mousepad
Install Mousepad by running the following commands:
./configure --prefix=/usr --enable-keyfile-settings && make
This package does not come with a test suite.
Now, as the root user:
make install
--enable-keyfile-settings: Use
the GSettings keyfile backend rather than the default
DConf-0.40.0.
Last updated on
The Nano package contains a small, simple text editor which aims to replace Pico, the default editor in the Pine package.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://www.nano-editor.org/dist/v5/nano-5.8.tar.xz
Download MD5 sum: d2249e3dd108c830df00efd7c1b79d86
Download size: 1.4 MB
Estimated disk space required: 23 MB
Estimated build time: 0.2 SBU
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/Nano
Install Nano by running the following commands:
./configure --prefix=/usr \
--sysconfdir=/etc \
--enable-utf8 \
--docdir=/usr/share/doc/nano-5.8 &&
make
This package does not come with a test suite.
Now, as the root user:
make install &&
install -v -m644 doc/{nano.html,sample.nanorc} /usr/share/doc/nano-5.8
--enable-utf8: This
switch enables unicode support in Nano.
Example configuration (create as a system-wide /etc/nanorc or a personal ~/.nanorc file)
set autoindent
set constantshow
set fill 72
set historylog
set multibuffer
set nohelp
set positionlog
set quickblank
set regexp
set suspend
Check the sample.nanorc file
in the installed documentation directory. It includes color
configurations and has some documentation included in the
comments.
Syntax highlighting is provided for several file types, in
/usr/share/nano/ directory.
E.g., for shell scripts, you can insert include /usr/share/nano/sh.nanorc in the
personal or global configuration file. If you wish
highlighting for all supported files, use include /usr/share/nano/*.nanorc. This
include does not descend into the extra directory. Move required files one
level up.
Last updated on
The Vim package, which is an abbreviation for VI IMproved, contains a vi clone with extra features as compared to the original vi.
The default LFS instructions install vim as a part of the base system. If you would prefer to link vim against X, you should recompile vim to enable GUI mode. There is no need for special instructions since X support is automatically detected.
The version of vim changes daily. The get the latest version, go to https://github.com/vim/vim/releases.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://anduin.linuxfromscratch.org/BLFS/vim/vim-8.2.3337.tar.gz
Download MD5 sum: e0325a4988b1b99b9c2e46fa853c1980
Download size: 15 MB
Estimated disk space required: 109 MB (add 61 MB for tests)
Estimated build time: 0.3 SBU (with parallelism=4; add 2.1 SBU for tests)
X Window System and GTK+-3.24.30
GPM-1.20.7, Lua-5.4.3, rsync-3.2.3, and Ruby-3.0.2
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/vim
If you recompile Vim to
link against X and your
X libraries are not on the
root partition, you will no longer have an editor for use
in emergencies. You may choose to install an additional
editor, not link Vim
against X, or move the
current vim
executable to the /bin
directory under a different name such as vi.
Install Vim by running the following commands:
If you intend to run the tests and have not installed Xorg in /usr, append LDFLAGS='-L$XORG_PREFIX/lib' to the configure line below.
echo '#define SYS_VIMRC_FILE "/etc/vimrc"' >> src/feature.h &&
echo '#define SYS_GVIMRC_FILE "/etc/gvimrc"' >> src/feature.h &&
./configure --prefix=/usr \
--with-features=huge \
--enable-gui=gtk3 \
--with-tlib=ncursesw &&
make
If the global configuration file /etc/vimrc references the VIMRUNTIME environment variable, some tests
may complain about being unable to find the corresponding
directory and wait for user input. If this is the case,
this file should be saved and removed before running the
tests.
To test the results, issue: make -j1 test. Even if one
of the tests fails to produce the file test.out in src/testdir, the remaining tests will still
be executed. If all goes well, the log will report
ALL DONE. Some tests labelled as
“flaky” may fail occasionally and
can be ignored. The tests are known to fail if the output is
redirected to a file.
Some color tests expect to be executed under the xterm terminal emulator.
Now, as the root user:
make install
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-8.2.3337, making it
consistent with the location of documentation for other
packages:
ln -snfv ../vim/vim82/doc /usr/share/doc/vim-8.2.3337
If you wish to update the runtime files, issue the following command (requires rsync-3.2.3):
rsync -avzcP --exclude="/dos/" --exclude="/spell/" \
ftp.nluug.nl::Vim/runtime/ ./runtime/
To install the runtime files and regenerate the tags file, as the root user issue:
make -C src installruntime && vim -c ":helptags /usr/share/doc/vim-8.2.3337" -c ":q"
--with-features=huge:
This switch enables all the additional features available in
Vim, including support for
multibyte characters.
--with-tlib=ncursesw:
This switch forces Vim to link against the libncursesw library.
--enable-gui=no: This will
prevent compilation of the GUI. Vim will still link against X, so that some features such as the
client-server model or the x11-selection (clipboard) are
still available.
--without-x: If you prefer not to
link Vim against
X, use this switch.
--enable-luainterp, --enable-perlinterp, --enable-python3interp=dynamic, --enable-tclinterp --with-tclsh=tclsh,
--enable-rubyinterp: These
options include the Lua, Perl, Python3, Tcl, or Ruby
interpreters that allow using other application code in
vim scripts. All the
--enable-... options can accept
=dynamic to dynamically load the
interpreter when needed. This is required for Python 3 to prevent segmentation faults.
For tcl, it is necessary to
indicate the name of the tclsh executable, since
configure only
searches versioned names with old versions.
Vim has an integrated spell checker which you can enable by issuing the following in a vim window:
:setlocal spell spelllang=ruThis setting will enable spell checking for the Russian language for the current session.
By default, Vim only
installs spell files for the English language. If a spell
file is not available for a language, then Vim will call the $VIMRUNTIME/plugin/spellfile.vim plugin
and will try to obtain the *.spl and optionally *.sug from
the vim ftp server, by using the $VIMRUNTIME/plugin/netrwPlugin.vim
plugin.
Alternatively you can manually download the *.spl and *.sug
files from: ftp://ftp.vim.org/pub/vim/runtime/spell/
and save them to ~/.vim/spell
or in /usr/share/vim/vim82/spell/.
To find out what's new in Vim-8.2.3337 issue the following command:
:help version-8.2.3337For additional information on setting up Vim configuration files, see The vimrc Files and http://vim.wikia.com/wiki/Example_vimrc.
A list of the reinstalled files, along with their short descriptions can be found in the LFS Vim Installation Instructions.
Last updated on
We are all familiar with the Bourne Again SHell, but there are two other user interfaces that are considered useful modern shells – the Berkeley Unix C shell and the Korn shell. This chapter installs packages compatible with these additional shell types.
Dash is a POSIX compliant
shell. It can be installed as /bin/sh or as the default shell
for either root or a second
user with a userid of 0. It depends on fewer libraries than
the Bash shell and is
therefore less likely to be affected by an upgrade problem or
disk failure. Dash is also
useful for checking that a script is completely compatible
with POSIX syntax.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): http://gondor.apana.org.au/~herbert/dash/files/dash-0.5.11.4.tar.gz
Download MD5 sum: 39d6fb8ab465be82a2276060bc3759d3
Download size: 236 KB
Estimated disk space required: 2.7 MB
Estimated build time: less than 0.1 SBU
libedit (command line editor library)
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/dash
Install Dash by running the following commands:
./configure --bindir=/bin --mandir=/usr/share/man && make
This package does not come with a test suite.
Now, as the root user:
make install
If you would like to make dash the default
sh, recreate
the /bin/sh symlink as the
root user:
If you create the symbolic link from dash to sh, you will need to reset the link to bash to build LFS.
ln -svf dash /bin/sh
--bindir=/bin: This
parameter places the dash binary into the root
filesystem.
--with-libedit: To compile
Dash with libedit support.
Last updated on
The Tcsh package contains “an enhanced but completely compatible version of the Berkeley Unix C shell (csh)”. This is useful as an alternative shell for those who prefer C syntax to that of the bash shell, and also because some programs require the C shell in order to perform installation tasks.
This package is known to build and work properly using an LFS-11.0 platform.
Download (FTP): ftp://ftp.astron.com/pub/tcsh/tcsh-6.22.04.tar.gz
Download MD5 sum: fa2b347fa9ae866eb036e6e4bb85fe1a
Download size: 992 KB
Estimated disk space required: 12 MB (with tests)
Estimated build time: 0.2 SBU (with tests)
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/tcsh
Install Tcsh by running the following commands:
./configure --prefix=/usr --bindir=/bin && make && sh ./tcsh.man2html
To test the results, issue: make check.
Now, as the root user:
make install install.man && ln -v -sf tcsh /bin/csh && ln -v -sf tcsh.1 /usr/share/man/man1/csh.1 && install -v -m755 -d /usr/share/doc/tcsh-6.22.04/html && install -v -m644 tcsh.html/* /usr/share/doc/tcsh-6.22.04/html && install -v -m644 FAQ /usr/share/doc/tcsh-6.22.04
--bindir=/bin: This
installs the tcsh program in
/bin instead of /usr/bin.
sh ./tcsh.man2html: This creates HTML documentation from the formatted man page.
ln -v -sf tcsh
/bin/csh: The FHS states that if there is a
C shell installed, there
should be a symlink from /bin/csh to it. This creates that symlink.
There are numerous configuration files for the C shell.
Examples of these are /etc/csh.cshrc, /etc/csh.login, /etc/csh.logout, ~/.tcshrc, ~/.cshrc, ~/.history, ~/.cshdirs, ~/.login, and ~/.logout. More information on these
files can be found in the tcsh(1) man page.
Update /etc/shells to include
the C shell program names (as the root user):
cat >> /etc/shells << "EOF"
/bin/tcsh
/bin/csh
EOF
The following ~/.cshrc
provides two alternative colour prompts and coloured
ls output. If
you prefer a global modification, issue the command as the
root user, replacing
~/.cshrc by /etc/csh.cshrc.
cat > ~/.cshrc << "EOF"
# Original at:
# https://www.cs.umd.edu/~srhuang/teaching/code_snippets/prompt_color.tcsh.html
# Modified by the BLFS Development Team.
# Add these lines to your ~/.cshrc (or to /etc/csh.cshrc).
# Colors!
set red="%{\033[1;31m%}"
set green="%{\033[0;32m%}"
set yellow="%{\033[1;33m%}"
set blue="%{\033[1;34m%}"
set magenta="%{\033[1;35m%}"
set cyan="%{\033[1;36m%}"
set white="%{\033[0;37m%}"
set end="%{\033[0m%}" # This is needed at the end...
# Setting the actual prompt. Two separate versions for you to try, pick
# whichever one you like better, and change the colors as you want.
# Just don't mess with the ${end} guy in either line... Comment out or
# delete the prompt you don't use.
set prompt="${green}%n${blue}@%m ${white}%~ ${green}%%${end} "
set prompt="[${green}%n${blue}@%m ${white}%~ ]${end} "
# This was not in the original URL above
# Provides coloured ls
alias ls ls --color=always
# Clean up after ourselves...
unset red green yellow blue magenta cyan yellow white end
EOF
Last updated on
The zsh package contains a command interpreter (shell) usable as an interactive login shell and as a shell script command processor. Of the standard shells, zsh most closely resembles ksh but includes many enhancements.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://www.zsh.org/pub/zsh-5.8.tar.xz
Download MD5 sum: e02a5428620b3dd268800c7843b3dd4d
Download size: 3.0 MB
Estimated disk space required: 72 MB (includes documentation and tests)
Estimated build time: 1.3 SBU (Using parallelism=4; includes documentation and tests)
Optional Documentation: https://www.zsh.org/pub/zsh-5.8-doc.tar.xz
Documentation MD5 sum: ef8514401a81bb1a4c4b655ebda8a1a2
Documentation download size: 3.0 MB
When there is a new zsh release, the old files shown above are moved to a new server directory: https://www.zsh.org/pub/old/.
libcap-2.53 with PAM, PCRE-8.45, and Valgrind-3.17.0,
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/zsh
If you downloaded the optional documentation, unpack it with the following command:
tar --strip-components=1 -xvf ../zsh-5.8-doc.tar.xz
Install zsh by running the following commands:
./configure --prefix=/usr \
--sysconfdir=/etc/zsh \
--enable-etcdir=/etc/zsh &&
make &&
makeinfo Doc/zsh.texi --plaintext -o Doc/zsh.txt &&
makeinfo Doc/zsh.texi --html -o Doc/html &&
makeinfo Doc/zsh.texi --html --no-split --no-headers -o Doc/zsh.html
If you have texlive-20210325 installed, you can build PDF format of the documentation by issuing the following command:
texi2pdf Doc/zsh.texi -o Doc/zsh.pdf
To test the results, issue: make check.
Now, as the root user:
make install &&
make infodir=/usr/share/info install.info &&
install -v -m755 -d /usr/share/doc/zsh-5.8/html &&
install -v -m644 Doc/html/* /usr/share/doc/zsh-5.8/html &&
install -v -m644 Doc/zsh.{html,txt} /usr/share/doc/zsh-5.8
If you downloaded the optional documentation, install it by
issuing the following commands as the root user:
make htmldir=/usr/share/doc/zsh-5.8/html install.html && install -v -m644 Doc/zsh.dvi /usr/share/doc/zsh-5.8
If you built the PDF format of the documentation, install it
by issuing the following command as the root user:
install -v -m644 Doc/zsh.pdf /usr/share/doc/zsh-5.8
--sysconfdir=/etc/zsh
and --enable-etcdir=/etc/zsh: These
parameters are used so that all the zsh configuration files are consolidated
into the /etc/zsh directory.
Omit these parameters if you wish to retain historical
compatibility by having all the files located in the
/etc directory.
--enable-cap: This option enables
POSIX capabilities.
--disable-gdbm: This option
disables the use of the GDBM
library.
--enable-pcre: This option allows
zsh to use the PCRE regular
expression library in shell builtins.
There are a whole host of configuration files for
zsh including /etc/zsh/zshenv, /etc/zsh/zprofile, /etc/zsh/zshrc, /etc/zsh/zlogin and /etc/zsh/zlogout. You can find more
information on these in the zsh(1) and related manual pages.
The first time zsh is executed, you will be prompted by
messages asking several questions. The answers will be used
to create a ~/.zshrc file. If
you wish to run these questions again, run zsh
/usr/share/zsh/5.8/functions/zsh-newuser-install
-f.
There are several built-in advanced prompts. In the
zsh shell,
start advanced prompt support with autoload -U promptinit,
then promptinit. Available
prompt names are listed with prompt -l. Select a
particular one with prompt
<prompt-name>.
Display all available prompts with prompt -p. Except for the
list and display commands above, you can insert the other
ones in ~/.zshrc to be
automatically executed at shell start, with the prompt you
chose.
Last updated on
Virtualization allows running a complete operating system, or virtual machine (VM), within another operating environment as a task. There are several commercial and open source environments that either emulate another processor or utilize the hardware virtualization features of the host processor.
qemu is a full virtualization solution for Linux on x86 hardware containing virtualization extensions (Intel VT or AMD-V).
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://download.qemu-project.org/qemu-6.1.0.tar.xz
Download MD5 sum: 47f776c276a24f42108ba512a2aa3013
Download size: 106 MB
Estimated disk space required: 1.9 GB
Estimated build time: 1.2 SBU (using parallelism=4; add 0.3 SBU for tests)
GLib-2.68.4, and X Window System
alsa-lib-1.2.5.1 and SDL2-2.0.16
Depending on the sound system, various packages in ALSA-1.2.5, Python-3.9.6, PulseAudio-15.0, BlueZ-5.61, cURL-7.78.0, Cyrus SASL-2.1.27, GnuTLS-3.7.2, GTK+-2.24.33, GTK+-3.24.30, libusb-1.0.24, libgcrypt-1.9.4, libssh2-1.9.0, LZO-2.10, Nettle-3.7.3, Mesa-21.2.1, SDL-1.2.15, VTE-0.64.2 or Vte-0.28.2, and libcacard
sphinx with the sphinx-rtd-theme theme
This optional dependencies list is not comprehensive. See the output of ./configure --help for a more complete list.
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/qemu
Before building qemu, check to see if your processor supports Virtualization Technology (VT):
egrep '^flags.*(vmx|svm)' /proc/cpuinfo
If you get any output, you have VT technology (vmx for Intel processors and svm for AMD processors). You then need to go into your system BIOS and ensure it is enabled. After enabing, reboot back to your LFS instance.
Enable the following options in the kernel configuration and recompile the kernel if necessary:
[*] Virtualization: ---> [CONFIG_VIRTUALIZATION]
<*/M> Kernel-based Virtual Machine (KVM) support [CONFIG_KVM]
<*/M> KVM for Intel (and compatible) processors support [CONFIG_KVM_INTEL]
<*/M> KVM for AMD processors support [CONFIG_KVM_AMD]The Intel or AMD settings are not both required, but the one matching your system processor is required.
To use the “bridge” network device, as explained below, check that bridge-utils-1.7.1 is installed and the following options in the kernel configuration are enabled:
[*] Networking support ---> [CONFIG_NET]
Networking options --->
<*/M> 802.1d Ethernet Bridging [CONFIG_BRIDGE]
Device Drivers --->
[*] Network device support ---> [CONFIG_NETDEVICES]
<*/M> Universal TUN/TAP device driver support [CONFIG_TUN]Add any users that might use the KVM device to that group:
usermod -a -G kvm <username>
Install qemu by running the following commands:
Qemu is capable of running many targets. The build process
is also capable of building multiple targets at one time in
a comma delimited list assigned to --target-list. Run ./configure --help to get
a complete list of available targets.
if [ $(uname -m) = i686 ]; then
QEMU_ARCH=i386-softmmu
else
QEMU_ARCH=x86_64-softmmu
fi
mkdir -vp build &&
cd build &&
../configure --prefix=/usr \
--sysconfdir=/etc \
--localstatedir=/var \
--target-list=$QEMU_ARCH \
--audio-drv-list=alsa \
--docdir=/usr/share/doc/qemu-6.1.0 &&
unset QEMU_ARCH &&
make
qemu uses ninja as a subprocess when building. To run the tests, issue: ninja test.
Now, as the root user:
make install
You will also need to add an Udev rule so that the KVM device gets correct permissions:
cat > /lib/udev/rules.d/65-kvm.rules << "EOF"
KERNEL=="kvm", GROUP="kvm", MODE="0660"
EOF
Change the permissions and ownership of a helper script, which is needed when using the “bridge” network device (see below):
chgrp kvm /usr/libexec/qemu-bridge-helper && chmod 4750 /usr/libexec/qemu-bridge-helper
For convenience you may want to create a symbolic link to run the installed program. For instance:
ln -sv qemu-system-`uname -m` /usr/bin/qemu
--audio-drv-list=alsa: This
switch sets the audio driver to ALSA. See below for enabling
other audio drivers.
--audio-drv-list=pa: This switch
sets the audio driver to pulseaudio. For other drivers see
the --audio-drv-list list in configure's help output.
The default audio driver is OSS. To enable support for both
alsa and pulseaudio, use --audio-drv-list=alsa,pa.
Since using qemu means using a virtual computer, the steps to
set up the virtual machine are in close analogy with those to
set up a real computer. You'll need to decide about CPU,
memory, disk, USB devices, network card(s), screen size, etc.
Once the “hardware” is decided, you'll have
for example to choose how to connect the machine to internet,
and/or to install an OS. In the following, we show basic ways
of performing those steps. But qemu is much more than this,
and it is strongly advised to read the qemu documentation in
/usr/share/doc/qemu-6.1.0/qemu-doc.html.
It is standard practice to name the computer running qemu “host” and the emulated machine running under qemu the “guest”. We'll use those notations in the following.
The following instructions assume the optional symbolic
link, qemu, has been created.
Additionally, qemu must be run from an
X Window System based terminal (either locally or over
ssh).
A virtual disk may be set up in the following way:
VDISK_SIZE=50GVDISK_FILENAME=vdisk.imgqemu-img create -f qcow2 $VDISK_FILENAME $VDISK_SIZE
The virtual disk size and filename should be adjusted as desired. The actual size of the file will be less than specified, but will expand as needed, so it is safe to put a high value.
To install an operating system, download an iso image from
your preferred Linux distribution. For the purposes of this
example, we'll use Fedora-16-x86_64-Live-LXDE.iso in the
current directory. Run the following:
qemu -enable-kvm \
-drive file=$VDISK_FILENAME \
-cdrom Fedora-16-x86_64-Live-LXDE.iso \
-boot d \
-m 1G
Follow the normal installation procedures for the chosen
distribution. The -boot option specifies the boot
order of drives as a string of drive letters. Valid drive
letters are: a, b (floppy 1 and 2), c (first hard disk), d
(first CD-ROM). The -m option is the amount of
memory to use for the virtual machine. The choice depends on
the load of the host. Modern distributions should be
comfortable with 1GB. The -enable-kvm option allows
hardware acceleration. Without this switch, the emulation is
much slower.
The virtual machine hardware is defined by the qemu command line. An example command is given below:
qemu -enable-kvm \
-smp 4 \
-cpu host \
-m 1G \
-drive file=$VDISK_FILENAME \
-cdrom grub-img.iso \
-boot order=c,once=d,menu=on \
-net nic,netdev=net0 \
-netdev user,id=net0 \
-device ac97 \
-vga std \
-serial mon:stdio \
-name "fedora-16"
-enable-kvm: enable
full KVM virtualization support. On some hardware, it may be
necessary to add the undocumented -machine smm=off option in order to enable
KVM.
-smp <N>:
enable symmetric multiprocessing with <N> CPUs.
-cpu <model>:
simulate CPU <model>. the list of supported models can
be obtained with -cpu help.
-drive
file=<filename>: defines a virtual disk
whose image is stored in <filename>.
-cdrom grub-img.iso:
defines an iso formated file to use as a cdrom. Here we use a
grub rescue disk, which may turn handy when something goes
wrong at boot time.
-boot
order=c,once=d,menu=on: defines the boot order
for the virtual BIOS.
-net
nic,netdev=<netid>: defines a network card
connected to the network device with id <netid>.
-netdev
user,id=<netid>: defines the network
“user” device. This is a virtual
local network with addresses 10.0.2.0/24, where the host has
address 10.0.2.2 and acts as a gateway to internet, and with
a name server at address 10.0.2.3, and an smb server at
address 10.0.2.4. A builtin DHCP server can allocate
addresses between 10.0.2.15 and 10.0.2.31.
-soundhw
<model>: defines the soundcard model. The
list may be obtained with -soundhw
help.
-vga <type>:
defines the type of vga card to emulate.
-serial mon:stdio:
sends the serial port of the guest (/dev/ttyS0 on linux guests), multiplexed
with the qemu monitor, to the standard input and output of
the qemu process.
-name <name>:
sets the name of the guest. This name is displayed in the
guest window caption. It may be useful if you run several
guests at the same time.
It may happen that the guest window displayed by qemu does not correspond to the full capability of the emulated vga card. For example, the vmware card is 1600x900 capable, but only 1024x768 is displayed by default. A suitable Xorg configuration on the guest allows to use the full size (Note that the Xorg video driver to use is Xorg VMware Driver-13.3.0):
cat > /usr/share/X11/xorg.conf.d/20-vmware.conf << "EOF"
Section "Monitor"
Identifier "Monitor0"
# cvt 1600 900
# 1600x900 59.95 Hz (CVT 1.44M9) hsync: 55.99 kHz; pclk: 118.25 MHz
Modeline "1600x900" 118.25 1600 1696 1856 2112 900 903 908 934 -hsync +vsync
Option "PreferredMode" "1600x900"
HorizSync 1-200
VertRefresh 1-200
EndSection
Section "Device"
Identifier "VMware SVGA II Adapter"
Option "Monitor" "default"
Driver "vmware"
EndSection
Section "Screen"
Identifier "Default Screen"
Device "VMware SVGA II Adapter"
Monitor "Monitor0"
SubSection "Display"
Depth 24
Modes "1600x900" "1440x900" "1366x768" "1280x720" "800x480"
EndSubSection
EndSection
EOF
New sizes will be available besides the native ones. You need to restart X in order to have the new sizes available.
The below solution for networking allows the guest to access
the local network through the host (and possibly to access
internet through the local routers), but the converse is not
true. Not even the host can access the guest, unless port
forwarding is enabled. And in the case several guests are
running, they cannot communicate with each other. Other
network devices can be used for this purpose. For example,
there is the “socket” device, which allows
several guests to share a common virtual network. In the
following, we describe in more details how to set up the
“bridge” device, which allows the
guests to appear as if connected to the local network. All
the commands below should be run as the root user.
Allow the host to forward IP packets:
sysctl -w net.ipv4.ip_forward=1
To make this permanent, add the command to /etc/sysctl.d/60-net-forward.conf:
cat >> /etc/sysctl.d/60-net-forward.conf << EOF
net.ipv4.ip_forward=1
EOF
Set up a required configuration file:
install -vdm 755 /etc/qemu && echo allow br0 > /etc/qemu/bridge.conf
In the command above, replace the switch -netdev user,... with
-netdev
bridge,id=net0.
|
Converts files from elf to dmp format |
|
|
is a test tool for the qemu EDID generator |
|
|
implements support for QMP (QEMU Monitor Protocol) commands and events that terminate and originate respectively within the guest using an agent built as part of QEMU |
|
|
provides commands to manage QEMU disk images |
|
|
is a diagnostic and manipulation program for (virtual) memory media. It is still at an early stage of development |
|
|
generates qemu reverse keymaps from xkb keymaps, which can be used with the qemu "-k" command line switch |
|
|
exports Qemu disk images using the QEMU Disk Network Block Device (NBD) protocol |
|
|
Implements the persistent reservation helper for QEMU |
|
|
allows to modify disk images using the QEMU Monitor Protocol (QMP) without running a VM |
|
|
is the QEMU PC System emulator |
Last updated on
Libraries contain code which is often required by more than one program. This has the advantage that each program doesn't need to duplicate code (and risk introducing bugs), it just has to call functions from the libraries installed on the system. The most obvious example of a set of libraries is Glibc which is installed during the LFS book. This contains all of the C library functions which programs use.
There are two types of libraries: static and shared. Shared
libraries (usually libXXX.so) are
loaded into memory from the shared copy at runtime (hence the
name). Static libraries ( libXXX.a)
are actually linked into the program executable file itself, thus
making the program file larger. Quite often, you will find both
static and shared copies of the same library on your system.
Generally, you only need to install libraries when you are
installing software that needs the functionality they supply. In
the BLFS book, each package is presented with a list of (known)
dependencies. Thus, you can figure out which libraries you need
to have before installing that program. If you are installing
something without using BLFS instructions, usually the
README or INSTALL file will contain details of the
program's requirements.
There are certain libraries which nearly everyone will need at some point. In this chapter these and some others are listed and it is explained why you may want to install them.
The Apache Portable Runtime (APR) is a supporting library for the Apache web server. It provides a set of application programming interfaces (APIs) that map to the underlying Operating System (OS). Where the OS doesn't support a particular function, APR will provide an emulation. Thus programmers can use the APR to make a program portable across different platforms.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://archive.apache.org/dist/apr/apr-1.7.0.tar.bz2
Download (FTP): ftp://ftp.mirrorservice.org/sites/ftp.apache.org/apr/apr-1.7.0.tar.bz2
Download MD5 sum: 7a14a83d664e87599ea25ff4432e48a7
Download size: 852 KB
Estimated disk space required: 11 MB (additional 4 MB for the tests)
Estimated build time: 0.2 SBU (add 1.7 SBU for tests)
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/apr
First, fix a security issue:
sed -e "/shift/i \
\ if (xt->tm_mon < 0 || xt->tm_mon >= 12) return APR_EBADDATE;" \
-i time/unix/time.c
Install Apr by running the following commands:
./configure --prefix=/usr \
--disable-static \
--with-installbuilddir=/usr/share/apr-1/build &&
make
To test the results, issue: make test.
Now, as the root user:
make install
--disable-static:
This switch prevents installation of static versions of the
libraries.
Last updated on
The Apache Portable Runtime Utility Library provides a predictable and consistent interface to underlying client library interfaces. This application programming interface assures predictable if not identical behaviour regardless of which libraries are available on a given platform.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://archive.apache.org/dist/apr/apr-util-1.6.1.tar.bz2
Download (FTP): ftp://ftp.mirrorservice.org/sites/ftp.apache.org/apr/apr-util-1.6.1.tar.bz2
Download MD5 sum: 8ff5dc36fa39a2a3db1df196d3ed6086
Download size: 420 KB
Estimated disk space required: 6.5 MB (add 1.4 MB for tests)
Estimated build time: less than 0.1 SBU (add 0.3 SBU for tests)
Berkeley DB-5.3.28, FreeTDS, MariaDB-10.6.4 or MySQL, OpenLDAP-2.5.7, PostgreSQL-13.4, SQLite-3.36.0 and unixODBC-2.3.9
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/apr-util
Install Apr Util by running the following commands:
./configure --prefix=/usr \
--with-apr=/usr \
--with-gdbm=/usr \
--with-openssl=/usr \
--with-crypto &&
make
To test the results, issue: make -j1 test. One test, testdbm, is known to fail.
Now, as the root user:
make install
--with-gdbm=/usr:
This switch enables the apr_dbm_gdbm-1.so plugin.
--with-openssl=/usr
--with-crypto: These switches enable the
apr_crypto_openssl-1.so plugin.
--with-berkeley-db=/usr: If you
have installed Berkeley DB-5.3.28, use this switch
to compile the apr_dbm_db-1.so
plugin.
--with-ldap: If you have
installed OpenLDAP-2.5.7, use this switch to
compile the apr_ldap.so plugin.
Last updated on
The Aspell package contains an interactive spell checking program and the Aspell libraries. Aspell can either be used as a library or as an independent spell checker.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://ftp.gnu.org/gnu/aspell/aspell-0.60.8.tar.gz
Download (FTP): ftp://ftp.gnu.org/gnu/aspell/aspell-0.60.8.tar.gz
Download MD5 sum: 012fa9209203ae4e5a61c2a668fd10e3
Download size: 3.3 MB
Estimated disk space required: 51 MB (Additional 8 MB for EN dictionary)
Estimated build time: 0.4 SBU
You'll need to download at least one dictionary. The link below will take you to a page containing links to dictionaries in many languages.
Aspell dictionaries: https://ftp.gnu.org/gnu/aspell/dict
Which-2.21 (for the dictionaries)
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/aspell
Install Aspell by running the following commands:
./configure --prefix=/usr && make
This package does not come with a test suite.
Now, as the root user:
make install &&
ln -svfn aspell-0.60 /usr/lib/aspell &&
install -v -m755 -d /usr/share/doc/aspell-0.60.8/aspell{,-dev}.html &&
install -v -m644 manual/aspell.html/* \
/usr/share/doc/aspell-0.60.8/aspell.html &&
install -v -m644 manual/aspell-dev.html/* \
/usr/share/doc/aspell-0.60.8/aspell-dev.html
If you do not plan to install Ispell, then copy the wrapper script ispell:
install -v -m 755 scripts/ispell /usr/bin/
If you do not plan to install Spell, then copy the wrapper script spell:
install -v -m 755 scripts/spell /usr/bin/
ln -svfn aspell-0.60 /usr/lib/aspell: This command is useful for configuration of other applications, such as enchant-2.3.1.
|
is a utility that can function as an ispell -a replacement, as an independent spell checker, as a test utility to test out Aspell features, and as a utility for managing dictionaries |
|
|
is a wrapper around aspell to invoke it in ispell compatible mode |
|
|
is a wrapper around aspell to invoke it in spell compatible mode |
|
|
imports old personal dictionaries into Aspell |
|
|
decompresses a prezipped file to stdout |
|
|
decompresses a prezipped file |
|
|
is a prefix delta compressor, used to compress sorted word lists or other similar text files |
|
|
is called by the various wrapper scripts to perform the actual compressing and decompressing |
|
|
displays information about the |
|
|
is a script to help use Aspell as an ispell replacement |
|
|
compresses or decompresses sorted word lists for use with the Aspell spell checker |
|
|
contains spell checking API functions |
|
|
is an interface to the |
Last updated on
Boost provides a set of free peer-reviewed portable C++ source libraries. It includes libraries for linear algebra, pseudorandom number generation, multithreading, image processing, regular expressions and unit testing.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://boostorg.jfrog.io/artifactory/main/release/1.77.0/source/boost_1_77_0.tar.bz2
Download MD5 sum: 09dc857466718f27237144c6f2432d86
Download size: 105 MB
Estimated disk space required: 1.0 GB (189 MB installed)
Estimated build time: 1.7 SBU (Using parallelism=4; add 1.3 SBU for tests)
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/boost
This package can be built with several jobs running in
parallel. In the instructions below, <N> stands for the number
of jobs. Install Boost by
running the following commands:
./bootstrap.sh --prefix=/usr --with-python=python3 &&
./b2 stage -j<N> threading=multi link=shared
To run the Boost.Build's regression test, issue pushd tools/build/test; python3 test_all.py; popd. All 154 tests should pass.
To run every library's regression tests, issue pushd status; ../b2; popd.
A few tests may fail. They take a very long time (over 119
SBU at -j4) and use a very large amount of disk space (46
GB). You should use the -jN switch to speed them up.
Now, as the root user:
./b2 install threading=multi link=shared
threading=multi: This
parameter ensures that Boost
is built with multithreading support.
link=shared: This
parameter ensures that only shared libraries are created,
except for libboost_exception and libboost_test_exec_monitor
which are created as static. Most people will not need the
static libraries, and most programs using Boost only use the headers. Omit this
parameter if you do need static libraries.
-jN: This switch may be added to
the b2 command
lines, to run up to N processes in parallel.
--with-python=python3: Add this
switch to the bootstrap command, if you
want Boost to use Python3 instead of Python2. Using Python3
is known to cause the installation to fail on some systems.
Last updated on
Brotli provides a general-purpose lossless compression algorithm that compresses data using a combination of a modern variant of the LZ77 algorithm, Huffman coding and 2nd order context modeling. Its libraries are particularly used for WOFF2 fonts on webpages.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://github.com/google/brotli/archive/v1.0.9/brotli-1.0.9.tar.gz
Download MD5 sum: c2274f0c7af8470ad514637c35bcee7d
Download size: 476 KB
Estimated disk space required: 24 MB (with python3 bindings)
Estimated build time: 0.4 SBU (with python3 bindings)
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/brotli
At first, fix an issue in pkg-config files:
sed -i '[email protected].@@' scripts/*.pc.in
Install brotli by running the following commands:
mkdir out &&
cd out &&
cmake -DCMAKE_INSTALL_PREFIX=/usr \
-DCMAKE_BUILD_TYPE=Release \
.. &&
make
To test the results, issue: make test.
If desired, build the Python3 bindings:
pushd .. && python3 setup.py build && popd
The python tests are missing most of the necessary testdata files and therefore 240 of 311 tests fail. If you nevertheless wish to test the bindings, go back to the top-level directory and issue: python3 setup.py test.
Now, as the root user:
make install && cd ..
If you have built the python
bindings, install them as the root user:
python3 setup.py install --optimize=1
Last updated on
CLucene is a C++ version of Lucene, a high performance text search engine.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://downloads.sourceforge.net/clucene/clucene-core-2.3.3.4.tar.gz
Download MD5 sum: 48d647fbd8ef8889e5a7f422c1bfda94
Download size: 2.2 MB
Estimated disk space required: 78 MB
Estimated build time: 0.8 SBU
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/clucene
Install CLucene by running the following commands:
patch -Np1 -i ../clucene-2.3.3.4-contribs_lib-1.patch &&
mkdir build &&
cd build &&
cmake -DCMAKE_INSTALL_PREFIX=/usr \
-DBUILD_CONTRIBS_LIB=ON .. &&
make
Now, as the root user:
make install
-DBUILD_CONTRIBS_LIB=ON: This
cmake variable enables building the CLucene contribs library
necessary for running applications that use language specific
text analyzers like LibreOffice for example.
Last updated on
The D-Bus GLib package contains GLib interfaces to the D-Bus API.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://dbus.freedesktop.org/releases/dbus-glib/dbus-glib-0.112.tar.gz
Download MD5 sum: 021e6c8a288df02c227e4aafbf7e7527
Download size: 700 KB
Estimated disk space required: 12 MB (with tests)
Estimated build time: 0.1 SBU (with tests)
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/dbus-glib
Install D-Bus GLib by running the following commands:
./configure --prefix=/usr \
--sysconfdir=/etc \
--disable-static &&
make
To test the results, issue: make check. Note that more comprehensive tests can be run by following the same method used in D-Bus instructions, which requires building the package twice.
Now, as the root user:
make install
--disable-static:
This switch prevents installation of static versions of the
libraries.
--enable-gtk-doc: Use this
parameter if GTK-Doc is
installed and you wish to rebuild and install the API
documentation.
Last updated on
The Double-conversion package contains a library that facilitates binary-to-decimal and decimal-to-binary routines for IEEE doubles.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://github.com/google/double-conversion/archive/v3.1.5/double-conversion-3.1.5.tar.gz
Download MD5 sum: e94d3a33a417e692e5600e75019f0272
Download size: 6.7 MB
Estimated disk space required: 54 MB
Estimated build time: 0.1 SBU
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/double-conversion
Install Double-conversion by running the following commands:
mkdir build &&
cd build &&
cmake -DCMAKE_INSTALL_PREFIX=/usr \
-DBUILD_SHARED_LIBS=ON \
-DBUILD_TESTING=ON \
.. &&
make
To test the results, issue: make test.
Now, as the root user:
make install
-DBUILD_SHARED_LIBS=ON: This
switch forces cmake to build a shared version of the library
instead of the static version.
-DBUILD_TESTING=ON:
This switch builds the test programs.
Last updated on
The enchant package provides a generic interface into various existing spell checking libraries.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://github.com/AbiWord/enchant/releases/download/v2.3.1/enchant-2.3.1.tar.gz
Download MD5 sum: 0b9b60da3bf595ff07547c40668a7373
Download size: 968 KB
Estimated disk space required: 7.3 MB (add 100 MB for tests)
Estimated build time: 0.2 SBU (add 0.5 SBU for tests)
dbus-glib-0.112, Doxygen-1.9.2, Hspell, Hunspell, Nuspell, Voikko, and unittest-cpp (required for tests)
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/enchant
Install enchant by running the following commands:
./configure --prefix=/usr --disable-static && make
To run tests, unittest-cpp must be installed and the
--enable-relocatable option
passed to configure above. If these conditions are present,
the tests may be run with make
check.
Now, as the root user:
make install
--disable-static:
This switch prevents installation of static versions of the
libraries.
You can test your installation and configuration by creating a test file and running the following commands (you can replace the en_GB dictionary by any other downloaded when installing Aspell-0.60.8):
cat > /tmp/test-enchant.txt << "EOF"
Tel me more abot linux
Ther ar so many commads
EOF
enchant-2 -d en_GB -l /tmp/test-enchant.txt &&
enchant-2 -d en_GB -a /tmp/test-enchant.txt
You will see a list of the misspelled words followed by a list of alternatives for them.
See more details in the enchant manual page.
Last updated on
Exempi is an implementation of XMP (Adobe's Extensible Metadata Platform).
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://libopenraw.freedesktop.org/download/exempi-2.5.2.tar.bz2
Download MD5 sum: 96e82c244a5659a9b07ae07ca8773ad9
Download size: 3.5 MB
Estimated disk space required: 372 MB (add 31 MB for tests)
Estimated build time: 0.5 SBU (using parallelism=4; add 0.3 SBU for tests)
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/exempi
If you intend to run the regression tests, first remove a test that depends on an apparently proprietary Adobe SDK:
sed -i -r '/^\s?testadobesdk/d' exempi/Makefile.am && autoreconf -fiv
Install Exempi by running the following commands:
./configure --prefix=/usr --disable-static && make
To test the results, issue: make check.
Now, as the root user:
make install
--disable-static:
This switch prevents installation of static versions of the
libraries.
Last updated on
FFTW is a C subroutine library for computing the discrete Fourier transform (DFT) in one or more dimensions, of arbitrary input size, and of both real and complex data (as well as of even/odd data, i.e. the discrete cosine/sine transforms or DCT/DST).
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): http://www.fftw.org/fftw-3.3.9.tar.gz
Download (FTP): ftp://ftp.fftw.org/pub/fftw/fftw-3.3.9.tar.gz
Download MD5 sum: 50145bb68a8510b5d77605f11cadf8dc
Download size: 4.0 MB
Estimated disk space required: 60 MB
Estimated build time: 1.4 SBU (using parallelism=4; add 2.2 SBU for tests)
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/fftw
We build fftw three times for different libraries in different numerical precisions: the default double precision floating point, the older 32-bit (single precision) version named float which sacrifices precision for speed, and the long double which offers increased precision at the cost of slower execution.
The first build is for double precision arithmetic. Install fftw by running the following commands:
./configure --prefix=/usr \
--enable-shared \
--disable-static \
--enable-threads \
--enable-sse2 \
--enable-avx &&
make
To test the results, issue: make check. On 32-bit systems, the tests can take substantially longer than they would on 64-bit machines.
Now, as the root user:
make install
Now build single precision:
make clean &&
./configure --prefix=/usr \
--enable-shared \
--disable-static \
--enable-threads \
--enable-sse2 \
--enable-avx \
--enable-float &&
make
As the root user:
make install
Finally, build long double precision:
make clean &&
./configure --prefix=/usr \
--enable-shared \
--disable-static \
--enable-threads \
--enable-long-double &&
make
As the root user:
make install
--enable-shared
--disable-static: Use shared libs instead of
static libs.
--enable-threads:
This enables libfftw3_threads.so to be compiled. It is
used by e.g. the gimp plugin
from G'MIC.
--enable-float: This
enables building the library that uses single precision
floating point arithmetic. It is faster but less precise than
the default double precision library. The library will be
called libfftw3f.so needed by
PulseAudio-15.0.
--enable-long-double:
This enables building the library that uses higher precision
long-double floating point arithmetic. The library will be
called libfftw3l.so.
|
is a utility to generate FFTW wisdom files, which contain saved information about how to optimally compute (Fourier) transforms of various sizes |
|
|
is a utility to generate C configuration routines from FFTW wisdom files, where the latter contain saved information about how to optimally compute (Fourier) transforms of various sizes |
|
|
is the Fast Fourier Transform library |
|
|
is the threaded Fast Fourier Transform library |
|
|
is the single-precision Fast Fourier Transform library, described as “float” for historic reasons |
|
|
is the threaded single-precision Fast Fourier Transform library |
|
|
is the long double Fast Fourier Transform library |
|
|
is the threaded long double Fast Fourier Transform library |
Last updated on
The GLib package contains low-level libraries useful for providing data structure handling for C, portability wrappers and interfaces for such runtime functionality as an event loop, threads, dynamic loading and an object system.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://download.gnome.org/sources/glib/2.68/glib-2.68.4.tar.xz
Download (FTP): ftp://ftp.acc.umu.se/pub/gnome/sources/glib/2.68/glib-2.68.4.tar.xz
Download MD5 sum: 07ba0e946bf6dcad36388675d2f2876f
Download size: 4.8 MB
Estimated disk space required: 104 MB (add 6 MB for tests)
Estimated build time: 0.6 SBU (add 1.0 SBU for tests; both using parallelism=4)
libxslt-1.1.34 and PCRE-8.45 (built with Unicode properties)
dbus-1.12.20 and bindfs (both may be used in some tests), GDB-10.2 (for bindings), docbook-xml-4.5, docbook-xsl-1.79.2, GTK-Doc-1.33.2 (to build API documentation), glib-networking-2.68.2 (for some tests, but this is a circular dependency), and sysprof-3.40.1
gobject-introspection-1.68.0 (should be installed before gtk+, atk, etc.)
Quoted directly from the INSTALL file: “Some of the
mimetype-related functionality in GIO requires the
update-mime-database and
update-desktop-database
utilities”, which are part of shared-mime-info-2.1 and desktop-file-utils-0.26,
respectively. These two utilities are also needed for some
tests.
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/glib2
If desired, apply the optional patch. In many cases,
applications that use this library, either directly or
indirectly via other libraries such as GTK+-3.24.30, output
numerous warnings when run from the command line. This patch
enables the use of an environment variable, GLIB_LOG_LEVEL, that supresses unwanted
messages. The value of the variable is a digit that
corresponds to:
| 1 Alert |
| 2 Critical |
| 3 Error |
| 4 Warning |
| 5 Notice |
For instance export
GLIB_LOG_LEVEL=4 will skip output of Warning
and Notice messages (and Info/Debug messages if they are
turned on). If GLIB_LOG_LEVEL is
not defined, normal message output will not be affected.
patch -Np1 -i ../glib-2.68.4-skip_warnings-1.patch
If a previous version of glib is installed, move the headers out of the way so that later packages do not encounter conflicts:
if [ -e /usr/include/glib-2.0 ]; then
rm -rf /usr/include/glib-2.0.old &&
mv -vf /usr/include/glib-2.0{,.old}
fi
Install GLib by running the following commands:
mkdir build &&
cd build &&
meson --prefix=/usr \
--buildtype=release \
-Dman=true \
.. &&
ninja
If libxslt-1.1.34 is installed, the above command may indicate several (about 33) errors that start with "Error: no ID for constraint linkend:" when generating the man pages. These are harmless.
The GLib test suite requires desktop-file-utils for some tests. However, desktop-file-utils requires GLib in order to compile; therefore, you must first install GLib and then run the test suite.
Now, as the root user:
ninja install &&
mkdir -p /usr/share/doc/glib-2.68.4 &&
cp -r ../docs/reference/{NEWS,gio,glib,gobject} /usr/share/doc/glib-2.68.4
You should now install desktop-file-utils-0.26 and shared-mime-info-2.1 and proceed to run the test suite.
To test the results, after having installed the package,
issue: ninja
test. One test named gio / file is known to fail if the test is
ran as the root user.
Finally, if this is a reinstall from glib2-2.64.x or earlier,
remove (as the root user) an
obsolete header file that interferes with some packages:
rm -f /usr/include/glib-2.0/glib/gurifuncs.h
--buildtype=release:
Specify a buildtype suitable for stable releases of the
package, as the default may produce unoptimized binaries.
-Dman=true: This
switch causes the build to create and install the package man
pages.
-Dgtk_doc=true: This switch
causes the build to create and install the API documentation.
|
can be used to start applications and to send messages to already-running instances of other applications |
|
|
is a simple tool used for working with D-Bus objects |
|
|
is used to generate code and/or documentation for one or more D-Bus interfaces |
|
|
is a utility that makes many GIO features available from the command line |
|
|
is used to create a |
|
|
is used to read the resource description from a file and the files that it references to create a binary resource bundle that is suitable for use with the GResource API |
|
|
is used to compile all the GSettings XML schema
files in a directory into a binary file with the
name |
|
|
is a C code marshaller generation utility for GLib closures |
|
|
is a variant of the gettext internationalization utility |
|
|
is a C language enum description generation utility |
|
|
is a small utility that draws a tree of types |
|
|
offers a simple command line interface to GResource |
|
|
offers a simple command line interface to GSettings |
|
|
is a test running utility |
|
|
is a test report formatting utility |
|
|
contain low-level core libraries for the GIMP Toolkit |
Last updated on
The GLibmm package is a set of C++ bindings for GLib.
This package is known to build and work properly using an LFS-11.0 platform.
Download (HTTP): https://download.gnome.org/sources/glibmm/2.66/glibmm-2.66.1.tar.xz
Download (FTP): ftp://ftp.acc.umu.se/pub/gnome/sources/glibmm/2.66/glibmm-2.66.1.tar.xz
Download MD5 sum: ee8c00fd7f08ae59f6af38dfa599194a
Download size: 7.2 MB
Estimated disk space required: 88 MB (with tests)
Estimated build time: 0.5 SBU (Using parallelism=4; with tests)
GLib-2.68.4 and libsigc++-2.10.7
Doxygen-1.9.2, glib-networking-2.68.2 (for tests), GnuTLS-3.7.2 (for tests), libxslt-1.1.34, and mm-common
User Notes: https://wiki.linuxfromscratch.org/blfs/wiki/glibmm
Install GLibmm by running the following commands:
mkdir bld && cd bld && meson --prefix=/usr --buildtype=release .. && ninja
To test the results, issue: ninja test.
Now, as the root user:
ninja install