[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freebsd-fs
Subject:    Re: Current gptzfsboot limitations
From:       Matt Reimer <mattjreimer () gmail ! com>
Date:       2009-11-25 0:28:05
Message-ID: f383264b0911241628w42b39b06od6e12d95edf2fa3d () mail ! gmail ! com
[Download RAW message or body]

On Tue, Nov 24, 2009 at 3:50 AM, James R. Van Artsdalen
<james-freebsd-fs2@jrv.org> wrote:
> I assume that *zfsboot requires that /boot and /boot/kernel be in the
> boot filesystem and not filesystems of their own.
>
> A man page probably ought to say this or someone will be tempted to "zfs
> create pool/boot/kernel" so they can roll back undesirable kernel installs.

gptzfsboot (and I'm pretty sure zfsboot too) uses the first pool it
finds. It opens the pool, gets the 'bootfs' property (i.e. the one set
with "zpool set bootfs=tank/ROOT tank") and retrieves loader(8) from
that filesystem. You can boot from any filesystem in the pool.

Matt
_______________________________________________
freebsd-fs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"
[prev in list] [next in list] [prev in thread] [next in thread]