(no title)
feikname | 3 years ago
Agreed.
> It wasnt windows's fault its just that its update utility had to overwrite a part of MBR
It was a reasonable assumption that whatever drive Windows' was installed on already had a working bootloader installed, otherwise it wouldn't have been able to boot itself to do Windows Update. Windows did NOT have to override it.
This was not MBR fault. AFAIK Linux did NOT do the same thing as overriding, which is why it has separate `grub2-install` and `update-grub` commands. Once installed to a drive, `update-grub` will only change the simple config file it reads at boot. Perhaps both of them did override themselves when a bugfix or new feature was available, but I don't think Windows's bootloader changed much after any OS release.
Now, GPT/UEFI is a million times better in that aspect because it can allow easily multiple different bootloaders that don't have to know of each other's existence. But I blame Windows in MBR case very much.
Also, some though not all motherboards allow you booting from BOTH old-school MBR and newer GPT so you may not need to disable CSM and still eat your GPT cake. This may be useful if you e.g. have an old MBR drive with Linux and another GPT one with Windows.
No comments yet.