Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 04 Jul 2013 19:25:51 +0300
From:      Andriy Gapon <avg@FreeBSD.org>
To:        Dmitry Morozovsky <marck@rinet.ru>
Cc:        freebsd-fs@FreeBSD.org, Volodymyr Kostyrko <c.kworr@gmail.com>
Subject:   Re: boot from ZFS: which pool types use?
Message-ID:  <51D5A20F.4070103@FreeBSD.org>
In-Reply-To: <alpine.BSF.2.00.1307042000130.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>

next in thread | previous in thread | raw e-mail | index | archive | help
on 04/07/2013 19:04 Dmitry Morozovsky said the following:
> However: setting this in boot.loader (or manually in loader prompt) is not 
> enough to have bootable system
> 
> And this, I suppose, could be attacked to reduce possibility of 
> user-configuration errors: not having a possibility to point at loader is a bit 
> disappointing, you see ;) 

I am confused with this's and that's and unknown file names.
What exactly did you try and what exactly did not work?

Please note that vfs.root.mountfrom tells loader to tell kernel from where it
should mount root fs.  It can not tell earlier boot blocks where to find loader
itself.

-- 
Andriy Gapon



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51D5A20F.4070103>