On 21 September 2018 at 14:14, Kevin Buckley <[email protected]> wrote:
> On 21 September 2018 at 01:36, Bruce Dubbs <[email protected]> wrote:
>> I have made some reasonably significant changes to LFS. In addition to five
>> package updates I have done the following.
>>
>> 1. Removed util-linux from Chapter 5.
>>
>> 2. Removed the associated symlinks from Chapter 6, Creating Essential
>> Files and Symlinks
>>
>> 3. Moved the System V specific packages in Chapter 6 (Sysvinit,
>> Sysklogd, and Eudev) to be the last packages in Chapter 6.
>>
>> 4. Moved the systemd specific packages (systemd and dbus) to the
>> end of Chapter 6 with the exception of procps which is now
>> at the end of the chapter due to being dependent on libsystemd.
>>
>> 5. Reordered eudev and util-linux in Chapter 6 to avoid the need
>> for LD_LIBRARY_PATH, config.cache, and LIBRARY_PATH in e2fsprogs.
>>
>> This reordering of packages simplifies the build and makes the build order
>> of Chapter 6 identical for both versions of LFS until the user
>> gets to the last three packages. There are still some differences in the
>> build instructions of acl, attr, createfiles, glibc, man-db,
>> procps and util-linux as well as text differences in a few other files.
>>
>> I've built both versions of LFS and they both build cleanly but have not
>> proceeded into BLFS. I'd appreciate any feedback about these changes,
>> especially if you see any issues I've missed.
>
> So,
>
> I am in the middle of an 8.3 build, in that I have Chapter 5
> (with util-linux) completed.
So,
I caried on with the build, but using the new ordering and
everything went smoothly.
My observations/thoughst (Chapter 6/7/8) are
* Automake
# TOTAL: 2904
# PASS: 2723
# SKIP: 142
# XFAIL: 39
# FAIL: 0
# XPASS: 0
# ERROR: 0
so no fail as per the Book's
"One test is known to fail in the LFS environment: subobj.sh."
although I was running the tests as a normal (PkgUser) user.
* Gzip
# TOTAL: 21
# PASS: 21
# SKIP: 0
# XFAIL: 0
# FAIL: 0
# XPASS: 0
# ERROR: 0
so no fail as per the Book's
"Two tests are known to fail in the LFS environment: help-version and zmore"
* Tar
At the emd of the Texinfo section, there's a paragraph about
how to recreate the /usr/share/info/dir file, along with a
block of commands to accomp[lish the task.
I'd suggest that that paragraph and commands would be better
off inside a "Note", and possibly with the <userinput> tags
being dropped from surrounding the commands.
* Procps-ng
The text reads
The meaning of the configure options:
--disable-kill
This switch disables building the kill command that will
be installed by the Util-linux package.
however, now that the Util-linux package gets installed BEFORE Procps-ng,
that should probably read
This switch disables building the kill command that has
already been installed by the Util-linux package.
* Sysklogd
explcity tries to install the man-page as root:root
This isn't an issue for a typical LFS build, but it just strikes me as
a bit of a strange requirement.
* Eudev
Does it need the config-cahe and LIB_PATH= now that it is the last
package to be installed ?
I installed it without using those commands and didn't see any
references to the /tools hierachy in the binaries
pkg eudev:eudev-3.2.5> ldd src/udev/udevd
linux-vdso.so.1 (0x00007ffc9311b000)
libblkid.so.1 => /lib/libblkid.so.1 (0x00007f022dd10000)
libuuid.so.1 => /lib/libuuid.so.1 (0x00007f022dd00000)
libkmod.so.2 => /lib/libkmod.so.2 (0x00007f022dce8000)
liblzma.so.5 => /lib/liblzma.so.5 (0x00007f022dcc0000)
libz.so.1 => /lib/libz.so.1 (0x00007f022dca0000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00007f022dc78000)
libc.so.6 => /lib/libc.so.6 (0x00007f022dab0000)
/lib64/ld-linux-x86-64.so.2 (0x00007f022dd68000)
pkg eudev:eudev-3.2.5> ldd src/udev/udevadm
linux-vdso.so.1 (0x00007ffdc73d3000)
libblkid.so.1 => /lib/libblkid.so.1 (0x00007fa8bed60000)
libuuid.so.1 => /lib/libuuid.so.1 (0x00007fa8bed50000)
libkmod.so.2 => /lib/libkmod.so.2 (0x00007fa8bed38000)
liblzma.so.5 => /lib/liblzma.so.5 (0x00007fa8bed10000)
libz.so.1 => /lib/libz.so.1 (0x00007fa8becf0000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00007fa8becc8000)
libc.so.6 => /lib/libc.so.6 (0x00007fa8beb00000)
/lib64/ld-linux-x86-64.so.2 (0x00007fa8bedb8000)
* 8.2. Creating the /etc/fstab File
As regards the text
"It is possible to make the ext3 filesystem reliable across power failures
for some hard disk types. To do this, add the barrier=1 mount option ..."
I fiund myself wondering, as the instructions for creating the LFS partition
in 2.5. Creating a File System on the Partition, suggest
"LFS assumes that the root file system (/) is of type ext4. "
whether or not the barrier=1 might apply there, although have since
realsied that barrier=1 is a default for ext4.
Thinking it might be worth pointing that out in the 8.2 text ?
* 8.3.1. Installation of the kernel
I felt that this, rather the last piece of the first note, to be a bit vague
Be sure to enable/disable/set the following features or the system
might not work correctly or boot at all:
Device Drivers --->
Generic Driver Options --->
[ ] Support for uevent helper [CONFIG_UEVENT_HELPER]
[*] Maintain a devtmpfs filesystem to mount at /dev [CONFIG_DEVTMPFS]
Kernel hacking --->
Choose kernel unwinder (Frame pointer unwinder) --->
[CONFIG_UNWINDER_FRAME_POINTER]
So, beneath that "Choose kernel unwinder" fold, there are a pair of
radio buttons, so it might be clearer to show the desired setting
of those buttons, as follows
( ) ORC unwinder
(X) Frame pointer unwinder
in the text, as the default is the ORC unwinder ?
Basically then, no show-stoppers for my PkgUser build.
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
