From: khm@sciops.net (Kurt H Maier)
Subject: [TUHS] There is turmoil in Linux-land - When did rm first avoid going upwards?
Date: Mon, 24 Apr 2017 15:10:06 -0700 [thread overview]
Message-ID: <20170424221006.GA27654@wopr> (raw)
In-Reply-To: <20170424214212.GA4966@naleco.com>
On Mon, Apr 24, 2017 at 11:42:14PM +0200, Josh Good wrote:
>
> So, to get on-topic, I have a question for UNIX historians: when was it
> first defined in the UNIX realm that "rm -r .*" should NOT delete the
> current and parent directories? Would the command "cd /tmp ; rm -rf .*"
> be able to kill a V6 or V7 UNIX system?
V7 has a dotname function it uses to protect against this.
khm
next prev parent reply other threads:[~2017-04-24 22:10 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
2017-04-24 21:59 ` Arthur Krewat
2017-04-24 22:10 ` Kurt H Maier [this message]
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=20170424221006.GA27654@wopr \
--to=khm@sciops.net \
/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).