From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1S1pDW-0004bC-SR for mharc-grub-devel@gnu.org; Sun, 26 Feb 2012 20:17:30 -0500 Received: from eggs.gnu.org ([208.118.235.92]:46093) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S1pDT-0004b5-QB for grub-devel@gnu.org; Sun, 26 Feb 2012 20:17:28 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S1pDS-0002If-DH for grub-devel@gnu.org; Sun, 26 Feb 2012 20:17:27 -0500 Received: from mail-ey0-f169.google.com ([209.85.215.169]:51056) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S1ous-0007Sy-MD for grub-devel@gnu.org; Sun, 26 Feb 2012 19:58:14 -0500 Received: by eaag11 with SMTP id g11so1858077eaa.0 for ; Sun, 26 Feb 2012 16:58:11 -0800 (PST) Received-SPF: pass (google.com: domain of phcoder@gmail.com designates 10.14.99.195 as permitted sender) client-ip=10.14.99.195; Authentication-Results: mr.google.com; spf=pass (google.com: domain of phcoder@gmail.com designates 10.14.99.195 as permitted sender) smtp.mail=phcoder@gmail.com; dkim=pass header.i=phcoder@gmail.com Received: from mr.google.com ([10.14.99.195]) by 10.14.99.195 with SMTP id x43mr6882940eef.46.1330304291544 (num_hops = 1); Sun, 26 Feb 2012 16:58:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=p3A81pWWVJE6Mk5i6zw3E3rbku6/NWmq0S/d07dWqB4=; b=JSBlulJifIBYcLNBzDTIALlPLKxpxf+jcACTLrUxE2gNb8Nr364+XYHSS7o+/Xc/GS w0RB1cCQzG9d71ryLk61l+AU7oGLAi2PYqx3IIPCEoSD0jc9F9kllfs2lts2KYfNOw7J eFLgKtG8DHksCEm7/0+OdkvmDpeiop1/lrjaM= Received: by 10.14.99.195 with SMTP id x43mr5123239eef.46.1330304291417; Sun, 26 Feb 2012 16:58:11 -0800 (PST) Received: from debian.x201.phnet (51-234.197-178.cust.bluewin.ch. [178.197.234.51]) by mx.google.com with ESMTPS id w60sm51619698eeb.4.2012.02.26.16.58.08 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 26 Feb 2012 16:58:09 -0800 (PST) Message-ID: <4F4AD51E.3070104@gmail.com> Date: Mon, 27 Feb 2012 01:58:06 +0100 From: =?UTF-8?B?VmxhZGltaXIgJ8+GLWNvZGVyL3BoY29kZXInIFNlcmJpbmVua28=?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20120216 Icedove/8.0 MIME-Version: 1.0 To: The development of GNU GRUB Subject: Re: [PATCH] grub + FreeBSD's loader(8) + ZFS root References: <4BBC5E39.7070007@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 209.85.215.169 Cc: Navdeep Parhar X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2012 01:17:29 -0000 On 07.04.2010 22:21, Navdeep Parhar wrote: > 2010/4/7 Vladimir 'φ-coder/phcoder' Serbinenko: >> Navdeep Parhar wrote: >>> Hello grub-devel, >>> >>> Right now it's not possible to boot using FreeBSD's loader(8) from a ZFS >>> root filesystem. Grub doesn't indicate to the loader that there is a >>> ZFS root involved and consequently the loader fails to find the kernel. >>> The attached patch fixes this. It does not affect those that boot the >>> kernel directly. This is only for users that want to boot using >>> FreeBSD's loader. >>> >>> Why would you want to? IMHO it is much simpler to boot indirectly using >>> the loader because in that case grub does not have to deal with >>> device.hints, kernel modules, kFreeBSD.xxx style variables, >>> /boot/zfs/zpool.cache, etc. As a FreeBSD user, I'm used to putting this >>> information in the "normal" config files (/boot/loader.conf, device.hints, >>> etc.) and not in a grub.cfg file. Grub only needs to know where the loader >>> is, nothing else: >>> >>> menuentry "FreeBSD 8" { >>> search -s -l fbsd8 >>> kfreebsd -D /@/boot/zfsloader >>> } >>> (fbsd8 is the name of the ZFS root pool) >>> >>> >> Eternal chainloading isn't the way to go. It limits grub usefullness and >> scope and is to be used only when no alternative exists. In this case >> the right direction would be to make a small C module to parse boot(8) >> config or a shell script for 30_osprober.in to do the same job > Sure, chainloading doesn't have to be the preferred way of booting an > OS, but it shouldn't fail without a good reason either. Right now > FreeBSD can be chainloaded from a UFS root but not from ZFS root. > That's all that I'm trying to fix here. This patch doesn't imply that > chainloading is *the* way to load FreeBSD - just that it is a usable > alternate to direct loading, even from a ZFS root. I've added this patch but only because since we support aout /boot/loader it makes little sense not to support zfsloader but it's not a recommended way to boot in either case. > Regards, > Navdeep > > > _______________________________________________ > Grub-devel mailing list > Grub-devel@gnu.org > http://lists.gnu.org/mailman/listinfo/grub-devel > -- Regards Vladimir 'φ-coder/phcoder' Serbinenko