The classic Unix horror story
lug.wsu.edu
The classic Unix horror story
1–10 of 54 posts
Re: The classic Unix horror story
#2Re: The classic Unix horror story
#3 $ cd /etc
$ chmod 600 some_file * # instead of some_file.*
oops... Thank God for boot diskettes.Re: The classic Unix horror story
#4Pretty please do not create such a directory in this comments thread.
Re: The classic Unix horror story
#5I still remember my "rm -fr /" episode after almost 20 years. It was slightly different, something related to chmod'ing some files under /etc on an AIX server: $ cd /etc $ chmod 600 some_file * # instead of some_file.* oops... Thank God for boot diskettes.
I managed to Ctrl-C it before it ate any files in /home, but I still had some nasty cleanup work to get the computer back in working order again. Thank god for LiveCDs.
Re: The classic Unix horror story
#6Re: The classic Unix horror story
#7Re: The classic Unix horror story
#8Not as hard-core as the recovery through emacs, but greatly welcome under stress.
Re: The classic Unix horror story
#9Late at night, I was tarring up a finished project right before emailing it to my professor. I ran:
tar -cvf *.cpp *.h something.tar
instead of: tar -cvf something.tar *.cpp *.h
It happily wrote most of my project into a tar file on top of the first source file, then complained that something.tar didn't exist. I overwrote "array.cpp" or something like that, and had to rewrite it (this was before I used source control for anything, and a large part of why I learned to use source control).Writing this comment, I had to look up the order of the parameters to tar; I still can't remember. Stupid tar.
Re: The classic Unix horror story
#10 o typing 'halt' into the wrong xterm, shutting down well planners
o and likely on the same network, jacking up the NIS+ on Solaris
It's been a constant itch that I never did manage to understand what I was doing wrong, such that NIS+ wouldn't restart correctly.