From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Ky8aO-0006Vf-8q for mharc-grub-devel@gnu.org; Thu, 06 Nov 2008 12:24:00 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ky8aL-0006Uw-QA for grub-devel@gnu.org; Thu, 06 Nov 2008 12:23:57 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ky8aJ-0006Uh-Sj for grub-devel@gnu.org; Thu, 06 Nov 2008 12:23:56 -0500 Received: from [199.232.76.173] (port=57686 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ky8aJ-0006Ue-N5 for grub-devel@gnu.org; Thu, 06 Nov 2008 12:23:55 -0500 Received: from ns39764.ovh.net ([91.121.25.85]:34942 helo=nexedi.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Ky8aJ-0001SC-QD for grub-devel@gnu.org; Thu, 06 Nov 2008 12:23:56 -0500 Received: from [10.8.0.46] (unknown [10.8.0.46]) by nexedi.com (Postfix) with ESMTP id 19E5A3E15E for ; Thu, 6 Nov 2008 18:23:54 +0100 (CET) From: "Yoshinori K. Okuji" Organization: enbug.org To: The development of GRUB 2 Date: Thu, 6 Nov 2008 18:23:15 +0100 User-Agent: KMail/1.9.9 References: <20081104203627.GA28595@thorin> In-Reply-To: <20081104203627.GA28595@thorin> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200811061823.15421.okuji@enbug.org> X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) Subject: Re: Multiboot2 header X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Nov 2008 17:23:58 -0000 On Tuesday 04 November 2008 21:36:27 Robert Millan wrote: > The Multiboot2 draft says a Multiboot2 header must be included in the OS > image. However, our code assumes (in code itself and in comments) that for > MB2 this is optional. > > As a consequence, if you feed GRUB's multiboot loader any ELF, it will > attempt to load it. I think this is very confusing for those developing > a Multiboot _1_ OS. If they happen to make a mistake and put the MB1 > header too high or unaligned, GRUB won't tell them about it but instead > fail in a very confusing way. > > So I assume (I'd like to!) that the correct one is the draft, and it's the > code that should be changed to reject executables that don't have either > MB1 or MB2 headers? Yes. The code is wrong. Regards, Okuji