All of lore.kernel.org
 help / color / mirror / Atom feed
From: "M. Gerards" <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>,
	"Yoshinori K. Okuji" <okuji@enbug.org>
Subject: Re: normal vs. rescue mode commands
Date: Thu,  3 Jun 2004 13:55:46 +0200	[thread overview]
Message-ID: <1086263746.40bf11c294ce7@webmail.han.nl> (raw)
In-Reply-To: <200406031312.39832.okuji@enbug.org>

Quoting "Yoshinori K. Okuji" <okuji@enbug.org>:

> 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



  reply	other threads:[~2004-06-03 11:57 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-01 12:17 ext2 find patch Tomas Ebenlendr
2004-06-01 20:13 ` Tomas Ebenlendr
2004-06-01 20:47   ` Marco Gerards
2004-06-01 21:09     ` Jeroen Dekkers
     [not found]     ` <20040602100915.GA1629@artax.karlin.mff.cuni.cz>
     [not found]       ` <1086176188.40bdbbbc4d86d@webmail.han.nl>
2004-06-02 14:43         ` normal vs. rescue mode commands Tomas Ebenlendr
2004-06-02 15:11           ` Tomas Ebenlendr
2004-06-02 16:10             ` Marco Gerards
2004-06-03 11:12               ` Yoshinori K. Okuji
2004-06-03 11:55                 ` M. Gerards [this message]
2004-06-03 12:50                 ` Tomas Ebenlendr
2004-06-04 11:24                   ` Yoshinori K. Okuji
2004-06-06 10:55                     ` Tomas Ebenlendr
2004-06-09 11:19                       ` Yoshinori K. Okuji
2004-06-09 12:07                         ` Jeroen Dekkers
2004-06-09 12:25                           ` Yoshinori K. Okuji
2004-06-09 12:48                             ` Jeroen Dekkers
2004-06-09 13:12                               ` Yoshinori K. Okuji
2004-06-09 13:54                                 ` Jeroen Dekkers
2004-06-09 14:22                                   ` Yoshinori K. Okuji
2004-06-09 14:44                                     ` Jeroen Dekkers
2004-06-10 11:51                                       ` Yoshinori K. Okuji
2004-06-09 12:28                         ` Tomas Ebenlendr
2004-06-09 12:31                           ` Tomas Ebenlendr
2004-06-03 11:08           ` Yoshinori K. Okuji
2004-06-27 10:45   ` ext2 find patch Marco Gerards

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=1086263746.40bf11c294ce7@webmail.han.nl \
    --to=metgerards@student.han.nl \
    --cc=grub-devel@gnu.org \
    --cc=okuji@enbug.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.