Date: Thu, 4 Jul 2013 22:18:43 +0400 (MSK) From: Dmitry Morozovsky <marck@rinet.ru> To: Andriy Gapon <avg@freebsd.org> Cc: freebsd-fs@freebsd.org, Volodymyr Kostyrko <c.kworr@gmail.com> Subject: Re: boot from ZFS: which pool types use? Message-ID: <alpine.BSF.2.00.1307042216510.2446@woozle.rinet.ru> In-Reply-To: <alpine.BSF.2.00.1307042208370.2446@woozle.rinet.ru> References: <alpine.BSF.2.00.1307041424030.2446@woozle.rinet.ru> <51D56066.1020902@FreeBSD.org> <alpine.BSF.2.00.1307041552031.2446@woozle.rinet.ru> <51D577A9.1030304@gmail.com> <alpine.BSF.2.00.1307041952030.2446@woozle.rinet.ru> <51D59AAD.3030208@FreeBSD.org> <alpine.BSF.2.00.1307042000130.2446@woozle.rinet.ru> <51D5A20F.4070103@FreeBSD.org> <alpine.BSF.2.00.1307042208370.2446@woozle.rinet.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 4 Jul 2013, Dmitry Morozovsky wrote: > Now, looking at zfsboot.c, couldn't we (for finding /boot/zfsloader suitable > for us) loop over, say, top-level datasets in pools we have, in abcense of > special property? As for me, this should plug the most annoying mistakes... And followup: for ufs/fdisk, one could easily drop in the boot process and switch to other disk, slice, partitiona and even loader. Not that it's (at least easily) achievable with zfsloader... And, not, unfortunately, I have no patches to apply.... -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1307042216510.2446>