From owner-freebsd-current@FreeBSD.ORG Sat Aug 21 22:15:27 2004 Return-Path: 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 13B3D16A4CE; Sat, 21 Aug 2004 22:15:27 +0000 (GMT) Received: from ylpvm15.prodigy.net (ylpvm15-ext.prodigy.net [207.115.57.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id C09CA43D2D; Sat, 21 Aug 2004 22:15:26 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (adsl-67-115-74-195.dsl.lsan03.pacbell.net [67.115.74.195]) i7LMFSEU017812; Sat, 21 Aug 2004 18:15:29 -0400 Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 39B9F53631; Sat, 21 Aug 2004 15:15:18 -0700 (PDT) Date: Sat, 21 Aug 2004 15:15:18 -0700 From: Kris Kennaway To: Tim Kientzle Message-ID: <20040821221518.GA80603@xor.obsecurity.org> References: <4127890E.5040809@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="VbJkn9YxBvnuCH5J" Content-Disposition: inline In-Reply-To: <4127890E.5040809@freebsd.org> User-Agent: Mutt/1.4.2.1i cc: Michiel Boland cc: current@freebsd.org Subject: Re: sysinstall creates PaxHeader directories X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Sat, 21 Aug 2004 22:15:27 -0000 --VbJkn9YxBvnuCH5J Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Aug 21, 2004 at 10:40:30AM -0700, Tim Kientzle wrote: > Michiel Boland wrote: > >Hi. Last week I did a rebuild from scratch by doing a make release and= =20 > >using the resulting cdrom. I notice that sysinstall creates several=20 > >directories called 'PaxHeader'. This is probably because cpio does not= =20 > >understand the bsdtar format? >=20 > The current FreeBSD cpio, pax, and gtar commands do > not understand the POSIX.1-2001 extensions being > used by bsdtar. (star, gtar 1.14, and many newer "pax" > implementations do support them, however.) These extensions > were designed so that older programs would extract the > extended attributes as regular files. Clearly, that design > is succeeding. ;-) >=20 > It might be reasonable for "make release" to specify > --format=3Dustar to suppress those extensions, or for > sysinstall to use libarchive rather than cpio so > it can take advantage of them. Neither option seems > likely before 5.3, of course. >=20 > Could you please send me the output of the following: > find / | grep 'PaxHeader' > so I can see exactly what files are triggering the > extensions? >=20 > If there aren't too many, the result of > find / | grep 'PaxHeader' | tar -cvz -I - -f attributes.tgz > would also be interesting. FYI, I'm seeing this in package builds too, when running ssh client bsdtar c | gtar x (to work around the permission problem). Kris --VbJkn9YxBvnuCH5J Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (FreeBSD) iD8DBQFBJ8l2Wry0BWjoQKURApsmAKDs3zaEdrLQcKOI00nSiodP0ExSIQCgz9D1 55UjyA8m/77PFobukbz9W84= =F8Vz -----END PGP SIGNATURE----- --VbJkn9YxBvnuCH5J--