From owner-freebsd-bugs  Wed Oct 23 00:10:07 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id AAA29800
          for bugs-outgoing; Wed, 23 Oct 1996 00:10:07 -0700 (PDT)
Received: (from scrappy@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id AAA29788;
          Wed, 23 Oct 1996 00:10:03 -0700 (PDT)
Date: Wed, 23 Oct 1996 00:10:03 -0700 (PDT)
From: "Marc G. Fournier" <scrappy>
Message-Id: <199610230710.AAA29788@freefall.freebsd.org>
To: zach@blizzard.gaffaneys.com, scrappy, freebsd-bugs
Subject: Re: bin/1377
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Synopsis: mv(1) retains the setuid bit when it is unable to preserve the uid.

State-Changed-From-To: feedback-open
State-Changed-By: scrappy
State-Changed-When: Wed Oct 23 00:09:24 PDT 1996
State-Changed-Why: 

It still exists in 2.1.5-RELEASE.  I will see what I can do to fix
that particular problem, meaning make it emulate cp(1) if it cannot
preserve permissions.  That seems to be the most sane route to take at
this point (and the mv(1) man page says that is does in fact emulate
cp(1) in the case of permissions).
 
I just grabbed the 2.2 source to see if it existed there too, assuming
ftp://freebsd.cdrom.com/pub/FreeBSD/FreeBSD-current/src/bin/mv is a
current snapshot. (it does)
 
There was a short discussion about what the behavior of mv(1) should
be in that situation, but I don't think anything came of it.
 
-- 
Zach Heilig (zach@blizzard.gaffaneys.com) | ALL unsolicited commercial email