From owner-freebsd-hackers@FreeBSD.ORG Sat Oct 2 17:55:25 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A227D16A4D1 for ; Sat, 2 Oct 2004 17:55:25 +0000 (GMT) Received: from kane.otenet.gr (kane.otenet.gr [195.170.0.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A53A43D2F for ; Sat, 2 Oct 2004 17:55:22 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from gothmog.gr (patr530-b208.otenet.gr [212.205.244.216]) i92HtJjZ011612; Sat, 2 Oct 2004 20:55:20 +0300 Received: from gothmog.gr (gothmog [127.0.0.1]) by gothmog.gr (8.13.1/8.13.1) with ESMTP id i92HtIUK002271; Sat, 2 Oct 2004 20:55:18 +0300 (EEST) (envelope-from keramida@freebsd.org) Received: (from giorgos@localhost) by gothmog.gr (8.13.1/8.13.1/Submit) id i92HtHtL002270; Sat, 2 Oct 2004 20:55:17 +0300 (EEST) (envelope-from keramida@freebsd.org) Date: Sat, 2 Oct 2004 20:55:17 +0300 From: Giorgos Keramidas To: Tillman Hodgson Message-ID: <20041002175517.GA2230@gothmog.gr> References: <20041002081928.GA21439@gothmog.gr> <200410021123.59811.max@love2party.net> <20041002102430.Y5481@thor.farley.org> <20041002165155.GP35869@seekingfire.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041002165155.GP35869@seekingfire.com> cc: freebsd-hackers@freebsd.org Subject: Re: Protection from the dreaded "rm -fr /" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Oct 2004 17:55:25 -0000 On 2004-10-02 10:51, Tillman Hodgson wrote: > On Sat, Oct 02, 2004 at 10:42:16AM -0500, Sean Farley wrote: > > Why not default on? root will not run 'rm -rf /' on purpose very often. > > Once will be enough. :) Also, when and why would someone want to do > > this? > > Exactly. Who would expect `rm -rf /` to actually succeed? It's not only > dangerous, it doesn't work in a useful way ;-) > > If one is thinking about `rm -rf /`, `newfs` is probably the right > answer. And a hell of a lot faster too. This is the *only* reason why I initially wrote this.