3 ms·
'This usually leads to screenfuls of error messages and users praying that in this megabyte of binary garbage no valid shell commands occur' hit a nerve.
by justintnt 16y ago
'This usually leads to screenfuls of error messages and users praying that in this megabyte of binary garbage no valid shell commands occur'
hit a nerve.
- hysterix 16y agoYeah I had a good laugh because it explains (at least some) of the times I've seen my shell behave like this.
- InclinedPlane 16y agoA similar problem is accidentally dumping binary data to the terminal screen (via an incautious grep, for example), as various bytes get rendered as their corresponding control characters. This is even worse on windows (or at least used to be, I think Win 7 fixed this) where ^G is hard-wired to the system speaker which is fairly difficult to mute effectively.
- varjag 16y agoThat's a bit more innocent though, since reset(1) usually helps.
- bradleyland 16y agoEven more terrifying. During my early days of Unix usage, I accidentally (through tab completion and incompetence) executed `source ~/.bash_history`. The outcome was not good.