From: ron@ronnatalie.com (Ron Natalie)
Subject: [TUHS] Runaway rm -r
Date: Mon, 24 Apr 2017 20:13:47 -0400 [thread overview]
Message-ID: <05b301d2bd58$cf338ec0$6d9aac40$@ronnatalie.com> (raw)
There was an incident at Pixar that a runaway rm ate most of the Toy Story 2
movie. The only thing that saved them was an employee had their own copy
on a machine at home.
We never lost the whole disk through one of these, but we did have a guy
wipe out /etc/passwd one day. Our password fields had an rfc-822ish user
name in the gcos field, so it looked
something like:
ron::51:50:Ronald Natalie <ron>:/sys1/ron:
Well, one of our users decided to grep for a user (alas while root) with the
command
grep <howard> /etc/passwd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170424/d87239fc/attachment-0001.html>
reply other threads:[~2017-04-25 0:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='05b301d2bd58$cf338ec0$6d9aac40$@ronnatalie.com' \
--to=ron@ronnatalie.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).