On Tue, May 14, 2024 at 8:13 PM Tim via users <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > Does /boot still need to be its own partition, these days? > /boot/efi has to be, but that's mapped into /boot, already. Definitely not. And it actually creates all kinds of problems when separated. The best *trivial* setup and usage should be having everything on BTRFS (except EFI, as you said), and maintain some amount of snapshots you can revert to anytime in case of any issues. When /boot is on the BTRFS, the snapshot contains the whole system, and ensures bootability of the snapshots. When /boot is on a standalone partition, the snapshot contains kernel modules, but not the actual kernel. When booting a new kernel (from /boot) with old kernel modules (from the snapshot), the modules can't be loaded, leaving you with a kind of crippled system. (bootable, but only partly usable) Which is far from what people would usually expect. -- A better, but more complicated setup consists of various snapshots of various subvolumes which are mounted to various locations. (e.g. standalone subvolumes for /home, games, backups, ... whatever) Often managed by some software (snapper, timeshit, ... not sure about the specific names), rather than the btrfs commands themselves. -- I managed to craft a setup that changes which snapshot (or which OS) will boot by changing just a single symlink. That too would be (likely ?) impossible with /boot on a separate partition. -- Michal Schorm Software Engineer Core Services - Databases Team Red Hat -- On Tue, May 14, 2024 at 8:13 PM Tim via users <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > On Tue, 2024-05-14 at 08:27 -0700, richard emberson wrote: > > Back on 05/03/2024 I posted the question: > > "How to increase size of /boot partition" > > I had the same problem. > > > > As was noted by some, I had not upgraded for a long, long time: > > "This type of layout and partition sizes is ancient. /tmp isn't even a partition now." > > Does /boot still need to be its own partition, these days? > > /boot/efi has to be, but that's mapped into /boot, already. > > > -- > > NB: All unexpected mail to my mailbox is automatically deleted. > I will only get to see the messages that are posted to the list. > > The following system info data is generated fresh for each post: > > uname -rsvp > Linux 6.2.15-100.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Thu May 11 16:51:53 > UTC 2023 x86_64 > -- > _______________________________________________ > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
