Mark Fletcher composed on 2023-12-21 21:30 (UTC):
> Felix Miata wrote:
>> I suspect few if any regulars here spend much time with Slackware.
> I am genuinely confused about how Slackware came into the picture
> here... my foreign OS is LFS, nothing to do with slackware as far as I
> know...
Pure unadulterated word dyslexia here. My brain routinely fails to register any
difference between LFS and Slackware, both of which in my mind rely more heavily
on the brains of its admins than those of Debian's or its derivatives'. LFS I've
never attempted to use. Slackware I have. Sorry for causing confusion here.
> I appreciate your initial help which I still think is my best hope of
> a solution
Boot setup are rather simple here. I don't "edit" content of any files in
/etc/grub.d/ in the usual sense of the word. What I do is copy 40_custom to
06_custom, and copy 41_custom to 07_custom on my Tumbleweed installation. Then I
remove the content from 40_custom and 41_custom to make them inert rather than
having the package system recreate them and bloat grub.cfg as a result. I
manually
maintain one file: /boot/grub2/custom.cfg on my Tumbleweed / filesystem. That
would correspond to a Debian LVM user, such as you, maintaining /grub/custom.cfg
on his /boot filesystem.
Admins are 100% responsible for the content of (*/gru*/)custom.cfg. Because of
my
particular handling of /etc/grub.d/, the stanzas in custom.cfg head the
selection
list presented by Grub on boot. Those generated by Grub's scripts are rarely
utilized here. Any selected stanza from custom.cfg that fails to boot something
can only be due to my own fault.
Tumbleweed is the only distro installed here where the ESP is routinely mounted
to
/boot/efi/. Only one bootloader is needed per typical Gnu/Linux-only multiboot
PC.
>From one PC here currently booted:
# grep vmlinuz /boot/grub2/custom.cfg | wc -l
21
# grep root= /boot/grub2/custom.cfg | wc -l
21
# grep root=LABEL /boot/grub2/custom.cfg | wc -l
21
#
There need be no difference from my configuration an any Debian user's, other
than
the name of the directory containing custom.cfg.
For those who don't know the why of /boot/grub2/ instead of /boot/grub/ (on
openSUSE at least), grub2 is used instead of grub in /boot/ as a historical
continuation of the multiple releases period when both Grub Legacy and Grub2
could
be simultaneously installed on the same installation without need for any
filename
customization in Grub as installed. IIRC, one could be setup on MBR, the other
on
a partition, possibly more for developer convenience than any expectation users
would want both at once.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
