From owner-freebsd-stable@freebsd.org  Mon Oct 17 04:38:38 2016
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 A40E7C0D487;
 Mon, 17 Oct 2016 04:38:38 +0000 (UTC)
 (envelope-from FreeBSD@shaneware.biz)
Received: from ipmail06.adl6.internode.on.net (ipmail06.adl6.internode.on.net
 [150.101.137.145])
 by mx1.freebsd.org (Postfix) with ESMTP id 15A321C01;
 Mon, 17 Oct 2016 04:38:37 +0000 (UTC)
 (envelope-from FreeBSD@shaneware.biz)
Received: from ppp121-45-99-127.bras2.adl6.internode.on.net (HELO
 leader.local) ([121.45.99.127])
 by ipmail06.adl6.internode.on.net with ESMTP; 17 Oct 2016 15:03:27 +1030
Subject: Re: help install new kernel on root-on-ZFS on 11-STABLE
To: Ben Woods <woodsb02@gmail.com>,
 "Brandon J. Wandersee" <brandon.wandersee@gmail.com>
References: <CAGBxaXkz7XxZqWUk7AOT7sPc0ZDCOHEYjxTRGBcrxn8ur3q=UQ@mail.gmail.com>
 <864m4cszoa.fsf@WorkBox.Home>
 <CAOc73CDewzb_+0Ov69ncaEFFKb+r6+Rtu536sF70CcLYK6GfDQ@mail.gmail.com>
Cc: FreeBSD Stable List <freebsd-stable@freebsd.org>,
 Aryeh Friedman <aryeh.friedman@gmail.com>,
 FreeBSD Mailing List <freebsd-questions@freebsd.org>
From: Shane Ambler <FreeBSD@ShaneWare.Biz>
Message-ID: <8764c713-1204-b780-a80d-3e0e422797bf@ShaneWare.Biz>
Date: Mon, 17 Oct 2016 15:03:21 +1030
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101
 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <CAOc73CDewzb_+0Ov69ncaEFFKb+r6+Rtu536sF70CcLYK6GfDQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
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: Mon, 17 Oct 2016 04:38:38 -0000

On 17/10/2016 09:01, Ben Woods wrote:
> On Monday, 17 October 2016, Brandon J. Wandersee <
> brandon.wandersee@gmail.com> wrote:
>>
>> Last I checked, the automated installer created a separate pool called
>> "bootpool," with a symlink from /boot to /bootpool.
>>
>
> I believe this is the case if the option for full disk encryption is
> selected in the installer. This is required until the boot loader is
> capable of recognising and accessing a geli encrypted disk.

For a "plain" install, /boot is nothing more than a directory created in
the root filesystem that will get created during installation. This is
the same for UFS and ZFS. I haven't checked during a build but I don't
think anything gets installed into /boot before installkernel so you
shouldn't expect it to exist before installkernel.

As mentioned you can create a separate pool for /boot so you can load
the kernel from a non-encrypted filesystem that can then mount the
remaining encrypted filesystems.

Another alternative setup is using boot environments that would create
filesystems as /sys/ROOT/<boot env name> that are then mounted as the
root filesystem. Like a plain system the /boot folder would still be
created at the installkernel stage.


-- 
FreeBSD - the place to B...Storing Data

Shane Ambler