From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.33) id 1Bd53S-0007wl-M6 for mharc-grub-devel@gnu.org; Wed, 23 Jun 2004 06:32:35 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1Bd53O-0007vo-EF for grub-devel@gnu.org; Wed, 23 Jun 2004 06:32:31 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1Bd53M-0007v1-FX for grub-devel@gnu.org; Wed, 23 Jun 2004 06:32:29 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1Bd53K-0007uu-My for grub-devel@gnu.org; Wed, 23 Jun 2004 06:32:27 -0400 Received: from [212.43.237.68] (helo=kotoba.storever.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Bd51e-0003WM-61 for grub-devel@gnu.org; Wed, 23 Jun 2004 06:30:43 -0400 Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by kotoba.storever.com (Postfix) with ESMTP id 13920F0D47A0 for ; Wed, 23 Jun 2004 06:30:39 -0400 (EDT) From: "Yoshinori K. Okuji" Organization: enbug.org To: The development of GRUB 2 Date: Wed, 23 Jun 2004 12:34:42 +0200 User-Agent: KMail/1.6.1 References: <20040621180005.GA11079@artax.karlin.mff.cuni.cz> <87eko7wetu.fsf@marco.marco-g.com> <20040623071008.GB18914@artax.karlin.mff.cuni.cz> In-Reply-To: <20040623071008.GB18914@artax.karlin.mff.cuni.cz> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406231234.44326.okuji@enbug.org> Subject: Re: normal mode chainloader 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: Wed, 23 Jun 2004 10:32:32 -0000 On Wednesday 23 June 2004 09:10, Tomas Ebenlendr wrote: > > This will be fixed by the autoloading that was proposed on the > > list. If someone uses the boot command, the boot.mod will be > > autoloaded. So I think it is not a requirement. > > That is not true in all cases. E.g. when there is corrupted or > missing boot.mod, or when autoloading is off. If you cannot load boot.mod for a reason, what you get is the same as when a loader module cannot be loaded: The difference is only that you cannot execute boot or, say, linux. For ordinary users, these look identical. The only solution for these cases is to go back to the rescue mode and boot something from it. Then, there is no way to provide a good interface anyway. If autoloading is off (although I'm not sure if it is better to allow the user to turn it off), the user should know what he/she does. He/She should load all required modules explicitly. This means that this person knows how GRUB works. For this person, it is no problem to load boot.mod manually. Okuji