Date: Fri, 19 Aug 2016 15:38:14 -0600 From: Warner Losh <imp@bsdimp.com> To: Adrian Chadd <adrian@freebsd.org> Cc: Sean Bruno <sbruno@freebsd.org>, "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org> Subject: Re: metalog -> makefs is broken again in -HEAD Message-ID: <CANCZdfprz6%2BNO4eUNQBADCJhtqDeuo2Zi8rYibCr6LvZoeyQwQ@mail.gmail.com> In-Reply-To: <CAJ-Vmo=1p4t8zEfBm9CUyc-A9tKY3mrt9-ZeoUQS%2BBmtKCYg=w@mail.gmail.com> References: <CAJ-VmoknWRf0bkfksp61pamKsLky_b=indGogS%2BJtFrFa%2BXaFw@mail.gmail.com> <78463d96-4dc3-b9a1-4793-05d6c6a76537@freebsd.org> <CAJ-Vmok1weKRsS4F_QWJP5-h%2BTBjAqQE2=PxSFStjh_VZqPF6w@mail.gmail.com> <b3a107fd-80d5-20aa-1f2b-ff60a75b8f94@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> <a0515f16-d40f-35b5-29bd-523924b4a8a3@freebsd.org> <68cb112b-9334-045a-d860-7011573a2b47@freebsd.org> <CAJ-Vmo=1p4t8zEfBm9CUyc-A9tKY3mrt9-ZeoUQS%2BBmtKCYg=w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Aug 19, 2016 at 3:27 PM, Adrian Chadd <adrian@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfprz6%2BNO4eUNQBADCJhtqDeuo2Zi8rYibCr6LvZoeyQwQ>