| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
| |
- according to our typography, referring to a manual page should be
<filename>page(x)</filename>
- don't enclose punctuation into quotes
- use <option> for option
|
|
|
|
| |
Stupid inconsistency...
|
| |
|
|
|
|
|
|
|
|
|
| |
In Linux 6.6 DRM_FBDEV_EMULATION no longer depends on FB, so we no
longer need to select FB (tested in a QEMU VM).
But if DRM is selected, we must select both DRM_FBDEV_EMULATION and
FRAMEBUFFER_CONSOLE or we'll see only blank screen. And now
FRAMEBUFFER_CONSOLE is not selected by default, be warned!!
|
|
|
|
| |
Only a trivial change (renaming CONFIG_FB).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update to vim-1837.$
Update to zlib-1.3.$
Update to wheel-0.41.2 (Python Module).$
Update to util-linux-2.39.2.$
Update to sysvinit-3.08.$
Update to shadow-4.14.0.$
Update to Python-3.11.5.$
Update to procps-ng-4.0.4.$
Update to pkgconf-2.0.2.$
Update to mpfr-4.2.1.$
Update to kbd-2.6.2.$
Update to gzip-1.13.$
Update to coreutils-9.4.$
Specify the 'nobody-group' for systemd.$
Remove unused usb group.$
|
|
|
|
|
|
|
|
|
| |
They are very long <screen> or <note>. By default they are attributed
"keep-together.within-column = always", override it to allow line break.
Fixes #5336.
Link: http://www.sagehill.net/docbookxsl/PageBreaking.html
|
|
|
|
| |
text not
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Import kernel-config infrastructure from BLFS and use it for kernel
configuration. Note that kernel-config.py is slightly different from
BLFS: we need role="nodump" for <screen> here.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
A couple of the newer kernel options overflow past 80 columns on
the kernel page. It's not optimal, but insert newlines for these
options.
Also reorder the options to to same ordeer as they appear in
menuconfig and add some blank lines between major setions for
clarity.
|
|
|
|
| |
Prepare for systemd-254 update. See #5293 for details.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
It's already removed from Linux 6.4.
Link: https://git.kernel.org/torvalds/linux/c/721da5cee9d4
|
|
|
|
|
| |
Report by wen zhang.
Also fix formatting.
|
|
|
|
|
| |
systemd-oomd needs PSI so it does not make sense to disable it by
default.
|
| |
|
| |
|
|
|
|
| |
"parition".
|
|
|
|
| |
Add an <important> note as an introduction to configuring the kernel.
|
|
|
|
|
|
|
|
|
| |
- 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 d0a9bda4e696f4be02499b87c2bd6d8f40a3d4a3.
"Don't change anything enabled by defconfig" seems too strong.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit de679165f9a63ce94202d356abbae2b9a3bff5c3.
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.
|
|
|
|
|
| |
This is less generic than defconfig, and you can then tell
not to tweak options...
|
|
|
|
|
|
| |
tell people not to messing the options enabled by defconfig up.
Yes, I messed them up and shot my own foot.
|
|
|
|
|
|
|
|
| |
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).
|
|
|
|
| |
Is there anyone using a blind system with serial console now? :)
|
|
|
|
|
|
|
|
|
|
| |
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 does not make too much sense to protect the userspace with PIE+ASLR
and SSP but leave the kernel alone...
|
|
|
|
|
|
| |
This reverts commit 098f4de3369ae0fc7d50fc6060b059eb5627de4e.
CVE-2022-2590 is fixed in Linux >= 5.19.6.
|
|
|
|
| |
Text only change.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
The references already correctly decorated are not changed because "if
it's not broken don't fix it".
|
|
|
|
| |
Also make the order and the layout the same as in menu.
|