the one that gave me the long heart stoppage was long, long ago on an old v7 pdp that had many local hacks (resume from core on power fail, for example :-) that crashed regularly during finals week. so i'm the freshman that comes in at 2am when the seniors are panicing.
eventually i type (on the la-120 line printer console) something like: ncheck /dev/diskname > /dev/diskname instead of: ncheck /dev/diskname > /tmp/logfile about 5 seconds after i hit return i realized what i had done and felt my heart stop. luckily ncheck (or icheck or dcheck) didn't produce output until it had been running for quite some time, so i managed to not stomp all over the superblock. shortly thereafter we installed bsd 2.9 which had fsck, plus the system stopped crashing all the time. On 2011-05-13 15:54, Tom Perrine wrote: > Those of you not in #lopsa (shame on you!) are missing a great thread... > > Great typos, the best way to destroy a system, unexpected command line > results... > > Here are a few: > > Reformatting a partition that was in use > rm -rf .? > removing /lib/libc.so > > So, what's your most memorable command line typo, "think-o", > "brain-fart", or "#$$@#$*&@#$" moment? > > What subtle opportunity for massive destruction would you pass on as a > warning to the next generation of system administrators? > > Don't limit yourself to bash/csh, feel free to explore databases, > storage and network catastrophes! > > "Share and enjoy" > > --tep > _______________________________________________ > Discuss mailing list > [email protected] > https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss > This list provided by the League of Professional System Administrators > http://lopsa.org/ > _______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
