From: rsalz@osf.org
To: rc@hawkwind.utcs.toronto.edu
Subject: Why featureful shells can be bad
Date: Mon, 22 Feb 1993 10:37:57 -0500 [thread overview]
Message-ID: <9302221537.AA11536@earth.osf.org> (raw)
Here's a fun story. The machine rodan.uu.net is the central server
for internal stuff at UUNET; it's where staff gets their email,
has their homedirs, etc. Well for some reason there was a file
/usr/spool/mqueue/=sendmail file, but no /usr/lib/sendmail.
Someone cp'd the latter, and tried to remove the former
rm =sendmail
Well, in zsh "=foo" means "expand to the full path of the exectuable of foo.
Zap, away went /usr/lib/sendmail AGAIN and nobody at uunet got email for
an hour or two.
Two iterations of this.
/r$
reply other threads:[~1993-02-22 15:38 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=9302221537.AA11536@earth.osf.org \
--to=rsalz@osf.org \
--cc=rc@hawkwind.utcs.toronto.edu \
/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).