From owner-freebsd-fs@FreeBSD.ORG Thu Jul 4 16:26:53 2013 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 523E3D13 for ; Thu, 4 Jul 2013 16:26:53 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 9A3B11FC3 for ; Thu, 4 Jul 2013 16:26:52 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id TAA13227; Thu, 04 Jul 2013 19:26:27 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1UumMV-000Ez2-Gw; Thu, 04 Jul 2013 19:26:27 +0300 Message-ID: <51D5A20F.4070103@FreeBSD.org> Date: Thu, 04 Jul 2013 19:25:51 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130405 Thunderbird/17.0.5 MIME-Version: 1.0 To: Dmitry Morozovsky Subject: Re: boot from ZFS: which pool types use? References: <51D56066.1020902@FreeBSD.org> <51D577A9.1030304@gmail.com> <51D59AAD.3030208@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, Volodymyr Kostyrko X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jul 2013 16:26:53 -0000 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