From owner-freebsd-current@FreeBSD.ORG  Mon Nov 15 01:29:53 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 737C316A4CE; Mon, 15 Nov 2004 01:29:53 +0000 (GMT)
Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net
	[66.166.149.50])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 1001443D1D; Mon, 15 Nov 2004 01:29:53 +0000 (GMT)
	(envelope-from kientzle@freebsd.org)
Received: from freebsd.org (p54.kientzle.com [66.166.149.54])
	by kientzle.com (8.12.9/8.12.9) with ESMTP id iAF1Tq90004972;
	Sun, 14 Nov 2004 17:29:52 -0800 (PST)
	(envelope-from kientzle@freebsd.org)
Message-ID: <41980690.5030405@freebsd.org>
Date: Sun, 14 Nov 2004 17:29:52 -0800
From: Tim Kientzle <kientzle@freebsd.org>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031006
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Joe Marcus Clarke <marcus@freebsd.org>
References: <4193C9E5.2090004@FreeBSD.org>
In-Reply-To: <4193C9E5.2090004@FreeBSD.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: current@freebsd.org
Subject: Re: BSD tar cannot archive files with setuid bit on -CURRENT
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: Mon, 15 Nov 2004 01:29:53 -0000

Joe Marcus Clarke wrote:
> 
> After upgrading to 6-CURRENT from November 10, I found bsdtar cannot
> archive files with setuid bits anymore.
....
> 
> This problem can be reproduced by:
> 
> # cd /tmp
> # tar cvf xxx.tar /bin/rcp

This is now fixed.  (The problem was actually
with the schg flag, not the setuid bit.  Forcing
ustar format with --format=ustar is a workaround.)

Thanks for the report,

Tim