Given the lack of Cs to my RFC, it seems I might well have been the only person so far to compare the books from a "text" viepoint.
In case it's thus of use, I list below some differences between the two texts that there would seem to be no reason not to rectify. These are differences in the books that are not attributable to their Sysvinit vs Systemd nature. The differences are either typos that have been recitifed in one book and not the other or English punctuation or syntax changes. I've thought to list the Chapter and section as well as the line numbers, as I doubt anyone authoring the content will be doing so in the plain text! The standard LFS book is the <; the systemd the > 2.5. Mounting the New Partition Note that "varibale" is wrong in both 1621c1573 < environment varibale as described in the previous section. --- > envronment varibale as described in the previous section. 5.7.1. Installation of Glibc 3089c3020 < First fix a build problem that affects i386 systems: --- > First, fix a build problem that affects i386 systems: 5.33.1. Installation of Util-linux 4271c4202 < Setting this environment variable prevents adding unneeded --- > Setting this envronment variable prevents adding unneeded 6.3.3. Deploying LFS on Multiple Systems 4714,4717c4643,4646 < not identical architectures. For instance the instruction set for Intel < architectures is not identical with AMD processors and later versions < of some processors may have instructions not available in earlier < versions. --- > not identical architectures. For instance, the instruction set for an > Intel architecture is not identical with an AMD processor and later > versions of some processors may have instructions that are unavailable > in earlier versions. 6.9.1. Installation of Glibc 5090c5033 < Now fix a build problem that affects i386 systems: --- > Now, fix a build problem that affects i386 systems: 5121c5064 < necessary networking applications when the tests are run. --- > necessary network applications when the tests are run. 6.20.1. Installation of Ncurses 6525,6529c6473,6477 < link against them at runtime. Currently, the only known binary-only < applications that link against non-wide-character Ncurses require < version 5. If you must have such libraries because of some binary-only < application or to be compliant with LSB, build the package again with < the following commands: --- > link against them at runtime. However, the only known binary-only > applications that link against non-wide-character Ncurses libraries > require version 5. If you must have such libraries because of some > binary-only application or to be compliant with LSB, build the package > again with the following commands: 6.31.1. Installation of M4 8128c8072 < The test-update-copyright.sh failure can be ignored. --- > The test-update-copyright.sh failure can safely be ignored. 6.34.1. Installation of Grep Note that this one and the previous have different ways of saying the same things " can safely be" vs "can be safely" 8270c8214 < The test-update-copyright.sh failure can be ignored. --- > The test-update-copyright.sh failure can be safely ignored. 6.38.1. Installation of Libtool 8503c8447 < Five tests are known to fail in the LFS build environment due to a --- > Five tests are known to fail in the LFS build envronment due to a 6.41.1. Installation of Inetutils Same text: ordering issue 8651a8596,8601 > --disable-r* > These parameters disable building obsolete programs that should > not be used due to security issues. The functions provided by > these programs can be provided by the openssh package in the > BLFS book. > 8663,8668d8612 < --disable-r* < These parameters disable building obsolete programs that should < not be used due to security issues. The functions provided by < these programs can be provided by the openssh package in the < BLFS book. < 6.46.1. Installation of Diffutils 9210c9154 < The test-update-copyright.sh failure can be ignored. --- > The test-update-copyright.sh failure can be safely ignored. 6.68.2. Installation of Util-linux Just an extra space 11176c11166 < ./configure ADJTIME_PATH=/var/lib/hwclock/adjtime \ --- > ./configure ADJTIME_PATH=/var/lib/hwclock/adjtime \ Section 7.3 has different names in the two books but a lot of identical content, so these are sytactical differences 12265,12266c12412,12413 < Linux systems in general traditionally used a static device creation < method, whereby a great many device nodes were created under /dev --- > Linux systems in general traditionally use a static device creation > method, whereby a great many device nodes are created under /dev 12268,12271c12415,12418 < corresponding hardware devices actually existed. This was typically < done via a MAKEDEV script, which contains a number of calls to the < mknod program with the relevant major and minor device numbers for < every possible device that might exist in the world. --- > corresponding hardware devices actually exist. This is typically done > via a MAKEDEV script, which contains a number of calls to the mknod > program with the relevant major and minor device numbers for every > possible device that might exist in the world. 12294,12295c12441,12442 < also suffered from race conditions that were inherent in its design and < could not be fixed without a substantial revision to the kernel. It was --- > also suffers from race conditions that are inherent in its design and > cannot be fixed without a substantial revision to the kernel. It was 12303,12304c12450,12451 < userspace-visible representation, the possibility of developing a < userspace replacement for devfs became much more realistic. --- > userspace-visible representation, the possibility of seeing a userspace > replacement for devfs became much more realistic. 12323,12326c12470,12473 < driver that wishes to register a device node will go through the < devtmpfs (via the driver core) to do it. When a devtmpfs instance is < mounted on /dev, the device node will initially be created with a fixed < name, permissions, and owner. --- > driver that wishes to register a device node will go through devtmpfs > (via the driver core) to do it. When a devtmpfs instance is mounted on > /dev, the device node will initially be created with a fixed name, > permissions, and owner. Just above the start of 7.8 Creating the /etc/inputrc File 13528c12926 < UTF-8 based locales are not supported well by some programs. Work is in --- > UTF-8 based locales are not supported well by many programs. Work is in -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
