One of my colleagues managed to accidentally run something like rm -rf /var/tmp/ * on a Solaris machine that was the mail server for the entire organisation.
After the command finished they realised that the inadvertent space in front of the asterisk meant that the command did slightly more damage than intended.
They were told to leave the machine running to be able to fix it from a backup, but they rebooted instead.
An open file is still usable even after it’s been deleted, so the kernel and shell were still up and running … before the reboot …
If I recall, it took weeks to fix, involving floppy disks, Sun engineers and much egg on face.
wildbus8979@sh.itjust.works 11 months ago
Remember kids, you gotta use
rm -rf --no-preserve-root /now a days!Barbarian@sh.itjust.works 11 months ago
rm -rf /*will work just fine.You need the additional flag for
rm -rf --no-preserve-root /.Kowowow@lemmy.ca 11 months ago
What is that for?
TropicalDingdong@lemmy.world 11 months ago
Image
ImplyingImplications@lemmy.ca 11 months ago
Too many people got trolled into “removing the French language pack” on Linux systems that there’s now a check to see if someone is deleting every file off their computer (including the os system files). --no-preserve-root is the option you need to include to actually delete all the files off your system.
wander1236@sh.itjust.works 11 months ago
Contrary to the memes, Linux does actually sometimes try to stop you from shooting yourself in the foot
CCF_100@sh.itjust.works 11 months ago
Overrides the protection in place that prevents you from deleting the root of your filesystem.