From owner-freebsd-current@FreeBSD.ORG Thu Jan 16 22:09:21 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5DABB4D4; Thu, 16 Jan 2014 22:09:21 +0000 (UTC) Received: from mail-ea0-x231.google.com (mail-ea0-x231.google.com [IPv6:2a00:1450:4013:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BE2561E85; Thu, 16 Jan 2014 22:09:20 +0000 (UTC) Received: by mail-ea0-f177.google.com with SMTP id n15so1431463ead.8 for ; Thu, 16 Jan 2014 14:09:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=UcVaXzUfwAZHET3s7QWi+qGR0jwztBNkaALveG+Tq+w=; b=o4kLd30hT/Epo9vEdf9cNGeXb+y06FKwwuQRVNKkF6wKTjt8Gm0c4IyfsjtQzjT1xV IC/2E4wY1afE6z6wi2PP05VaUxVHq0zxGYvi87WgYI7DMWyza9sYVm86qHRzIKyU3c0I EG5PBOs8iQR5CKPWv75m2u9VY9JKJHP2T5161Oq5WeV2UdpansDbljz0d98ChHxQgFb8 eCF8r0f9AcUivJPq5Nk6XJjfWHY/+6+UAVBwmyuWmJXLHVM8lwh9k6IydXjOgrrUHv3C uHeAOKKm/jRmEPGBR72DdcOeKTkq6GiHcXtV7ireZbyY5efUUdE721T0MD+V7v8u26HB hgmQ== X-Received: by 10.15.24.72 with SMTP id i48mr14607588eeu.74.1389910159069; Thu, 16 Jan 2014 14:09:19 -0800 (PST) Received: from [192.168.1.101] (45.81.datacomsa.pl. [195.34.81.45]) by mx.google.com with ESMTPSA id z49sm8857601eeo.10.2014.01.16.14.09.18 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 16 Jan 2014 14:09:18 -0800 (PST) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Subject: Re: mtree acl support Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=windows-1250 From: =?iso-8859-2?Q?Edward_Tomasz_Napiera=B3a?= In-Reply-To: <1389904576.2313.71707745.52B4D2D1@webmail.messagingengine.com> Date: Thu, 16 Jan 2014 23:09:16 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <3607BA99-E4C9-4A0B-9BF1-7081DD79700B@FreeBSD.org> References: <1389710847.2685.70601137.72B5C024@webmail.messagingengine.com> <93FD368C-21D1-4A5F-986A-859D83AFB5BF@kientzle.com> <1389904576.2313.71707745.52B4D2D1@webmail.messagingengine.com> To: Mark Felder X-Mailer: Apple Mail (2.1283) Cc: FreeBSD current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 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: Thu, 16 Jan 2014 22:09:21 -0000 Wiadomo=9C=E6 napisana przez Mark Felder w dniu 16 sty 2014, o godz. = 21:36: > On Wed, Jan 15, 2014, at 23:11, Tim Kientzle wrote: >>=20 >> On Jan 14, 2014, at 6:47 AM, Mark Felder wrote: >>=20 >>> I was recently talking to someone about how one would backup / = restore >>> ACLs reliably. I didn't see any mention of ACLs in the mtree man = page >>> and after a quick google I came upon this old mailing list post: >>>=20 >>> = http://lists.freebsd.org/pipermail/freebsd-hackers/2008-April/024173.html >>>=20 >>> patch in list is here: = http://heka.cenkes.org/sat/diffs/mtree_acl.diff >>> I've mirrored it here: https://feld.me/freebsd/mtree_acl.diff >>>=20 >>> This old patch appears to still apply cleanly. I hate to see a patch = die >>> and be forgotten. >>=20 >> One problem that =91tar=92 has addressed (inspired by Joerg = Schilling=92s >> work on star) is to permit ACLs to be restored even if the user = database >> is out of date. >>=20 >> This is done by including a fourth field in each ACE with the >> numeric user ID. >>=20 >> I suspect you want to do the same for mtree. I thought >> I remembered acl_to_text having an option to use >> an extended text format, so it might be a trivial change. >>=20 >=20 > As long as it's not default. One of the most convenient ways to change = a > user's UID (or multiple users!) is to do an mtree backup, change > UID/GID, and then re-apply mtree backup. Every file that the user(s) > previously owned will be automatically changed to the new UID/GID for > you :-) I don't think the functionality above would interfere with that in any = way. The owner entries ("user:" for POSIX, "owner@" for NFSv4 ACLs) are = stored in a different way, and they never have the appended ID. (Besides, why not just "find ./ -user XXX -print0 | xargs -0 chown = YYY"?) --=20 If you cut off my head, what would I say? Me and my head, or me and my = body?