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.
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.
“beyond repair” my ass, this is Linux
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.
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.
Maybe its also a ship of theseus type situation. If you have to copy /etc/ from somewhere else, is it still the same installation?
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…
exactly lol.
“wtf is a ‘boot/efi’ directory, seems stupid, bye bye!”
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
rm -rf /in UEFI system, no more return.Related articles
Laughs in NixOS (while still spending the next few days going insane trying to figure out what isn’t in config qq)
THANK GOD we have this failsafe now:
rm: it is dangerous to operate recursively on '/' rm: use --no-preserve-root to override this failsafeLinus Sebastian: “Why do I hear boss music?”
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.
testdiskentered the chat. (Kind of a challenge though but still)Yes, but many modern mainboards do feature two UEFI copies and can switch to the backup on the fly - and most let you restore a bricked UEFI from a USB drive. Not sure if this can help here or even work on this situation, but it might be worth a try.
In Ubuntu you used to be able to delete the UEFI firmware from the motherboard.