Date: Sat, 2 Oct 2004 21:09:46 -0600 From: Tillman Hodgson <tillman@seekingfire.com> To: freebsd-hackers@freebsd.org Subject: Re: Protection from the dreaded "rm -fr /" Message-ID: <20041003030946.GV35869@seekingfire.com> In-Reply-To: <20041002.192951.35870461.imp@bsdimp.com> References: <20041002175517.GA2230@gothmog.gr> <20041002204851.K24332@fw.reifenberger.com> <20041002210554.GS35869@seekingfire.com> <20041002.192951.35870461.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Oct 02, 2004 at 07:29:51PM -0600, M. Warner Losh wrote:
> In message: <20041002210554.GS35869@seekingfire.com>
> Tillman Hodgson <tillman@seekingfire.com> writes:
> : It'll never work, though, that's the thing. At some point it'll rm
> : something it itself needs and error out. There isn't a way to use `rm
> : -rf /` that /doesn't/ result in foot-shooting.
>
> No. You are wrong. if you rm -rf in a chroot, then it won't result
> in foot shooting, necessarily, like it would outside a chroot.
If you're chrooted, where is the rm binary and associated libraries?
They're in the chroot, in a branch off hte virtual / tree root.
`rm -rf /`, even in chroot, won't delete everything that the command
looks like it will. At the very least the final unlink, that of /
itself, will likely result in undefined behaviour. Where do the dev's
go if there's no / to root them in? etc etc.
-T
--
"Waking a person unnecessarily should not be considered a capital crime.
For a first offense, that is."
-- Robert Heinlein
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041003030946.GV35869>