- Mention NVME.
- Mention PAE (CONFIG_HIGHMEM64G) for 32-bit.
- Don't repeat the link to BLFS kernel config index twice on SysV.
And don't display the long URL for it.
- Emphasis that BLFS UEFI kernel config is needed even if you'll use the
UEFI bootloader of the host distro.
This reverts commit de679165f9.
localmodconfig does not work very well. It can only *un*select things
already enabled as modules if the module is not loaded by the host. It
won't select anything new, nor unselect unneeded things already set to
"y" instead of "m".
Maybe you think we can copy .config from a "mainstream" distro
(producing a highly modular kernel) and use "make localmodconfig", but
when we tested it with a Debian host kernel config, the resulted kernel
refuses to boot.
"make allmodconfig && make localmodconfig" does not work well either:
"allmodconfig" selects many things as y (these thing are not available
as a module) but "localmodconfig" fails to unselect them.
Let's not encourage users to try tricky things and shoot their own foot.
For systemd, if CONFIG_EXPERT is disable, CONFIG_FHANDLE will be enabled
automatically. So there is no need to enable CONFIG_EXPERT and then set
CONFIG_FHANDLE manually.
LFS and the host may use different /boot configuration, so do not assume
they'll share a /boot partition (two different /boot partition or only one
with separate /boot are possible).
Some host create /dev/shm as a tmpfs. Some have is as
a symlink to a location in another directory. This
change handles both cases.
The change to the sysV bootscripts now creates /dev/shm
as a separate tmpfs from /run. This makes LFS sysV and
systemd versions treat /dev/shm the same.
It's recommended for CVE-2022-21233 mitigation. And, if the BIOS has
enabled x2APIC but CONFIG_X86_X2APIC=n, the kernel will panic on boot.
If x2APIC is disabled or not available, the kernel with
CONFIG_X86_X2APIC=y can still boot normally.
No need to tag anything again because interrupt handling cannot affect
userspace.
The help of this options says:
"However, if you have a new compiler with ..., you may need to disable
this config option in order to successfully build the kernel."
As we are having state-of-art GCC-12, and Linux-5.18 release candidate
FTBFS with GCC-12 and CONFIG_WERROR=y [1], and <rant>the kernel developers
are making stupid and meaningless discussion instead of fixing the building
failure</rant> [2], I don't think enabling this option makes any sense
building LFS.
[1]:https://lkml.org/lkml/2022/4/14/1676
[2]:https://lkml.org/lkml/2022/4/21/254
