41–50 of 183 posts
It reminds me of the Russian Linux Roulette... [ $[ $RANDOM % 6] = 0 ] && rm -rf / || echo '*Click*' But it's a bit boring. So there's also an improved version [0], which deletes a random file from the system instead of everything. alias roulette='[ $[ $RANDOM % 6 ] == 0 ] && rm -f $(shuf -n1 -e *) && echo "BOOM" || echo *Click*' [0] https://gist.github.com/mjkaufer/85bb5f800525245942a8
> Perhaps rm -rf / should be replaced with something with more verbose flags set. That way, when you run a bad command, you are told immediately that things are being deleted This gives me an idea: Hell Linux. In Hell Linux, the operating system does its best to pretend that nothing is wrong, so it takes you as long as possible to realize that you've made a mistake. Commands ignore all unrecognized flags. In shell sc…
That's a bit extreme. You should at least allow some error messages. Though those ones should just say "Oops, something went wrong :)"
This is like that time, last week, when I was having issues with do-release-upgrade and someone helpfully suggested to run sudo apt-get purge python* && sudo apt-get autoclean && sudo apt-get install python* Which I did without paying attention to what I was doing and it turns out that this is one of the worst things you could do ever on a Debian-based distro. Damn you, abu-ahmed al-khatiri.
That's why dnf (the yum successor) has dns, sudo, systemd, systemd-udev and yum set as protected packages by default on Centos 8 (and you can't remove python withouth removing dnf/yum because of dependencies, so it should stop that as well). I imagine apt has something similar, and maybe it's not (or wasn't) set by default on the dist you're running? If not, I would raise that as a bug with the distro, as breaking it…
It reminds me of the Russian Linux Roulette... [ $[ $RANDOM % 6] = 0 ] && rm -rf / || echo '*Click*' But it's a bit boring. So there's also an improved version [0], which deletes a random file from the system instead of everything. alias roulette='[ $[ $RANDOM % 6 ] == 0 ] && rm -f $(shuf -n1 -e *) && echo "BOOM" || echo *Click*' [0] https://gist.github.com/mjkaufer/85bb5f800525245942a8
First one requires --no-preserve-root to be effective on GNU tools ;)
rm -rf /*
This is like that time, last week, when I was having issues with do-release-upgrade and someone helpfully suggested to run sudo apt-get purge python* && sudo apt-get autoclean && sudo apt-get install python* Which I did without paying attention to what I was doing and it turns out that this is one of the worst things you could do ever on a Debian-based distro. Damn you, abu-ahmed al-khatiri.
Coworker was trying to remove node so we could install a new version, so he ran:
rm -rf /usr/bin node
-rf was due to muscle memory, and unfortunately he forgot the space.
That was a fun one to clean up. We were able to use nc because that was in /bin and not /usr/bin, so we used that to pipe curl over through a socket and then used curl to install dpkg + apt, then ran apt update to fix everything and that seemed to work.
That server is still running today, but I'm sure something is still seriously wrong with it. Nothing that affects me though, so I don't care haha.
> Perhaps rm -rf / should be replaced with something with more verbose flags set. That way, when you run a bad command, you are told immediately that things are being deleted This gives me an idea: Hell Linux. In Hell Linux, the operating system does its best to pretend that nothing is wrong, so it takes you as long as possible to realize that you've made a mistake. Commands ignore all unrecognized flags. In shell sc…
Initially, I though you were talking about the lastest MacOS. You had me there for a second.
> Perhaps rm -rf / should be replaced with something with more verbose flags set. That way, when you run a bad command, you are told immediately that things are being deleted This gives me an idea: Hell Linux. In Hell Linux, the operating system does its best to pretend that nothing is wrong, so it takes you as long as possible to realize that you've made a mistake. Commands ignore all unrecognized flags. In shell sc…
> Perhaps rm -rf / should be replaced with something with more verbose flags set. That way, when you run a bad command, you are told immediately that things are being deleted This gives me an idea: Hell Linux. In Hell Linux, the operating system does its best to pretend that nothing is wrong, so it takes you as long as possible to realize that you've made a mistake. Commands ignore all unrecognized flags. In shell sc…
> 0 exit code is reported for all processes, no matter how they terminate.
These two things are mutually exclusive - shell script branching is usually based off of exit codes.
Earlier quoted context omitted.
That's a bit extreme. You should at least allow some error messages. Though those ones should just say "Oops, something went wrong :)"
Or perhaps the famous ? from ed :)
The only message for all syntax errors, is:
WHAT?
HOW?
SORRY