Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
I've only ever used grub with bios/mbr or a BIOS/gpt (with grub bios partition).
No clue about efi/uefi.
This is the simplest method I can think of.
The arch wiki, however, is, as always, a great source of info:
https://wiki.archlinux.org/title/GRUB
**Linux is amazing in it's ability to keep working even when you accidentally all the things.
Annoyingly so. I once made a backup. Then to confirm it would restore the system, I deleted everything on root path. as in /
It did as told.
OK let's reboot and verify system.
Sudo reboot
Command not found
sudo shutdown
Command not found
But it sat there with a blinking cursor on the terminal
I'm a noob, so forgive me if I'm being very ignorant here, but how on earth could that be a good idea? It sounds like "in order to see if I've installed these airbags correctly I shall now crash head first into this concrete bridge foundation at max speed"?
I'm assuming it's a fresh install, so nothing of value was lost if the restore failed. But also I've heard attempting to delete things in
/sys
and/dev
can brick your computer. So it's not a great idea.I'm not so sure your analogy works. Unless you are testing to see how fast you can bring a new test dummy into production. Or you are testing to see how fast you can install new airbags with blemishes and all.
It gave me a reason to finally run the command that by recursively deleting everything.
It sounded like you were testing the (one and only) backup in a live environment is all.
Not to victim blame but you did put in --no-preserve-root. You had to read those instructions.😄