From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 2 10:52:37 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 585A916A504 for ; Thu, 2 Nov 2006 10:52:37 +0000 (UTC) (envelope-from jan.grant@bristol.ac.uk) Received: from dirg.bris.ac.uk (dirg.bris.ac.uk [137.222.10.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB6D843D5E for ; Thu, 2 Nov 2006 10:52:36 +0000 (GMT) (envelope-from jan.grant@bristol.ac.uk) Received: from mail.ilrt.bris.ac.uk ([137.222.16.62]) by dirg.bris.ac.uk with esmtp (Exim 4.63) (envelope-from ) id 1GfaBU-0005vC-VF; Thu, 02 Nov 2006 10:52:35 +0000 Received: from cse-jg.cse.bris.ac.uk ([137.222.12.37]:50691) by mail.ilrt.bris.ac.uk with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1GfaBI-0006bL-26; Thu, 02 Nov 2006 10:52:20 +0000 Date: Thu, 2 Nov 2006 10:52:19 +0000 (GMT) From: Jan Grant X-X-Sender: cmjg@tribble.ilrt.bris.ac.uk To: Daniel Valencia In-Reply-To: <20061031161640.71807.qmail@web53907.mail.yahoo.com> Message-ID: <20061102104744.O52313@tribble.ilrt.bris.ac.uk> References: <20061031161640.71807.qmail@web53907.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-ILRT-MailScanner: Found to be clean X-ILRT-MailScanner-SpamCheck: not spam, SpamAssassin (score=-1.228, required 6, autolearn=disabled, ALL_TRUSTED -1.44, AWL 0.21) X-ILRT-MailScanner-From: jan.grant@bristol.ac.uk X-Spam-Status: No X-Spam-Score: -1.3 X-Spam-Level: - Cc: freebsd-hackers@freebsd.org Subject: Re: [patch] rm can have undesired side-effects X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Nov 2006 10:52:37 -0000 On Tue, 31 Oct 2006, Daniel Valencia wrote: > if the file is not writable, return with error. > if the file has multiple links, and option -f was not specified, > return with error. > overwrite the file. > optionally, unlink the file. > > Additionally, -P should either be rm'ed from rm, or added as a > backwards compatibility hack that calls "shred" and returns with error > every time the latter does. > > These are my 1.99 cents. You might as well just truncate the file before removing it. --- Bakul Shah wrote: > If you are that concious about scrubbing why not add > scrubbing as a mount option (suggested option: -o paranoid) > then at least it will be handled consistently. This is, I reckon, the only sensible suggestion thus far: if the FS doesn't help you then you are implicitly depending on the FS implementation to ensure you are writing over the original data blocks anyway. -- jan grant, ISYS, University of Bristol. http://www.bris.ac.uk/ Tel +44 (0)117 3317661 http://ioctl.org/jan/ You see what happens when you have fun with a stranger in the Alps?