3 ms·
I don't think we're understanding each other. A cp command can populate a filesystem, but it won't create a new partition (or filesystem), which is what I was a
by yjftsjthsd-h 3y ago
I don't think we're understanding each other. A cp command can populate a filesystem, but it won't create a new partition (or filesystem), which is what I was asking about. You can't just handwave away "make a new boot partition", because part of the problem is that systems in the wild are unlikely to have free disk space sitting around for you to create a new partition in.
> Only because Linux bootloaders suck as they completely fall over when misconfigured.
Have you got a bootloader that doesn't do awful things when it has no configuration? I mean, I guess you could write a bootloader that searched through available filesystems and tried to find something it could boot, but that seems like a great way for unexpected surprises on boot (what, you didn't want to default to booting this 6-month-old backup kernel?)
(And it's not just the bootloader config that you have to deal with - like I said, you have to do something to tell the firmware to even run that bootloader)
- charcircuit 3y ago>I don't think we're understanding each other. Then let me explain with English: Move all of your files from the boot partition into the main partition. Then setup the system to boot from the main partition. Since there is likely gigabytes to terabytes free you will not need to worry about a few 30 MiB files being added to the /boot directory.
- fyrn_ 3y agoThat restricts you to using root filesystem that the bootloader can read, which excludes many modern filesystems, btra, f2fs, etc.. Also you would then need a separate efi partition instead of a combined boot and efi setup as is typical these days.
- charcircuit 3y agoSo use a bootloader that can read them then.
- fyrn_ 3y agoYou still have an extra partition, and there just plain aren't any bootloaders that can load those filesystems. You'd pretty much be stuck with ext4 as your most modern filesystem option. Really the kernel should have a better system for loading firmware from the root drive after the bool state that the root drive becomes accessible. Not for everything of course, but many of the biggest firmware blobs are fine as late loaders
- charcircuit 3y ago>You still have an extra partition Which can be reused to store other files. >You'd pretty much be stuck with ext4 as your most modern filesystem option. What do you mean? You can grub boot from a partition that even uses LUKS and ZFS.