From owner-freebsd-bugs  Mon Feb 12  8:15:44 2001
Delivered-To: freebsd-bugs@freebsd.org
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
	by hub.freebsd.org (Postfix) with ESMTP id BB45637B491
	for <freebsd-bugs@FreeBSD.ORG>; Mon, 12 Feb 2001 08:15:41 -0800 (PST)
Received: (from wollman@localhost)
	by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA18573;
	Mon, 12 Feb 2001 11:15:34 -0500 (EST)
	(envelope-from wollman)
Date: Mon, 12 Feb 2001 11:15:34 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <200102121615.LAA18573@khavrinen.lcs.mit.edu>
To: Bruce Evans <bde@zeta.org.au>
Cc: freebsd-bugs@FreeBSD.ORG
Subject: Re: bin/25013: mv(1) cannot move unresolvable symlinks across devices
In-Reply-To: <200102120520.f1C5K1d05869@freefall.freebsd.org>
References: <200102120520.f1C5K1d05869@freefall.freebsd.org>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

<<On Sun, 11 Feb 2001 21:20:01 -0800 (PST), Bruce Evans <bde@zeta.org.au> said:

>  I think that POSIX.2 and/or BSD made a mistake here, and mv should never
>  move across filesystems without being forced to.  

The POSIX rationale makes it clear that this was an intentional
choice.  The definition of `mv' says that it shall attempt rename()
first, but if this fails with [EXDEV], `mv' shall proceed by copying
the hierarchy.

-GAWollman




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message