Date: Sun, 24 Sep 2017 17:30:10 +0200 From: Marius Strobl <marius@FreeBSD.org> To: Ian Smith <smithi@nimnet.asn.au> Cc: freebsd-stable@freebsd.org, FreeBSD Release Engineering Team <re@freebsd.org> Subject: Re: FreeBSD 10.4-RC2 Now Available Message-ID: <20170924153010.GY20729@alchemy.franken.de> In-Reply-To: <20170924193857.D35468@sola.nimnet.asn.au> References: <20170923175450.GX20729@alchemy.franken.de> <20170924193857.D35468@sola.nimnet.asn.au>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Sun, Sep 24, 2017 at 07:46:19PM +1000, Ian Smith wrote: > On Sat, 23 Sep 2017 19:54:50 +0200, Marius Strobl wrote: > > > o Given that the amd64 disc1 image was overflowing, more of the base > > components installed into the disc1 (live) file systems had to be > > disabled. Most notably, this removed the compiler toolchain from > > the disc1 images. All disabled tools are still available with the > > dvd1 images, though. > > 1) Does that also apply to the components installed on the memstick.img? Yes, given that the disc1 file systems are also used to create the memstick images. > 2) Are we any closer to gettng a larger memstick.img with dvd1 contents? No, given that we'd likely want to have a variant of the memstick images which include all base tools also for snapshots. However, so far the dvd1 images are only created for releases and around the notion to contain packages, i. e. it's not as simple as creating additional memstick images from the dvd1 file system. Also, given that with head the amd64 disc1 image is overflowing despite all of the stripping, the way to go for 12.0 likely is to drop the historical limits on images sizes along with the disc1 images and instead provide DVD images with all base tools and for releases, additional DVD images with packages on top. Similar for memstick images. All of this probably boils down to adding options to both makefs(8) and mkimg(1) for simply excluding the packages directory (as for makefs(8), simpler than via an mtree(8) file) first, so we neither need to employ hacks in the release scripts nor build yet another file system set. Marius -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJZx89+XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ1M0Q5QjQzNTVGOTU5ODBGQzVENzZCMDIy MEI3MERFMTNGMUQxRTRGAAoJECC3DeE/HR5PrNwQAI7hNUN3IZRFcV3fzAl88GKP B6FmZKSWogxTwqLJCQgglJXoUkid5FfzMGH9qDjEE1g6W0sN4Q5aysv5+5s+WPWU Xfhl5ivm070dYDBaqbR0cxCaK7cbIScf14dbpxE6hNUYHV5hnQZp8kT+vvvWYIQz TZlHGiK1dccYH5WOg/UgR7nvs6piXI5XzmvP7o1mWv2TdT0DwaNXjuHznwZnAdW7 rStMPpvlC99a6+iAU74cbcBQi9w6Uuro+7V+DXZSwQRdP0PQsx1zOxkwAeY5+BKz PFK7w0SC5GB1ym7ddQSyY3+8bQOEelwOX99yqU9SCqPnqyMOl+l+CAv8gCenyoBl BgU4fTAAtsxNgne065/cGA+EEMDZtI2mdleGV8xXQGUFu2Dp8+HOhKBID95SW7LJ +WDAKUvbkQvw5URjFZ3TtsbqZQptGji/Xze8i6nJ1dv0aU2ajU3sjR/N5yy+wg9i KUK7K53Wx0TKVUkd4oUDePEUSjnRzalO8BPk4oLi08EvmX/yBMVswdaV4GIhCy5+ hSzud+98xmq3eDhoRsLqE2eRUbP9BegbM7VappEqFRE1I0mLQG9A/8DR49aZhzA2 TFg+rnYhjjW3gW3GtgZteHeRYIlk9ADsTxvbz2CEL2JpuUIFeb6g2OPPXeqTXZQZ hQPI71i7MhhJXRg+sQdM =nrnb -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170924153010.GY20729>