From: Christian Kujau <lists@nerdbynature.de>
To: Russell Coker <russell@coker.com.au>
Cc: Ivan Sizov <sivan606@gmail.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Strange behavior after "rm -rf //"
Date: Thu, 11 Aug 2016 23:15:49 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.20.14.1608112315440.8131@trent.utfs.org> (raw)
In-Reply-To: <A0E51DF2-D230-4847-A541-581A8A9C36DB@coker.com.au>
On Fri, 12 Aug 2016, Russell Coker wrote:
> There are a variety of ways of giving the same result that rm
> doesn't reject. "/*" Wasn't caught last time I checked. See the above
> URL if you want to test out various rm operations as root. ;)
Oh, yes - "rm -r /*" would work, even with a current coreutils version.
But since the OP stated "rm -rf //" I was curious about the userspace
part on that.
Thanks for the link to the SELinux playground, nice setup!
Christian.
--
BOFH excuse #346:
Your/our computer(s) had suffered a memory leak, and we are waiting for them to be topped up.
prev parent reply other threads:[~2016-08-12 6:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 16:30 Strange behavior after "rm -rf //" Ivan Sizov
2016-08-08 17:13 ` Chris Murphy
2016-08-08 18:38 ` Ivan Sizov
2016-08-08 18:52 ` Hugo Mills
2016-08-08 19:00 ` Ivan Sizov
2016-08-09 17:10 ` Chris Murphy
2016-08-09 20:30 ` Duncan
2016-08-21 17:54 ` Ivan Sizov
2016-08-08 19:02 ` Duncan
2016-08-09 23:24 ` Christian Kujau
2016-08-12 3:08 ` Russell Coker
2016-08-12 6:15 ` Christian Kujau [this message]
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=alpine.DEB.2.20.14.1608112315440.8131@trent.utfs.org \
--to=lists@nerdbynature.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=russell@coker.com.au \
--cc=sivan606@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.