From owner-freebsd-current@FreeBSD.ORG Wed Oct 23 16:12:27 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C2383270 for ; Wed, 23 Oct 2013 16:12:27 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 947402A59 for ; Wed, 23 Oct 2013 16:12:27 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 3686741422 for ; Wed, 23 Oct 2013 16:12:25 +0000 (UTC) Message-ID: <5267F56A.5060800@allanjude.com> Date: Wed, 23 Oct 2013 12:12:26 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: 10.0-BETA1 ZFS install -- /var/empty read-only References: <5267CE4B.8050602@vangyzen.net> <5267D145.9070502@vangyzen.net> In-Reply-To: <5267D145.9070502@vangyzen.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Oct 2013 16:12:27 -0000 On 2013-10-23 09:38, Eric van Gyzen wrote: > On 10/23/2013 08:30, Kimmo Paasiala wrote: >> On Wed, Oct 23, 2013 at 4:29 PM, Kimmo Paasiala wrote: >>> On Wed, Oct 23, 2013 at 4:25 PM, Eric van Gyzen wrote: >>>> I just installed 10.0-BETA1 using the [very cool] new automatic ZFS >>>> option. I noticed that /var/empty is not mounted read-only. I suspect >>>> it could be. I made it so, and sshd still seemed to work. >>>> >>>> Eric >>> I don't think there's a standard for how to break down the ZFS pool to >>> individual datasets. If the install made only a single dataset for >>> /var you would then effectively get a read-write /var/empty. The >> *The same applies* >> >>> applies if you install on UFS and don't assign a separate filesystem >>> for /var/empty like the default install does in fact. > There might not be a standard, but the installer does have a default > set, which includes a separate filesystem for /var/empty. I imagine > this was done specifically to make it read-only. Since that was not > done, it seems like an oversight. > > Eric > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" You have to be careful with marking the /var/empty read only, if you do it too soon the extract of base.txz fails. This might be a good use of Colin Percival's 'firstboot' script -- Allan Jude