Date: Mon, 9 Jun 2014 09:37:21 +0100 From: krad <kraduk@gmail.com> To: Tom Evans <tevans.uk@googlemail.com> Cc: "Andrey V. Elsukov" <bu7cher@yandex.ru>, freebsd-stable <freebsd-stable@freebsd.org>, Aristedes Maniatis <ari@ish.com.au> Subject: Re: ZFS boot pool selection Message-ID: <CALfReyfX-zH0uZJaL6eCW8u_V8koB8JtByeoCisOBVp3Xkw15w@mail.gmail.com> In-Reply-To: <CAFHbX1KT041fhdp77POdwgrb4iDRBoqCWZbML-7UhiToTc9bTg@mail.gmail.com> References: <53902B1D.8030200@ish.com.au> <53909B22.7000801@yandex.ru> <53912346.7010207@ish.com.au> <CAFHbX1KT041fhdp77POdwgrb4iDRBoqCWZbML-7UhiToTc9bTg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I thought the bootfs variable told the bootcode where to get the kernel, and loader environment from. Unless otherwise stated in the loader.conf/fstab, this would also be where the kernel mounted the rootfs from. A subtle but important difference. On 6 June 2014 10:26, Tom Evans <tevans.uk@googlemail.com> wrote: > On Fri, Jun 6, 2014 at 3:11 AM, Aristedes Maniatis <ari@ish.com.au> wrote: > > Should vfs.root.mountfrom and bootfs be removed from the latest ZFS > howto instructions? > > Definitely not either. I use manageBE (another beadm-a-like tool) to > manage my root pool, the bootfs property is what determines which root > is used, and vfs.root.mountfrom is what I would put in the loader to > boot from a different one. > > Cheers > > Tom > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALfReyfX-zH0uZJaL6eCW8u_V8koB8JtByeoCisOBVp3Xkw15w>