From owner-freebsd-arch@freebsd.org Fri Aug 19 21:38:16 2016 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 2FF88BC0A3E for ; Fri, 19 Aug 2016 21:38:16 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E20B9130C for ; Fri, 19 Aug 2016 21:38:15 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x235.google.com with SMTP id m101so60723828ioi.2 for ; Fri, 19 Aug 2016 14:38:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=7JMfurbqXV2kMLhgYovTDMoESYsVpSnxnqK/xMXgUjg=; b=KokQyHACQVicAcw0K5YdR4jCk156kQjy305/53fh71qOdTw0K3adN+FA8fVTNl3kfS le1+ZhOqEusFlH23cOskiG1tm48GO7IP8cm9D2WWqj0GEhva0g8fWQ9nUi6ia6a8EcaV Eie1FucXa06VWfcorKUSiC21Gk1N9Agl9HjsNgNEE3bhobxqEg945kN+IgK19kfKsNGq gjwJBnhbvtnNYfjw/Zh8ZUIzxgcNzJRu5k60k6uEYE4Q3yUUA3soUA6NXutIVSB+nkHM 09T6o95vb2xSSar1TyWJnpOv2GZ1+Hh1VRf73N/1uXUTlIA4j4JBsU97OfW74GWJk+QQ 7Tdg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=7JMfurbqXV2kMLhgYovTDMoESYsVpSnxnqK/xMXgUjg=; b=gAk6WrR/3NI7s5TosqeFm2yFsoFrZknepwnjAqqMP5PK11UMaPTePxgYuYbnM/1cQq eQsT0Fy2CJzjWjhheIphz5YtkfY+cZRVU3/5WOyVMfxqr+LFbyfQ2J6JvB3dzGh00UTi 6WXbzP4Lbx1ysmib4DGkX8wuo7j+CIxR1NHvSb04ACut3TSk2LGMhoLC5GT8CjQP0Pa8 FAED61DsM366f4ynQb/WaTd9cOwagsCUcJIYTsLNO0PAEMk23WPFy6d/C4filDIoUZe2 fFsHAftESTNnM+Hr2wM11gK5ZYVbVUCsIbTNVahc3a2THDApxbbp73ZcP5EDpgPZaVFl JlXg== X-Gm-Message-State: AEkoouv80zyJieD8KBRsO+1FlCKqvFCVn9WDhEKRCLNwpM/xSaTDh2024kGnwZ3fWN5Ou+NWaYYQNVN6MSABlw== X-Received: by 10.107.21.134 with SMTP id 128mr11664007iov.59.1471642695110; Fri, 19 Aug 2016 14:38:15 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.36.65.7 with HTTP; Fri, 19 Aug 2016 14:38:14 -0700 (PDT) X-Originating-IP: [50.253.99.174] In-Reply-To: References: <78463d96-4dc3-b9a1-4793-05d6c6a76537@freebsd.org> <8b012527-e76c-060d-be5b-547deca5cb07@FreeBSD.org> <01069203-3566-12f7-993b-10e8e43be1ac@freebsd.org> <0dbec794-9dc2-4e72-6114-1e4b0968dae5@FreeBSD.org> <60a8da58-dbd5-dd26-6047-745bcf6a21f4@freebsd.org> <894b4841-166c-422f-9fe8-50ed261d76bb@FreeBSD.org> <1836ae28-b510-06dd-b83f-d08060cf87ac@freebsd.org> <8478b8aa-b8cf-7383-9923-249fced3dac3@FreeBSD.org> <4c28236a-f9ca-4601-336f-0829842b6d1a@freebsd.org> <270be6c4-16f9-3b89-c3b3-5983ec85834f@FreeBSD.org> <68cb112b-9334-045a-d860-7011573a2b47@freebsd.org> From: Warner Losh Date: Fri, 19 Aug 2016 15:38:14 -0600 X-Google-Sender-Auth: 6oFlk3-WoFyRnYoBKp6qdmezGQw Message-ID: Subject: Re: metalog -> makefs is broken again in -HEAD To: Adrian Chadd Cc: Sean Bruno , "freebsd-arch@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Aug 2016 21:38:16 -0000 On Fri, Aug 19, 2016 at 3:27 PM, Adrian Chadd wrote: > hi, > > ok, so here's the hilarity. > > We don't really have tools for consistently manipulating > metalog/manifest files. So, in order to do things like > add/delete/modify things in the manifest file, we need to do some .. > hackery. > > So that's what filter.pl does. It takes in the metalog file and does a > replace or append. It currently doesn't have a "delete" method. > > the .tmp file is "the extra files that we add /after/ the system > installs". Ie, it's the customisations done. It goes through filter.pl > and then the resultant metalog file has the complete thing that's > going into the image. > > When I get around to adding package support for mips (not mips_ap) > then it'll also have a second intermediary metalog file that has the > combination of all of the package installs, so makefs knows what to > do. > > Ok, so for metalog versus manifest. I remember doing it one way and > then brooks saying "Don't do that, here's the bugs". I'll have to go > over that and see. NanoBSD will eventually follow suit as well. I really want to be able to create entire images, including installing packages, as a normal user. Making sure all this works is on that path. I have similar scripts to Adrian's filter script as well for manipulating mtree files (and makefs does take mtree files, it's just picky about the exact form, sadly). Warner