From owner-freebsd-current@FreeBSD.ORG Wed Oct 23 13:38:15 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B288878B for ; Wed, 23 Oct 2013 13:38:15 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from aussmtpmrkpc120.us.dell.com (aussmtpmrkpc120.us.dell.com [143.166.82.159]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 76FCF2FE6 for ; Wed, 23 Oct 2013 13:38:15 +0000 (UTC) X-Loopcount0: from 64.238.244.148 X-IronPort-AV: E=Sophos;i="4.93,554,1378875600"; d="scan'208";a="49587592" Message-ID: <5267D145.9070502@vangyzen.net> Date: Wed, 23 Oct 2013 08:38:13 -0500 From: Eric van Gyzen User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130702 Thunderbird/17.0.7 MIME-Version: 1.0 To: Kimmo Paasiala , FreeBSD current Subject: Re: 10.0-BETA1 ZFS install -- /var/empty read-only References: <5267CE4B.8050602@vangyzen.net> In-Reply-To: Content-Type: text/plain; charset="UTF-8" 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 13:38:15 -0000 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