3 ms·
Because it's old. Because it's painfully slow. Because messing with a FAT partition feels much better than messing with MBR or whatever weird "boot partition" t
by floatboth 9y ago
Because it's old. Because it's painfully slow. Because messing with a FAT partition feels much better than messing with MBR or whatever weird "boot partition" thing that happens in a "legacy-BIOS-plus-GPT" situation.
- int_19h 9y agoWho said anything about GPT? I use MBR partitioning as well. Again, it's simple, and it works for my purposes, why change it? And I don't consider a few seconds to be "painfully slow" for something that is done maybe once a week, if that (suspend is there for a reason...). As far as "messing with MBR", why is that somehow problematic? MBR was specifically designed for this exact purpose - hosting a partition table and a boot loader. And there are tools to do precisely what needs to be done to it, and these tools have been there for a very long time - so I'm confident that they work right. On top of that, MBR structure is simple enough that I can manually inspect or edit it with dd directly on the block device in question.