From owner-freebsd-fs@FreeBSD.ORG Mon Nov 19 20:53:09 2012 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A6F9D4F9 for ; Mon, 19 Nov 2012 20:53:09 +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 EB72D8FC12 for ; Mon, 19 Nov 2012 20:53:08 +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 WAA17230; Mon, 19 Nov 2012 22:52:50 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1TaYKo-000Cwo-0s; Mon, 19 Nov 2012 22:52:50 +0200 Message-ID: <50AA9C20.1090004@FreeBSD.org> Date: Mon, 19 Nov 2012 22:52:48 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121030 Thunderbird/16.0.2 MIME-Version: 1.0 To: vermaden Subject: Re: Why do we need vfs.root.mountfrom for zfs References: <848051353247434@web29h.yandex.ru> <50A934D2.9010205@FreeBSD.org> <1026501353267511@web27h.yandex.ru> <50A93A6E.1090907@FreeBSD.org> <50A96AE2.60803@shatow.net> <50AA2AE5.5080002@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, Bryan Drewery 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: Mon, 19 Nov 2012 20:53:09 -0000 on 19/11/2012 21:25 vermaden said the following: > the beadm already checks if its being run on FreeBSD 8.0 or later, but > that can be inappropriate if the needed bits would be MFC to stable/7 > and then put into the 7.5-RELEASE (is there any chance? for that). I don't expect that there ever will be 7.5 and I am not MFC-ing anything to stable/7 now, because it is a "legacy" branch. > So please decide if You want beadm to support the stable/7 branch. Not up to me to decide... > Yesterday I got that piece of information ,that vfs.root.mountfrom is > not needed now. Can I assume that using vfs.root.mountfrom is > harmless then? For ZFS booting vfs.root.mountfrom now has a reasonable default value, that's all. You can still use vfs.root.mountfrom or fstab, but in most cases it's just potentially more confusing than the default (bootfs). > I ask because if we remove that from beadm, then anything from > 2012.06 and later will just work and everything before won't. As beadm > already checks if its being used on FreeBSD 8.0 or later, removing the > setting of vfs.root.mountfrom from beadm would probably make it > 9.1+ exclusive only (along with 9.0-STABLE from 2012.06 or later of > course). > > The needed bits will probably find its way into the stable/8, but as > 8.3-RELEASE was released 2012.04, then the 8.4-RELEASE with needed > bits would be probably available in late 2013, it would not be nice > for 8.x users to force them to upgrade to 9.x series when its still > possible to use beadm on 8.x (even in its limited form - without > the boot menu BE selection). I believe that 8.4 release process will start as soon as 9.1 is out of the door (that's a very uncertain date, I know) and hopefully it will take not more than a few weeks. So I'd hope for early 2013 or perhaps even late 2012. But definitely not late 2013. > Another solution may be checking the commit version (r243107) > for needed features and then set (or not) the vfs.root.mountfrom > option. > > I would like to hear your comments on these thoughts/solutions. Potentially you could just for a branch+revision combination (or __FreeBSD_version). But you can just keep using vfs.root.mountfrom. BTW, please note that it is the version of loader that is important here. -- Andriy Gapon