On Tue, Jul 29, 2025 at 1:27 AM Felix Miata <mrmazda@xxxxxxxxxxxxx> wrote:
All my Fedora installations do this, as I only have one bootloader per PC installed, no matter how many distros are:
# ls -1 /dists/*/etc/fstab | wc -l
19
# inxi -S
System:
Host: ab560 Kernel: 6.14.11-200.fc41.x86_64 arch: x86_64 bits: 64
Console: pty pts/1 Distro: Fedora Linux 41 (Forty One)
# time rpm -ivh kernel-longterm-6.12.40-200.fc41.x86_64.rpm kernel-longterm-core-6.12.40-200.fc41.x86_64.rpm kernel-longterm-modules-6.12.40-200.fc41.x86_64.rpm kernel-longterm-modules-core-6.12.40-200.fc41.x86_64.rpm
warning: kernel-longterm-6.12.40-200.fc41.x86_64.rpm: Header V4 RSA/SHA256 Signature, key ID 1eedd52f: NOKEY
Verifying... ################################# [100%]
Preparing... ################################# [100%]
Updating / installing...
1:kernel-longterm-modules-core-6.12################################# [ 25%]
2:kernel-longterm-core-6.12.40-200.################################# [ 50%]
3:kernel-longterm-modules-6.12.40-2################################# [ 75%]
4:kernel-longterm-6.12.40-200.fc41 ################################# [100%]
/etc/kernel/install.d/20-grub.install: line 128: grub2-get-kernel-settings: command not found
/etc/kernel/install.d/20-grub.install: line 140: grub2-probe: command not found
/etc/kernel/install.d/20-grub.install: line 140: grub2-probe: command not found
/etc/kernel/install.d/20-grub.install: line 143: grub2-mkrelpath: command not found
dirname: missing operand
Try 'dirname --help' for more information.
real 0m32.959s
user 0m41.893s
sys 0m9.168s
#
Anyone know a way to determine what makes the calls to unneeded, uninstalled
$BOOTLOADER, or a way to cause them to be skipped? The way I remember it,
without presence of /etc/kernel/install.d/*, kernel installation fails to
generate /boot/initramfs-<version>, thus why I found 20-grub.install somewhere
and placed it myself.
I'm not sure what $BOOTLOADER is. Is it a path to a program or something else?
If $BOOTLOADER is a program, then one way to do it _may_ be to set BOOTLOADER=`command -v true` or similar. The technique is used by Autotools when a program is missing but you want success anyway. For example, you want `make all` to succeed even though you are missing the tools to build the stuff in docs/ directory.
Jeff
-- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue