4 ms·
Almost 20 years ago I typed "rm /lib" instead of "rm lib" by mistake. Kernel panic messages started to flash on the terminal and I felt butterflies on my stomac
by scardine 12y ago
Almost 20 years ago I typed "rm /lib" instead of "rm lib" by mistake. Kernel panic messages started to flash on the terminal and I felt butterflies on my stomach. It was a huge (at the time) Sun machine, took more than 12h to restore it.
That is why I avoid running as root.
- chillingeffect 12y agolol, we should have a thread about famous typos. The other late evening, I typed "sudo pip uninstall pip" instead of "sudo pip uninstall pil" Not that bad, but i was on an outdated distro (13.04) and I couldn't apt-get pip back. :< It was time to move to 13.10 anyway.
- rglullis 12y agowhat? `sudo apt-get install python-pip --reinstall` wouldn't work?
- jlarocco 12y agoUsing Linux or OSX on a modern single user computer, the separation between root and non-root makes very little sense. I don't care if I "rm -Rf /bin" because I can reinstall all of it in less than an hour. It's an inconvenience, but hardly the end of the world. On the other hand, "rm $HOME/*" would be a huge pain in the ass, potentially losing personal data that I can't just "apt-get install _____" back. It does make sense for shared computers, but not many people running OSX and desktop Linux are running on shared computers.
- marvy 12y agothat's what time machines are for