On Thu, Jul 25, 2013 at 04:33:58PM +0100, Johannes Totz wrote: > On 24/07/2013 12:47, Andriy Gapon wrote: > >on 22/07/2013 23:38 Pawel Jakub Dawidek said the following: > >>On Mon, Jul 22, 2013 at 10:29:40AM +0300, Andriy Gapon wrote: > >>>I think that this setup (on ZFS level) is quite untypical, although not > >>>impossible on FreeBSD (and perhaps only FreeBSD). > >>>It's untypical because you have separate boot pool (where loader, loader.conf > >>>and kernel are taken from) and root pool (where "/" is mounted from). > >> > >>As I said elsewhere, it is pretty typical when full disk encryption is > >>used. > > > >I am judging by the number of reports / amount of feedback so far. > > I'm using a similar configuration too, where I have a USB stick with > unencrypted kernel and /boot bits which load a GELI keyfile (from > its own pool zboot), and then the rest of the system starts up from > the fully encrypted HDD (from another pool zsystem, so boot and > rootfs are on different pools). > > I'm not sure I understand the problem though. What exactly "broke" > after your commit? The pool that contains the bits that would > normally go to /boot is not imported automatically, but the rest is > working (ie. /boot symlink pointing to nowhere)? Or does booting > somehow fail? > "/boot" disappears and becomes a broken symlink. Glen
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:39 UTC