On Thu, 20 Nov 2025 16:24:13 +0100 (CET)
karl@??? wrote:

> Didier:
> > Le 20/11/2025 __ 13:42, g4sra via Dng a __crit__:
>...
>
> A. Soo, there was formely at least one reason.

Yeah that was a big reason back in the day Another was security, /boot
could be read-only or not even mounted.

I had heard of the usermerge in passing but only recently dug into this
and find the justifications trivia if not minutiae.

>
> B. you might have a few systems using the same /boot, eg. for testing.
> There are a lot of handy things you can argue for if you mention
> testing.

Converserly one could have multiple boot folders. :)

This was sometimes a strategy for testing/upgrading. Some BIOS/EFI use a
similar type system.

>
> C. Who cares.
> With todays disk sizes you can have /boot sufficiently large for how
> many kernels you want to have without hampering any other partitions.
> So, what is the problem, what does it matter if someone wants it for
> whatever reason. In the end, as time goes by, your disk will be too
> small for your system use, and your processor will be too slow etc.
> so you will have to replace things that don't gives you what you need.
> And, it isn't good economy to chase every perceived flaw.
>
> D, As Martin wrote, you can use a simpler fs type, eg. ext2 or even
> vfat to comply with other things, eg. booting other types of systems.
> (Since you already might have an efi partition, why not put boot there.
> I have not tested that but it could be a possibility.)

I have always used a separate boot folder because that is the way I learned.
I always used ext2 becuase it is very annoying to compile a kernel or upgrade
and forget to compile the root fs driver or update the initrd. Also,
boot loaders tended to be rather crude in their fs support. Even grub
could be hit or miss like with XFS for example.

I originally have shied away from uefi but have been using it on newer systems and
have a merged /boot on these systems and mount the efi partition of course.

>
> Regards,
> /Karl Hammar


--
Security <security@???>