From: alec.muffett@gmail.com (Alec Muffett)
Subject: [TUHS] There is turmoil in Linux-land - When did rm first avoid going upwards?
Date: Mon, 24 Apr 2017 22:48:33 +0100 [thread overview]
Message-ID: <CAFWeb9K_173PJpm4Rzt_JMt56ZQxQ9Smsg5+kY_DiHfJyifxPw@mail.gmail.com> (raw)
In-Reply-To: <20170424214212.GA4966@naleco.com>
Off-topic but funny: I have personally witnessed a 4.1BSD Vax where someone
accidentally did "mv . .." (or possibly "mv .. .") and it worked, with
resulting horrible mess.
-a
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170424/742c06be/attachment.html>
next prev parent reply other threads:[~2017-04-24 21:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 21:42 Josh Good
2017-04-24 21:48 ` Alec Muffett [this message]
2017-04-24 21:59 ` Arthur Krewat
2017-04-24 22:10 ` Kurt H Maier
2017-04-24 22:06 Noel Chiappa
2017-04-24 22:18 ` Josh Good
2017-04-24 23:23 ` Kurt H Maier
2017-04-25 0:06 ` Ron Natalie
2017-04-25 0:18 ` Kurt H Maier
2017-04-25 0:22 ` ron minnich
2017-04-25 0:24 ` Kurt H Maier
2017-04-25 0:26 ` ron minnich
2017-04-25 0:59 Noel Chiappa
2017-04-25 1:34 Noel Chiappa
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=CAFWeb9K_173PJpm4Rzt_JMt56ZQxQ9Smsg5+kY_DiHfJyifxPw@mail.gmail.com \
--to=alec.muffett@gmail.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).