From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 27 04:53:06 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 85274870 for ; Wed, 27 Nov 2013 04:53:06 +0000 (UTC) Received: from mail-pd0-f176.google.com (mail-pd0-f176.google.com [209.85.192.176]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5C5BE2692 for ; Wed, 27 Nov 2013 04:53:06 +0000 (UTC) Received: by mail-pd0-f176.google.com with SMTP id w10so9102704pde.21 for ; Tue, 26 Nov 2013 20:53:00 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=efO9Dv/PMGv4GfFc8cHpazbjF2PcZDFUjog4TpmvhA4=; b=RAhGsgCbsMRMl1lRjdhg5Rjxz/BdFTbFxsS3aW8RUkbo5LHP9A9pHVRcrCCz6CV6t0 g4gr6NHr3jaDJiwf3jsMu9GbnaV0Hc991Nd6c6PcmKr68dXYcmZafJ2dWei2eOy8+z5G AB5+CoNql7UnAiGodzDakMAza8Fl+DCCCOFc9Zh/xgoQ16mQxINRJLgtPD0ZdXn5U1db fD4Vk7Sgqf/grdSNAC+CXrXJgFcqb6+sBGxbWMzdHzI9/9FIINBw0H+y1Qdl9xOTaePQ KBkhJXcTkSMTM6jCdUPjPOI9MeTK2su90Umn+gd46+0/hWKG6oYFP7pElq25YqO999nu sd6w== X-Gm-Message-State: ALoCoQkntsnXINp9uIoR/4vZzTu0Cw7VLO+hXPcKdmVKqBnJNZARgrrCgar5IjTxhhWM5F1uTaO4 X-Received: by 10.67.23.71 with SMTP id hy7mr38761817pad.99.1385527980809; Tue, 26 Nov 2013 20:53:00 -0800 (PST) Received: from [192.168.2.123] (99-74-169-43.lightspeed.sntcca.sbcglobal.net. [99.74.169.43]) by mx.google.com with ESMTPSA id oj6sm95985076pab.9.2013.11.26.20.52.59 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 26 Nov 2013 20:52:59 -0800 (PST) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\)) Subject: Re: O_XATTR support in FreeBSD? From: Tim Kientzle In-Reply-To: Date: Tue, 26 Nov 2013 20:52:44 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <706707CA-BD52-4814-BCCE-EB044B062BA6@kientzle.com> References: <718836647.19911209.1385302696963.JavaMail.root@uoguelph.ca> To: Cedric Blancher X-Mailer: Apple Mail (2.1822) Cc: Freebsd hackers list , Richard Yao , Rick Macklem , Pedro Giffuni , Jordan Hubbard X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Nov 2013 04:53:06 -0000 On Nov 26, 2013, at 1:51 AM, Cedric Blancher = wrote: > 5. Support for tar and pax is already there. Its described in > Solaris's fsattr man page, they use a extended header with filename > /dev/null (to prevent older tar versions from tripping over the new > headers) and then have a named attribute header which describes the > attributes names and flags. There are quite a few alternative approaches for storing extended attributes in tar and pax files. I=92ve documented several at: https://github.com/libarchive/libarchive/wiki/TarExtendedAttributes If you have documentation for variations that aren=92t explained there, please let me know. Small sample tar or pax files that can be evaluated are greatly appreciated. Cheers, Tim