11–20 of 54 posts
frequent automated offsite backups are your friend
$ chown -R terra_t.terra_t /
on a production system. Fortunately I was able to recover the permissions of most of the system files from the rpm database, and do the rest by hand...
One should be careful making such damage threats though, may end up with male appendage replacing rabbit foot on someones' keychain
Man, how many times is this story going to be submitted?
frequent automated offsite backups are your friend
Yes, but too bad that frequent offsite automated backups were still at least a decade off in 1986. At the very least, the network bandwidth just simply wasn't there. Heck, at this stage of the game, 1Mbps was considered to be blazing fast on a LAN. Even Internet backbones were 56k.
but you're right, networking speed/bandwidth has gotten better since then, but that's irrelevant and I never claimed it hadn't. my point was that there is a simple, well-known solution/palliative for this, so no need for this kind of drama going forward.
I've never actually been bitten by rm (or done anything remotely this badass) but in college I did have a bad Unix moment: Late 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…
Fortunately, they are only virtual fingers and we can grow them back on demand with adequate preparation, unlike real ones. :)
My terrible UNIX, or really SunOS/Solaris moments have been: 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.
Is there a "social news sites classics" directory yet? I would love to see reposts of oldies no longer justified due to a good directory of these things, prominently linked. Pretty please do not create such a directory in this comments thread.
I've never actually been bitten by rm (or done anything remotely this badass) but in college I did have a bad Unix moment: Late 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…
The -f (--file) flag takes an argument. So you could do:
tar -cf *.cpp -f something.tar