From owner-freebsd-current@FreeBSD.ORG  Fri May 21 11:05:39 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 7D4FA16A4CE
	for <current@freebsd.org>; Fri, 21 May 2004 11:05:39 -0700 (PDT)
Received: from users.altadena.net (users.altadena.net [207.151.161.11])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6391943D3F
	for <current@freebsd.org>; Fri, 21 May 2004 11:05:39 -0700 (PDT)
	(envelope-from pete@users.altadena.net)
Received: from pete by users.altadena.net with local (Exim 4.34)
	id 1BREOW-000KfI-V6
	for current@freebsd.org; Fri, 21 May 2004 11:05:20 -0700
Date: Fri, 21 May 2004 11:05:20 -0700
From: Pete Carah <pete@altadena.net>
To: current@freebsd.org
Message-ID: <20040521180520.GA79342@users.altadena.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
Sender: Pete Carah <pete@users.altadena.net>
Subject: Tar problem
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 May 2004 18:05:39 -0000

I don't know how new this is but it didn't occur the last time I tried
to unpack the ports collection (probably a year ago).   I haven't got
room on my usr disk for ports, so I symlink it off to a bulk disk 
(hardware, not nfs).  When I unpack the ports collection, the symlink 
has been overwritten with the real directory (in this case it'll barely 
fit, but no builds work inside it...).

I see that the default tar on this system is still gtar - I don't remember
this behavior from the last time I tried the same thing.

I only mention this because it is a real bother, and I've seen talk about
changing versions of tar...  Does the new version do the same?  and/or
is there an option whose default changed (like --posix?).  If this is posix
behavior then I see it as yet another gratuitous change that posix made
just to bother old users (there are LOTS of those; the arg changes to
sort, for another example).

-- Pete