Don't ever do this on a current bare metal system!
Even if you have everything backed up, plan on re-installing anyway, and just want to see what happens.
On a modern EFI system, recursively deleting everything (including the EFI path) has a chance of permanently hard-bricking your computer!
The CLI has worked great for fifty years and it'll work great for another fifty years.
Fifty years from then? Well, I don't know, it'll probably be nuclear winter and the climate wars. But hey, I'm not going to be here, so until then it's the CLI for me
9 replies
WARNING:
Don't ever do this on a current bare metal system!
Even if you have everything backed up, plan on re-installing anyway, and just want to see what happens.
On a modern EFI system, recursively deleting everything (including the EFI path) has a chance of permanently hard-bricking your computer!
How?
Just systemd things...
https://github.com/systemd/systemd/issues/2402
Wow. Thx for the warning
It's not the 1970s anymore, why are you using the CLI?
The CLI has worked great for fifty years and it'll work great for another fifty years.
Fifty years from then? Well, I don't know, it'll probably be nuclear winter and the climate wars. But hey, I'm not going to be here, so until then it's the CLI for me
Try administering M365/Azure using the admin web UI, and you'll realize CLI usage is more important now than it ever was.
Then congratulations to Microsoft for the hard feat of making a GUI worse than a CLI.
Because a GUI requires more system resources.