From owner-freebsd-current@FreeBSD.ORG Tue Sep 27 18:00:24 2005 Return-Path: X-Original-To: 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 559A716A421 for ; Tue, 27 Sep 2005 18:00:24 +0000 (GMT) (envelope-from emaste@phaedrus.sandvine.ca) Received: from mailserver.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AEC443D53 for ; Tue, 27 Sep 2005 18:00:23 +0000 (GMT) (envelope-from emaste@phaedrus.sandvine.ca) Received: from labgw2.phaedrus.sandvine.com ([192.168.3.11]) by mailserver.sandvine.com with Microsoft SMTPSVC(5.0.2195.6713); Tue, 27 Sep 2005 14:00:18 -0400 Received: by labgw2.phaedrus.sandvine.com (Postfix, from userid 12627) id 7B2E313635; Tue, 27 Sep 2005 14:00:21 -0400 (EDT) Date: Tue, 27 Sep 2005 14:00:21 -0400 From: Ed Maste To: Garrett Wollman Message-ID: <20050927180021.GB9994@sandvine.com> References: <20050926195807.GD95971@sandvine.com> <17208.30606.117170.36398@khavrinen.csail.mit.edu> <20050927001650.GA9994@sandvine.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050927001650.GA9994@sandvine.com> User-Agent: Mutt/1.4.2.1i X-OriginalArrivalTime: 27 Sep 2005 18:00:18.0367 (UTC) FILETIME=[520324F0:01C5C38D] Cc: freebsd-current@FreeBSD.ORG Subject: Re: Bsdtar and archive torture tests X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Sep 2005 18:00:24 -0000 On Mon, Sep 26, 2005 at 08:16:50PM -0400, Ed Maste wrote: > Hmm, good point. I haven't set it to anything; locale(1) shows > that the LC_ variables are set to "C". So then I can see how this > happens, but it's still surprising (to me) behaviour. Ok, now I've definately encountered some non-obvious behaviour. A symlink target of 100 bytes or less keeps the same name, while a target of more than 100 bytes gets munged from the converstion to UTF-8 and back. For example, the symlink created by the following script doesn't change the link target: #!/bin/sh fname=$(printf $(jot -b \\303\\240 -s '' 50)) ln -fs $fname test tar -cf - test | tar -tvf - but if the 50 in the jot command is changed to 51, the target changes. So I guess that the link target doesn't fit in the standard header anymore, and needs an extended tag. Having different behaviour for the two cases does seem odd. -- Ed Maste, Sandvine Incorporated