From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1RWN0F-0007c8-Fb for mharc-grub-devel@gnu.org; Fri, 02 Dec 2011 01:53:47 -0500 Received: from eggs.gnu.org ([140.186.70.92]:34425) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RWN0D-0007bC-12 for grub-devel@gnu.org; Fri, 02 Dec 2011 01:53:45 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RWN0B-0003zN-Mm for grub-devel@gnu.org; Fri, 02 Dec 2011 01:53:44 -0500 Received: from mail-ww0-f41.google.com ([74.125.82.41]:55885) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RWN0B-0003zF-GL for grub-devel@gnu.org; Fri, 02 Dec 2011 01:53:43 -0500 Received: by wgbdt12 with SMTP id dt12so444069wgb.0 for ; Thu, 01 Dec 2011 22:53:42 -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:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=u50Wnws4xmYzJTIuJVONioJT13qI8zVlcopQwZfD9Vg=; b=AUe0178kVTbMbGCx6XIyfP3noArCmoOJgCONAzCW3u6fYI3DoHpNzukGtdU2F5Pf8m mBAUdN7LvWrIsZXsw9g3tum2gE9JnZI98G+92lepvcGxg3wBX48vfDURZMXZY7xTudZm +Iu1cSyLqRTblFofDjbuYtCObg0oQ1qYPWiz0= Received: by 10.180.88.66 with SMTP id be2mr7537031wib.54.1322808822492; Thu, 01 Dec 2011 22:53:42 -0800 (PST) Received: from debian.x201.phnet (77-232.197-178.cust.bluewin.ch. [178.197.232.77]) by mx.google.com with ESMTPS id m5sm2385484wie.2.2011.12.01.22.53.40 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 01 Dec 2011 22:53:41 -0800 (PST) Message-ID: <4ED875F3.6080905@gmail.com> Date: Fri, 02 Dec 2011 07:53:39 +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> <4ED49F36.50905@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: GNU/Linux 2.6 (newer, 2) X-Received-From: 74.125.82.41 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: Fri, 02 Dec 2011 06:53:46 -0000 On 02.12.2011 07:22, Keshav P R wrote: > 2011/11/29 Vladimir 'φ-coder/phcoder' Serbinenko > > > 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 > > > The problem i have is installing both grub2 i386-pc and x86_64-efi . > Both have /boot/grub as $grubdir . I use /boot/grub for all grub2-bios > stuff and /boot/efi/efi/grub for all grub2-efi-x86_64 related stuff. I > have not seen any issue with having modules in /efi/grub dir > itself. AFAIK the modules are platform dependent since one can't use > i386-pc modules in i386-efi and vice-versa. x86_64-efi is out of > question since its a different arch. I guess for now doing > > sed 's|/boot/grub|/boot/efi/efi/grub|g' -i grub-mkconfig > > will do, until you implement the platform specific subdir idea you > mentioned. Thanks for clarifying this. For me this is not an issue. > But I also maintain grub2 packages in Archlinux. What should I tell > the users (those who have both grub2-bios and grub2-efi-x86_64), use > /boot/efi/efi/grub for everything or do the sed stuff for > grub-{install,mkconfig}? > --boot-directory=/boot-bios and --boot-directory=/boot-efi > sed 's|/boot/grub|/boot/grub-efi|g' -i grub-{install,mkconfig} > > TIA. > > Regards. > > Keshav > > > -- > Regards > Vladimir 'φ-coder/phcoder' Serbinenko > > -- Regards Vladimir 'φ-coder/phcoder' Serbinenko