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: [PATCH] Split of normal mode (version 2)
Date: Mon, 6 Apr 2009 00:43:02 +0900	[thread overview]
Message-ID: <200904060043.03075.okuji@enbug.org> (raw)
In-Reply-To: <ca0f59980904050802p6745c631q33667eb3202b8e44@mail.gmail.com>

On Monday 06 April 2009 00:02:59 Bean wrote:
> On Sun, Apr 5, 2009 at 10:33 PM, Yoshinori K. Okuji <okuji@enbug.org> wrote:
> > On Saturday 04 April 2009 14:06:18 Bean wrote:
> >> One of the problem for normal.mod dependency is its side effect. For
> >> example, currently ls.mod depend on normal.mod just for
> >> grub_normal_print_device_info. If we want to embed ls.mod in core.img,
> >> we must embedded normal.mod as well, along with a lot of
> >> initialization actions that we may not want.
> >
> > Right, if we can completely merge the ls on rescue mode and that on
> > normal mode. For now, I am not sure if this is feasible, so I prefer to
> > keep a poor version of ls for rescue mode, which does not require
> > functions in normal.mod, until you prove that that is feasible.
>
> Hi,
>
> Currently, this is implemented using priority list. The commands has a
> field that indicate its priority. For normal command, the value is 0,
> for extended command, it's 1. So if two version of ls is loaded, the
> extended ls would be used. All commands are in a unify set, so you can
> run normal commads/extended commands in either rescue or normal mode.

Great. As long as we can use a smaller (so more stupid) version of ls, I have 
no objection.

Regards,
Okuji



  reply	other threads:[~2009-04-05 15:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-30 17:41 [PATCH] Split of normal mode (version 2) Bean
2009-04-03 18:40 ` Yoshinori K. Okuji
2009-04-03 19:49   ` Bean
2009-04-03 20:12     ` Yoshinori K. Okuji
2009-04-03 22:19       ` phcoder
2009-04-03 23:02         ` Colin D Bennett
2009-04-05 14:23           ` Yoshinori K. Okuji
2009-04-04  5:06       ` Bean
2009-04-05 14:33         ` Yoshinori K. Okuji
2009-04-05 15:02           ` Bean
2009-04-05 15:43             ` Yoshinori K. Okuji [this message]
2009-04-06 16:39               ` Bean
2009-04-07  0:41                 ` Yoshinori K. Okuji
2009-04-09 23:49                 ` Yoshinori K. Okuji
2009-04-10  5:17                   ` Bean
2009-04-10 20:17                     ` Bean
2009-04-11  9:50                       ` Yoshinori K. Okuji
2009-04-11 14:03                         ` Bean

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=200904060043.03075.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.