Why, instead of safely entering a BIOS setup, does the cell phone brick when installing the Custom ROM wrongly? Wouldn’t this protection be better for users? I mean, this could be done through ADB.

Also, do you think it’s possible that this way of doing things will come to the computer, with ARM hoping to gain a good share of the market and all?

  • rhythmisaprancer@moist.catsweat.com
    link
    fedilink
    arrow-up
    3
    ·
    3 months ago

    I switched to a Linux OS in '08 and haven’t really paid attention since. I’ve done a little partition work but I’m no superuser… I probably have a UEFI and don’t know it. My days of using the bible are gone haha

    • Snot Flickerman
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      3 months ago

      That’s not a guarantee.

      UEFI uses GUID Partition Tables (GPT) instead of a Master Boot Record (MBR) and needs an EFI partition.

      I personally recall Linux in 08 had pretty abysmal UEFI/GPT support. I’d say support didn’t become as good until about 2015-2016ish.

      So you very well may still be using traditional MBRs if you haven’t really changed your setup.

      Especially since a lot of UEFIs come with a compatability layer to mimic BIOS and allow some backward compatability.

      • rhythmisaprancer@moist.catsweat.com
        link
        fedilink
        arrow-up
        2
        ·
        3 months ago

        Late reply since I’ve been in the field - I no longer have to worry about partition space for kernels, that is nice. Using mobile rn but I will look when I get on my computer.