From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1RVJZE-00077M-9U for mharc-grub-devel@gnu.org; Tue, 29 Nov 2011 04:01:32 -0500 Received: from eggs.gnu.org ([140.186.70.92]:41668) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RVJZ5-00070N-Ie for grub-devel@gnu.org; Tue, 29 Nov 2011 04:01:29 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RVJYx-0008AT-9I for grub-devel@gnu.org; Tue, 29 Nov 2011 04:01:23 -0500 Received: from mail-ey0-f169.google.com ([209.85.215.169]:34792) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RVJYx-0008AG-4i for grub-devel@gnu.org; Tue, 29 Nov 2011 04:01:15 -0500 Received: by eaah1 with SMTP id h1so3304225eaa.0 for ; Tue, 29 Nov 2011 01:01:14 -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=y9/ubZs6RKVPGPD32AkfOhHibSRP+tithXUFJ45KUJ0=; b=O398fOiXzlMUCyF8ihL9B8u38JLzZwARrSuslNsRq/lA8zLL45uewHLyulef9K7ynt VuAJWQ6qK/CW8K6YW6eioTHDzQbvvgWnvT1LuCcoq+neGV73MRP3n3Y6MRSr8Ui3xxcp amS3hAbjUruRmi5pPsS0owR2CETd+JErBwAEg= Received: by 10.227.208.13 with SMTP id ga13mr8921730wbb.4.1322557274170; Tue, 29 Nov 2011 01:01:14 -0800 (PST) Received: from debian.x201.phnet (1-234.197-178.cust.bluewin.ch. [178.197.234.1]) by mx.google.com with ESMTPS id z35sm15139350wbm.12.2011.11.29.01.01.05 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 29 Nov 2011 01:01:13 -0800 (PST) Message-ID: <4ED49F36.50905@gmail.com> Date: Tue, 29 Nov 2011 10:00:38 +0100 From: =?UTF-8?B?VmxhZGltaXIgJ8+GLWNvZGVyL3BoY29kZXInIFNlcmJpbmVua28=?= User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111114 Icedove/3.1.16 MIME-Version: 1.0 To: The development of GNU GRUB Subject: Re: [PATCH, RFC, RFT] Mactel integration References: <4ED38BC0.6090100@gmail.com> <4ED409C8.1000307@gmail.com> <36DA8C1F-F042-48E9-A552-3B1C076306DA@oracle.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: GNU/Linux 2.6 (newer, 2) X-Received-From: 209.85.215.169 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: Tue, 29 Nov 2011 09:01:29 -0000 On 29.11.2011 08:25, Keshav P R wrote: > grubx64.efi is installed at /boot/efi/efi/grub2/grubx64.efi , but the > modules are located at /boot/grub (which is $grubdir aka prefix set in > grubx64.efi/core.efi). But this again creates confusion for some users > who have to find out the "actual" prefix dir in case he/she wants to > modify grub.cfg and grubenv in that dir. The only way to force > grub-install to install "everything" in /boot/efi/efi/grub/ is to us The modules and configuration files form platform-independent part as far as install is concerned (it's always handles the same way). The grub.efi is the EFI specific part which needs to go where EFI expects it. /efi directory on ESP as its name implies stores files for EFI, perhaps some small config files, it is not to store our bunch of modules. It's ok to use ESP to store modules unless they go into /efi directory but it's hard to say if such a long list of files will trigger any bugs in firmware implementation but in any case platform-independent part shouldn't go into firmware-specific directories. We've already had issues with IEEE1275 when we did something similar -- Regards Vladimir 'φ-coder/phcoder' Serbinenko