From owner-freebsd-hackers@FreeBSD.ORG Mon Oct 30 21:05:17 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 36C0E16A510 for ; Mon, 30 Oct 2006 21:05:17 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.FreeBSD.org (Postfix) with SMTP id 3761143D64 for ; Mon, 30 Oct 2006 21:05:16 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 17452 invoked by uid 399); 30 Oct 2006 21:05:15 -0000 Received: from localhost (HELO ?192.168.0.7?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 30 Oct 2006 21:05:15 -0000 Message-ID: <45466902.5090603@FreeBSD.org> Date: Mon, 30 Oct 2006 13:05:06 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: "Simon L. Nielsen" References: <20061029222847.GA68272@marvin.astase.com> <20061030003628.42bc5f8d@loki.starkstrom.lan> <45455f6a.yNcc0kkyEKpoRv3m%perryh@pluto.rain.com> <20061030083849.GB871@turion.vk2pj.dyndns.org> <20061030103151.GD871@turion.vk2pj.dyndns.org> <20061030202030.GB1043@zaphod.nitro.dk> In-Reply-To: <20061030202030.GB1043@zaphod.nitro.dk> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: perryh@pluto.rain.com, 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: Mon, 30 Oct 2006 21:05:17 -0000 Simon L. Nielsen wrote: > Personally I think rm should do what you ask it to do - if you ask it > to overwrite a file which has multiple links, well... though luck. Sorry, I disagree. It's not always obvious to the user when a file has hard links, and I can't see any situation where the pre-recent-patch behavior (overwriting the actual file when using -P on a hard link) is the expected outcome. It's all well and good to say, "tough luck," but I don't think that's what our users expect. Doug -- This .signature sanitized for your protection