pocket composed on 2024-12-03 23:26 (UTC+0100):
>>>>>>> [alarm@alarm ~]$ ls -l /
>>>>>>> lrwxrwxrwx 1 root root 7 Nov 25 19:15 bin -> usr/bin
>>>>>>> drwxr-xr-x 3 root root 4096 Dec 31 1969 boot
>>>>>> …
>>>>>> What Debian puts a FAT filesystem on /boot/? Is that a systemd-boot
>>>>>> configuration?
>>>>> Mine for one.......
>>>> Keeping your bootloader of choice a secret?
>>> Nope, a bootloader is a bootloader is a bootloader
>> Except one that doesn't load any bootloader files, kernel or initrd from
>> /boot/,
>> which is what one or more others than Grub* are reputedly doing.
> I miss your point, the boot loader loads the kernel then control passes to
> systemd/init/bash
It used to be that bootloaders always found the kernels and initrds they were to
load in /boot/. That has been reported to be no longer the case. My interest was
in having anyone report experience with such a bootloader (along with its name)
which does not load kernels and/or initrds from /boot/. I have to wonder what,
if
anything, such bootloaders use /boot/ for, and if not bootloader files, kernels
and initrds, where they are expecting to get them from. Given the insecurity of
FAT, I hope I don't live long enough to be forced to keep my kernels or initrds
on
such.
--
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
