From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1GR7Z5-0007G9-8K for mharc-grub-devel@gnu.org; Sat, 23 Sep 2006 09:29:07 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GR7Z3-0007Aj-9o for grub-devel@gnu.org; Sat, 23 Sep 2006 09:29:05 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GR7Z1-00077G-If for grub-devel@gnu.org; Sat, 23 Sep 2006 09:29:05 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GR7Z1-000774-Cw for grub-devel@gnu.org; Sat, 23 Sep 2006 09:29:03 -0400 Received: from [204.127.225.94] (helo=alnrmhc14.comcast.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GR7cz-0003sW-GG for grub-devel@gnu.org; Sat, 23 Sep 2006 09:33:09 -0400 Received: from [192.168.102.31] (c-24-99-61-70.hsd1.ga.comcast.net[24.99.61.70]) by comcast.net (alnrmhc14) with ESMTP id <20060923132901b1400j8heme>; Sat, 23 Sep 2006 13:29:01 +0000 Message-ID: <45153675.1020603@comcast.net> Date: Sat, 23 Sep 2006 09:28:21 -0400 From: Damon Register User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: The development of GRUB 2 References: <4512E68E.1030306@lmco.com> <4513D925.8090802@draigBrady.com> In-Reply-To: <4513D925.8090802@draigBrady.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: when is menu.lst read in grub process 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: Sat, 23 Sep 2006 13:29:05 -0000 Pádraig Brady wrote: > I had the same issue when I had to setup grub in a non standard way. > I read the source and documented the process here: > http://www.pixelbeat.org/docs/disk/ That is really great. Thanks. I think this should be part of the official grub documentation or at least a link should be provided, Your process description seems to confirm what others have said, that menu.lst is read by stage 2 and therefore menu.lst can be tampered without reinstall of grub. There is one thing that still remains confusing for me. You say about stage 1 Bootloader jumps to location (sector num) of next stage. This sector num is stored at a particular location in the bootloader "code" at grub install time and usually points to a stage 1.5 located in the "DOS compat space" immediately after the MBR. How does the grub install process know the correct number to store in stage 1? That location does not come from menu.lst? Damon Register