From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 17:36:24 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A37416A417 for ; Tue, 25 Sep 2007 17:36:24 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from fw.farid-hajji.net (fw.farid-hajji.net [213.146.115.42]) by mx1.freebsd.org (Postfix) with ESMTP id 7EDEF13C45B for ; Tue, 25 Sep 2007 17:36:23 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from epia-2.farid-hajji.net (epia-2 [192.168.254.11]) by fw.farid-hajji.net (Postfix) with ESMTP id AE41FDFDD6; Tue, 25 Sep 2007 19:37:54 +0200 (CEST) Date: Tue, 25 Sep 2007 19:40:08 +0200 From: cpghost To: Daichi GOTO Message-ID: <20070925194008.3c2d7113@epia-2.farid-hajji.net> In-Reply-To: <46F905FD.9060208@freebsd.org> References: <46F905FD.9060208@freebsd.org> Organization: Cordula's Web X-Mailer: Claws Mail 3.0.0 (GTK+ 2.10.14; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: FreeBSD Current , Masanori OZAWA Subject: Re: The safety expansion for FreeBSD rm(1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 17:36:24 -0000 On Tue, 25 Sep 2007 21:58:37 +0900 Daichi GOTO wrote: > Today is not unionfs. Introduction for safety expansion of rm(1). > I know that some unix folks have a experience that you remove some > files or directories accidentally. Yes, me too. LoL > > Have you any dreams that rm(1) autonomously judges target should > be remove or not? To complexify system base command is objectionable > behavior but adding some little and simple mechanism to prevent a > issue is acceptable I suppose. > > We have created safety expansion for rm(1). If you have any interests, > please try follow patch. > > http://people.freebsd.org/~daichi/safety-rm/ > > Thanks :) Interesting idea, but isn't that a violation of POLA? Imagine an unsuspecting sysadmin trying to rm something, and forgetting or not knowing about ~/.rm? Isn't it better to protect important system directories with something like: # chflags sunlink /path/to/dir and unprotect them with # chflags nosunlink /path/to/dir to avoid mistakes? Thanks, -cpghost. -- Cordula's Web. http://www.cordula.ws/