From owner-freebsd-stable@freebsd.org  Sun Sep 24 09:50:20 2017
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@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 EF1E7E24120
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Sun, 24 Sep 2017 09:50:20 +0000 (UTC)
 (envelope-from smithi@nimnet.asn.au)
Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 57C3070425;
 Sun, 24 Sep 2017 09:50:19 +0000 (UTC)
 (envelope-from smithi@nimnet.asn.au)
Received: from localhost (localhost [127.0.0.1])
 by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id v8O9kJDG030527;
 Sun, 24 Sep 2017 19:46:19 +1000 (EST)
 (envelope-from smithi@nimnet.asn.au)
Date: Sun, 24 Sep 2017 19:46:19 +1000 (EST)
From: Ian Smith <smithi@nimnet.asn.au>
To: Marius Strobl <marius@freebsd.org>
cc: freebsd-stable@freebsd.org,
 FreeBSD Release Engineering Team <re@freebsd.org>
Subject: Re: FreeBSD 10.4-RC2 Now Available
In-Reply-To: <20170923175450.GX20729@alchemy.franken.de>
Message-ID: <20170924193857.D35468@sola.nimnet.asn.au>
References: <20170923175450.GX20729@alchemy.franken.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Sep 2017 09:50:21 -0000

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?

2) Are we any closer to gettng a larger memstick.img with dvd1 contents?

cheers, Ian