All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: normal mode chainloader
Date: Wed, 23 Jun 2004 12:34:42 +0200	[thread overview]
Message-ID: <200406231234.44326.okuji@enbug.org> (raw)
In-Reply-To: <20040623071008.GB18914@artax.karlin.mff.cuni.cz>

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



  reply	other threads:[~2004-06-23 10:32 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-21 18:00 normal mode chainloader Tomas Ebenlendr
2004-06-22  9:00 ` Marco Gerards
2004-06-22 11:33   ` Tomas Ebenlendr
2004-06-22 19:52     ` Marco Gerards
2004-06-23  7:10       ` Tomas Ebenlendr
2004-06-23 10:34         ` Yoshinori K. Okuji [this message]
2004-06-23 10:40           ` Tomas Ebenlendr
2004-06-22 11:41   ` Tomas Ebenlendr
2004-06-22 20:25     ` Marco Gerards
2004-06-23  7:29       ` Tomas Ebenlendr
2004-06-23 10:55         ` Marco Gerards
2004-06-23 17:20           ` Jeroen Dekkers
2004-06-23  8:11       ` Copyright crap Was: " Tomas Ebenlendr
2004-06-23  8:59         ` Jeroen Dekkers
2004-06-23 10:43           ` Tomas Ebenlendr
2004-06-23 11:58       ` Tomas Ebenlendr
2004-06-23 16:49         ` Marco Gerards
2004-06-24  8:44           ` Tomas Ebenlendr
2004-06-24 15:26             ` Marco Gerards
2004-06-24 16:51               ` Tomas Ebenlendr
2004-07-01 10:54                 ` Marco Gerards
2004-07-01 11:17                   ` Yoshinori K. Okuji
2004-07-01 11:53                     ` Tomas Ebenlendr
2004-07-01 13:30                       ` Marco Gerards
2004-07-01 16:03                         ` history, autoloading was: " Tomas Ebenlendr
2004-09-10 22:05                         ` Marco Gerards
2004-09-12 12:46         ` Marco Gerards
2004-09-17 18:48           ` Tomas Ebenlendr
2004-09-17 18:53             ` M. Gerards
2004-09-17 19:32               ` Tomas Ebenlendr
2004-09-17 19:38                 ` M. Gerards
2004-09-20  6:58                   ` Tomas Ebenlendr
2004-09-21  8:22                     ` Module loading - grub-emu, bug in kern/dl.c Tomas Ebenlendr
2004-11-17 15:43                       ` Marco Gerards
2004-11-17 20:30                         ` Tomas Ebenlendr
2004-11-17 20:45                           ` Marco Gerards
2004-11-22 15:18                         ` Timothy Baldwin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200406231234.44326.okuji@enbug.org \
    --to=okuji@enbug.org \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.