Le 20/11/2025 à 13:42, g4sra via Dng a écrit :
>
> * snip -
>
>> I don't recomend making /boot a mountpoint though.
>>
> Why not ?

    Solutions to problems always cause other problems; therefore I'm
against solutions to non-existing problems. So, to begin with,  what is
the problem with not having /boot a partition per se?

    If your /boot is a partition, then you will need to check carefully
its available size before you upgrade linux-image. Failing to do so may
cause failure to install the kernel or the initrd and then to update
grub, and you might not notice the message within the flow of messages
caused by updating many other packages in the same time. Then next boot
will fail.

    In general spreading your OS over many partitions causes the same
kind of problems for all of them, there is always too much space
allocated to one and not enough to another, and, anyway, the loss of any
of them makes your system hardly recoverable. Therefore just have one,
except for /home, of course, and for the temporary directories.

    /run is automatically on tmpfs in Debian/Devuan, and /dev on
devtmpfs, but I recommend tmpfs also for /var/run, and it is
questionable for /tmp. But for OS permanent storage, one filesystem is
my choice.

    So my advice is: don't create problems by inventing solutions to
non-existing ones. Which is also a reason to avoid systemd, btw.

--     Didier