From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.33) id 1BVqqY-0005Oy-Rv for mharc-grub-devel@gnu.org; Thu, 03 Jun 2004 07:57:23 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BVqqX-0005Oj-SW for grub-devel@gnu.org; Thu, 03 Jun 2004 07:57:21 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BVqqV-0005OW-Vv for grub-devel@gnu.org; Thu, 03 Jun 2004 07:57:21 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BVqqV-0005OK-To for grub-devel@gnu.org; Thu, 03 Jun 2004 07:57:19 -0400 Received: from [145.74.66.11] (helo=mail-cn.han.nl) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BVqpO-0005c0-Lc for grub-devel@gnu.org; Thu, 03 Jun 2004 07:56:11 -0400 Received: from localhost (charlie.han.nl [145.74.66.9]) by mail-cn.han.nl (Postfix) with ESMTP id 44C1181A9; Thu, 3 Jun 2004 13:56:08 +0200 (CEST) Received: from mail-cn.han.nl ([145.74.66.11]) by localhost (charlie.han.nl [145.74.66.9]) (amavisd-new, port 10024) with ESMTP id 23389-06; Thu, 3 Jun 2004 13:56:05 +0200 (CEST) Received: from mail1.han.nl (mail1.han.nl [145.74.103.11]) by mail-cn.han.nl (Postfix) with ESMTP id 71B7F8204; Thu, 3 Jun 2004 13:55:47 +0200 (CEST) Received: from india.han.nl (india.han.nl [145.74.103.15]) by mail1.han.nl (Postfix) with ESMTP id 255B5C04C; Thu, 3 Jun 2004 12:55:45 +0200 (CEST) Received: by india.han.nl (Postfix, from userid 48) id C67DD7865; Thu, 3 Jun 2004 13:55:46 +0200 (CEST) Received: from 145.74.169.156 ( [145.74.169.156]) as user metgerards@localhost by webmail.han.nl with HTTP; Thu, 3 Jun 2004 13:55:46 +0200 Message-ID: <1086263746.40bf11c294ce7@webmail.han.nl> Date: Thu, 3 Jun 2004 13:55:46 +0200 From: "M. Gerards" To: The development of GRUB 2 , "Yoshinori K. Okuji" References: <20040601121704.GA4680@artax.karlin.mff.cuni.cz> <20040602151116.GA6309@artax.karlin.mff.cuni.cz> <871xky2b69.fsf@marco.marco-g.com> <200406031312.39832.okuji@enbug.org> In-Reply-To: <200406031312.39832.okuji@enbug.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.1 X-Originating-IP: 145.74.169.156 X-Virus-Scanned: by amavisd-new@vscan-cn.han.nl Cc: Subject: Re: normal vs. rescue mode commands X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.4 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, 03 Jun 2004 11:57:22 -0000 Quoting "Yoshinori K. Okuji" : > On Wednesday 02 June 2004 18:10, Marco Gerards wrote: > > Okuji, you told me a while ago that you wanted to think about this. > > What is your opinion? > > I'm not sure if I understand your quesion correctly. But if it is about > sharing commands between rescue mode and normal mode, I don't want to > share them at all. Because I want to make normal mode more fancy than > now, and rescue mode cannot be fancy due to the size limitation (on > i386-pc). That is not really what I mean, but close. What I was talking about is laoders. The linux, chainloader, multiboot, etc. can be shared. Both have different access points I assume. The problem is that when you load a loader should be able access it from both normal mode and rescue mode. An example is the chainloader and linux loader compiled into rescue mode. When you load normal.mod those loaders have to be registered with normal mode. The best solution, it seems, is creating a list of modules that need to be registered with normal mode. Or just a list of modules (all modules) that can be scanned. When normal mode is started the first thing it needs to do is scan for active modules, like linux and chainloader. -- Marco