Date: Mon, 30 Oct 2006 13:05:06 -0800 From: Doug Barton <dougb@FreeBSD.org> To: "Simon L. Nielsen" <simon@FreeBSD.org> Cc: perryh@pluto.rain.com, freebsd-hackers@freebsd.org Subject: Re: [patch] rm can have undesired side-effects Message-ID: <45466902.5090603@FreeBSD.org> In-Reply-To: <20061030202030.GB1043@zaphod.nitro.dk> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45466902.5090603>