From owner-freebsd-arch@freebsd.org Sun Nov 29 18:16:11 2015 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 35CC1A223EE for ; Sun, 29 Nov 2015 18:16:11 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id F1E611A24 for ; Sun, 29 Nov 2015 18:16:10 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id D6ABB4F865; Sun, 29 Nov 2015 18:16:08 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTP id tATIG7bh044937; Sun, 29 Nov 2015 18:16:07 GMT (envelope-from phk@phk.freebsd.dk) To: Warner Losh cc: "freebsd-arch@freebsd.org" Subject: Re: mtree "language" enhancements In-reply-to: From: "Poul-Henning Kamp" References: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <44935.1448820967.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Sun, 29 Nov 2015 18:16:07 +0000 Message-ID: <44936.1448820967@critter.freebsd.dk> X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Nov 2015 18:16:11 -0000 -------- In message , Warner Losh writes: >As part of making NanoBSD buildable by non-root, I've found a need to hav= e >a richer mtree language than we currently have. >I'd like a new type called 'action' (so type=3Daction in the records). Th= is >type is defined loosely to manipulate and earlier entry (or maybe entries= , >still unsure) in the file. I suggest you define this so that all records have an action, and that the default action is "create" >2. "move" which relocates a previous entry. An additional targetpath >keyword specifies the ultimate destination for this entry. >3. "copy" which duplicates a previous entry. It too takes targetpath. Is targetpath absolute or relative ? Can it reach out of the mtree root ? >4. "meta" which changes the meta data of the previous entry. All keywords >on this are merged with the previous entry. System-III called this "chmog" if I recall correctly :-) >The one other thing that my merging tool does is to remove all size >keywords. That sounds wrong to me. Shouldn't you just emit "meta" records updating the size as appropriate ? What about digest fields ? -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= .