On Thu 21 Dec 2023 at 22:19:47 (-0500), Felix Miata wrote: > David Wright composed on 2023-12-21 19:20 (UTC-0600): > > On Thu 21 Dec 2023 at 21:38:46 (+0000), Mark Fletcher wrote: > > >> My very first attempt involved using Debian's > >> /boot partition as the /boot partition for LFS as well, so installing > >> LFS's kernel (6.4.12 IIRC) alongside Debian's, but I quickly learned > >> the folly of that when I saw the mess update-grub made of that... > > > What sort of mess? I would have thought Grub would ignore excess > > kernels dropped into /boot. > > It doesn't exactly ignore. This is from a rather old Dell MBR booting > with Grub Legacy installed (but rarely actually used to boot Bullseye):
[ … ] > Found kernel: /boot/vmlinuz > Found kernel: /boot/vmlinuz-prv2 > Found kernel: /boot/vmlinuz-prv > Found kernel: /boot/vmlinuz-cur > Found kernel: /boot/vmlinuz-5.10.0-26-amd64 > Found kernel: /boot/vmlinuz-5.10.0-23-amd64 > Found kernel: /boot/vmlinuz-5.10.0-20-amd64 > Found kernel: /boot/vmlinuz-5.10.0-18-amd64 > Found kernel: /boot/vmlinuz-5.10.0-14-amd64 > Found kernel: /boot/vmlinuz-5.10.0-13-amd64 > Found kernel: /boot/vmlinuz-5.10.0-11-amd64 > Found kernel: /boot/vmlinuz-5.10.0-9-amd64 > Updating /boot/grub/menu.lst ... done [ … ] > Newer PCs with grub-efi exhibit similar behavior, but all here that actually > have grub-efi installed already have current kernel. Mine is a bullseye BIOS-booting laptop with the previously listed /boot directory. I copied a couple of kernels and initrds from the bookworm RCs in partition noah04, and then ran grub-mkconfig. Stderr shows: Generating grub configuration file ... Found linux image: /boot/vmlinuz-6.1.0-13-686 Found initrd image: /boot/initrd.img-6.1.0-13-686 Found linux image: /boot/vmlinuz-6.1.0-10-686 Found initrd image: /boot/initrd.img-6.1.0-10-686 Found linux image: /boot/vmlinuz-5.10.0-26-686 Found initrd image: /boot/initrd.img-5.10.0-26-686 Found linux image: /boot/vmlinuz-5.10.0-25-686 Found initrd image: /boot/initrd.img-5.10.0-25-686 Warning: os-prober will be executed to detect other bootable partitions. Its output will be used to detect bootable binaries on them and create new boot entries. Found Debian GNU/Linux 12 (bookworm) on /dev/sda4 done All the Debian kernels installed from linux-image-….deb packages are found by Grub, and appear in the usual array of prefix10 menuentries. Also, both the bookworm kernels are found by os-prober, as shown by the previously posted zgrep result: listing, and appear in the usual array of prefix30 menuentries. But something about the hd-media installer kernel/initrd seems to prevent Grub from finding them and constructing a menuentry. We know that the LFS kernel is detected by Debian's os-prober, but only that Grub makes a "mess" when given the opportunity of finding the LFS kernel in the same /boot as the Debian ones. What exactly is this mess? Cheers, David.
