• krnl386@lemmy.ca
    link
    fedilink
    arrow-up
    18
    arrow-down
    1
    ·
    11 months ago

    Ah yes, simplicity. MBR, with all its limitations had one killer feature: it was extremely simple.

    UEFI, as powerful as it is, is the opposite of simple. Many moving parts, so many potential failure points. Unfortunately, it seems like modern software is just that: more complex and prone to failure.

    • 0x4E4FOP
      link
      fedilink
      English
      arrow-up
      7
      ·
      11 months ago

      Exactly why old devices are so hard to break - they’re incredibly simple.

      To be honest, I see nothing wrong with MBR boot, it does the job, I’ll use it till I can or till it doesn’t do the job I want/need.

    • rab@lemmy.ca
      link
      fedilink
      arrow-up
      6
      ·
      11 months ago

      I work in IT for many years and I think your last sentence is very true. And is also why the industry is so lucrative haha

    • Tommi Nieminen@lemm.ee
      link
      fedilink
      arrow-up
      3
      ·
      11 months ago

      True, but… When MBR Grub drops to rescue or doesn’t appear at all, it’s not only difficult (at least for newbies) but somewhat random if you can actually boot a given OS. With EFI Grub, I’ve often managed to boot using BIOS boot override to launch a usable Grub configuration.

      • 0x4E4FOP
        link
        fedilink
        English
        arrow-up
        1
        ·
        11 months ago

        You just fix grub with a live usb, it’s not that difficult.

        • Tommi Nieminen@lemm.ee
          link
          fedilink
          arrow-up
          3
          ·
          11 months ago

          “Not that difficult” but still more difficult than being able to boot without a separate live USB drive.

          • 0x4E4FOP
            link
            fedilink
            English
            arrow-up
            1
            ·
            11 months ago

            OK, I would agree with that.

      • krnl386@lemmy.ca
        link
        fedilink
        arrow-up
        1
        ·
        11 months ago

        Actually grub 0.x series had much more useful rescue shell tab completion than the latest release. You could easily list all boot devices, partitions, and even filesystems and their contents. All from the rescue shell. Consequently, you could boot into Linux and reinstall grub in the MBR to fix it. All that without using a boot CD/USB! Good luck doing that with the latest version of grub and UEFI.

        Also getting into the BIOS on legacy firmware was also very simple. On most machines it’s the three finger salute followed by either F1, Delete or rarely F11 or F12.

        The boot process was simple, and the BIOS had just one simple task: load and execute the first 512 bytes of the disk that was designated as the boot device. That’s it.

        • 0x4E4FOP
          link
          fedilink
          English
          arrow-up
          3
          ·
          11 months ago

          Asus --> Del - Enter BIOS, F8 - Boot menu (very confusing since Windows also uses F8 for the recovery mode boot menu, so you have to press F8, then when the boot menu appears, chose the boot device, then have one hand on Enter and the other on F8 again, so that you hit Enter and start tapping like crazy on F8 to enter the rescue mode menu… annoying as hell)

          GigaByte --> Del or F2 - Enter BIOS, F12 - Boot menu, Alt + F10 - Copy main BIOS to backup BIOS

          MSI --> Del or F2 - Enter BIOS, F11 - Boot menu

          ASRock --> Del or F2 - Enter BIOS, F11 or F10 - Boot menu

          Biostar --> Del - Enter BIOS, F9 - Boot menu

          Intel --> F2 - Enter BIOS, F10 or F12 - Boot menu

          I used to remember some of the brand name PCs as well, but time has gotten the best of me 🤷.

          The boot process was simple, and the BIOS had just one simple task: load and execute the first 512 bytes of the disk that was designated as the boot device. That’s it.

          This is actually what I love about MBR nowadays. It’s simple enough so no one wants to mess with it and render the rig unbootable and obscure enough so no one (MS) actually checks if there is anything there that might trigger warnings (non-MS code).