Those who do not delete history are destined to reparse it.
-
-
- End of conversation
New conversation -
-
-
Shouldn’t have done anything right? Because prepended numbers?
-
No numbers on my system - I guess the history command adds them itself
-
Kind of want to try this now.
End of conversation
New conversation -
-
-
I once ran rm -rf / home/olduser, complete with the space, so I feel your pain :(
-
Tip from a colleague: when rm -rf’ing, put the argument in double quotes. If you accidentally put a space in the result is file not found rather than disaster. (Yes I have had a disaster...)
-
This should be enforced by rm rf somehow
-
With great power comes great responsibility
-
apt install safe-rm
End of conversation
New conversation -
-
-
Ehe, Poor man's ansible.
-
Ansible is the poor mans Ansible.
End of conversation
New conversation -
-
-
What happens, when you do that? I am scared to try it out myself.
-
It runs all the last commands that you ran (arround 1000 are saved)
-
I save forever, so I better don't do this :P
-
Actually, the history file starts each line with an index number, which will let each line fail with 'unknown command 147' etc, IIRC
-
Not with bash, depends on your shell I guess
End of conversation
New conversation -
-
-
The worst typo of my life was supposed to be "ls /bin | grep sh" but instead I typed "ls /bin | sh grep", it was the primary firewall on a five nines telco setup. When I finally got physical access even the disks were wiped, thankfully there was a hot standby. Could be worse :)
-
I once accidentally fsck-ed the root disk of a live server, which didn't lose much data, but did confuse running processes and eventually tanked the kernel, and produced much swearing and eye-rolling in my general vicinity for some time
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.