From owner-freebsd-bugs  Tue Jul  9 18:49:39 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id SAA24906
          for bugs-outgoing; Tue, 9 Jul 1996 18:49:39 -0700 (PDT)
Received: from mole.mole.org (marmot.mole.org [204.216.57.191])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA24896
          for <freebsd-bugs@freefall.freebsd.org>; Tue, 9 Jul 1996 18:49:36 -0700 (PDT)
Received: (from mail@localhost) by mole.mole.org (8.6.12/8.6.12) id BAA02023; Wed, 10 Jul 1996 01:49:15 GMT
Received: from meerkat.mole.org(206.197.192.110) by mole.mole.org via smap (V1.3)
	id sma002019; Wed Jul 10 01:48:52 1996
Received: (from mrm@localhost) by meerkat.mole.org (8.6.11/8.6.9) id SAA28951; Tue, 9 Jul 1996 18:48:52 -0700
Date: Tue, 9 Jul 1996 18:48:52 -0700
From: "M.R.Murphy" <mrm@MARMOT.Mole.ORG>
Message-Id: <199607100148.SAA28951@meerkat.mole.org>
To: bde@zeta.org.au, zach@blizzard.gaffaneys.com
Subject: Re: bin/1375: Extraneous warning from mv(1)
Cc: freebsd-bugs@freefall.freebsd.org
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> mv cannot know if the user cares, so it shouldn't silently drop
> attributes.  I now think it should refuse to the move if it can't
> preserve all the attributes.  It can simply unlink the target and
> avoid unlinking the source if there is a problem.

Or, one could leave it as it is, and accept the known, rather predictable,
and simple behavior instead of a more complicated and unknown behavior.

--
Mike Murphy  mrm@Mole.ORG  +1 619 598 5874
Better is the enemy of Good. If it ain't broke, don't fix it.