CLFS supports a broad range of processors and addresses advanced techniques not included in the LFS book such as cross-build toolchains, multilibrary support (32 & 64-bit libraries side-by-side), and alternative instruction set architectures such as Itanium, SPARC, MIPS, and Alpha.
Besides its main purpose of creating a security-focused operating system, HLFS had the secondary goal of being a security teaching tool.
It is aimed at users who have gone through the LFS and BLFS books several times and wish to reduce the amount of work involved.
A clean partition and a working Linux system with a compiler and some essential software libraries are required to build LFS.
Then, the root directory must be changed, (using chroot), to the toolchain's partition to start building the final system.
During the chroot phase, bash's hashing feature is turned off and the temporary toolchain's bin directory moved to the end of PATH.
The unit must be interpreted as an approximation; various factors influence the actual time required to build a package.
This would also create another interesting side effect: people who tend to be quick in expressing dissatisfaction on the distributions' mailing lists and forums would probably show a lot more respect for the developers.
Building up a set of 4 CDs containing a stable, secure and reliable operating system, plus thousands of applications, is most definitely not.Tux Machines wrote a review about Linux From Scratch 6.1 in 2005:[20] Now on to BLFS.