From owner-freebsd-bugs Tue Mar 9 1:59:16 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 1F74D14FB4; Tue, 9 Mar 1999 01:59:11 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id UAA08499; Tue, 9 Mar 1999 20:58:52 +1100 Date: Tue, 9 Mar 1999 20:58:52 +1100 From: Bruce Evans Message-Id: <199903090958.UAA08499@godzilla.zeta.org.au> To: freebsd-bugs@FreeBSD.ORG, sheldonh@FreeBSD.ORG, wosch@FreeBSD.ORG Subject: Re: bin/1565 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Synopsis: Moving a file to it's link completely removes file > >Responsible-Changed-From-To: freebsd-bugs->wosch >Responsible-Changed-By: sheldonh >Responsible-Changed-When: Tue Mar 9 00:33:05 PST 1999 >Responsible-Changed-Why: >Closed with his permission. The bug in the PR seems to be fixed, but cross-device moves are still quite broken: (1) $ touch /tmp/z; ln -s /tmp/z ~/z1; mv ~/z1 /tmp/z where "~" and "/tmp" are not on the same filesystem, causes the link to be removed instead of moved. (2) $ rm /tmp/z; ln -s /tmp/z ~/z1; mv ~/z1 /tmp/z causes the link to be moved, but then mv(1) emits a bogus error message saying that the rename to do the move failed. mv(2) also has various bugs for hard links. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message