All of lore.kernel.org
 help / color / mirror / Atom feed
From: phcoder <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Split of normal mode (version 2)
Date: Sat, 04 Apr 2009 00:19:46 +0200	[thread overview]
Message-ID: <49D68B82.2080001@gmail.com> (raw)
In-Reply-To: <200904040512.15522.okuji@enbug.org>

> We can just put them in the normal.mod. What is wrong? Frankly, your argument 
> reminds me of the old discussion about monolithic vs. micro kernels...
Yes, it's quite similar and IMO it's better to have more small modules. 
It also forces to code in an abstratc way which simplifies the maintaining
> setjmp is required for the switch between rescue mode and normal mode. 

It isn't. You can just call the corresponding function. What's wrong 
with such approach?


-- 

Regards
Vladimir 'phcoder' Serbinenko



  reply	other threads:[~2009-04-03 22:19 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 [this message]
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
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=49D68B82.2080001@gmail.com \
    --to=phcoder@gmail.com \
    --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.