You are going to fuck this up. Don’t come crawling back to me when you lose all your data since the dawn of time and you completely brick this goddamn computer. This is your one and only warning.

    • Azzu@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      81
      ·
      edit-2
      3 days ago

      I guess they meant “beyond repair if you don’t have access to a live boot USB or the means to create one”. Gotta remember who this warning is meant for. For those kind of users, “beyond repair” might technically be true.

      • mormund@feddit.org
        link
        fedilink
        arrow-up
        33
        ·
        3 days ago

        Maybe its also a ship of theseus type situation. If you have to copy /etc/ from somewhere else, is it still the same installation?

        • styanax@lemmy.world
          link
          fedilink
          arrow-up
          15
          ·
          3 days ago

          In modern Linux and assuming you did no pre-filtering or post-processing, no. machine-id systemd is a thing, fstabs commonly use device UUIDs now snd so forth with various subsystems. A laptop GRUB config commonly has the resume UUID set (sleep/hibernation stuff), a server typically has network configs tied to the hardware IDs, and on and on…

      • bigboitricky@lemmy.world
        link
        fedilink
        arrow-up
        10
        ·
        3 days ago

        rolls up sleeves Not if I gave anything to say about it! Watch a master at work missing boot folder missing rescue disk missing OS backups

      • Scubus@sh.itjust.works
        link
        fedilink
        arrow-up
        2
        ·
        2 days ago

        I feel like there is probably some software stuff you could do to permanently fuck the hardware, such as running a resistor at full voltage for a sustained period of time when its only meant to see bursts. Still not truly beyond repair, but you could make it very difficult.

        • kadu@scribe.disroot.org
          link
          fedilink
          arrow-up
          1
          ·
          1 day ago

          Before a relatively recent fix, Linux would mount and expose the folders that contain critical firmware data on your motherboard, meaning you could brick several models of motherboard by deleting or messing with those files.

      • redjard@lemmy.dbzer0.com
        link
        fedilink
        arrow-up
        5
        ·
        3 days ago

        Efi spec states it must be safe to delete all variables. It’s only motherboards not adhering to the spec that are affected, effectively faulty hardware.
        If you do this on a mb from that era chances are nothing will happen, and if something does happen chances are it is recoverable. You’d have to have some truly bad luck on your choice of mb to have it be permanently bricked by that.

      • RyeBread@feddit.org
        link
        fedilink
        arrow-up
        1
        ·
        3 days ago

        Laughs in NixOS (while still spending the next few days going insane trying to figure out what isn’t in config qq)