From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: NESTED_FUNC_ATTR (was: Re: iso9660 support)
Date: Sun, 17 Oct 2004 22:37:05 +0200 [thread overview]
Message-ID: <200410172237.05155.okuji@enbug.org> (raw)
In-Reply-To: <20041017184953.GA24688@artax.karlin.mff.cuni.cz>
On Sunday 17 October 2004 20:49, Tomas Ebenlendr wrote:
> No, it isn't. I think grub-emu is important for example for saving
> default menu entry mechanism or so.
I don't agree. Please look at GRUB legacy. It does not use the grub
shell to save a defaule entry.
> And I think, that in such case will be less confusing,
> when there will be one binary (module) for both grub-emu and grub
> (boottime).
I don't think so, because grub-emu is useful only for developers.
Ordinary users don't care.
> So, what is the size constraint? Is it for machines with small stack?
No. This is the same as GRUB legacy. We want to use free space right
after the MBR, but this region is quite small (normally, 31KB). I
reduced the binary size very seriously to make core.img fit in this
region, and I don't want to give it up.
Okuji
next prev parent reply other threads:[~2004-10-17 20:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 22:39 iso9660 support Marco Gerards
2004-10-14 23:27 ` Johan Rydberg
2004-10-15 0:20 ` NESTED_FUNC_ATTR (was: Re: iso9660 support) Tomas Ebenlendr
2004-10-15 1:16 ` Johan Rydberg
2004-10-15 8:40 ` Yoshinori K. Okuji
2004-10-17 18:49 ` Tomas Ebenlendr
2004-10-17 19:41 ` Marco Gerards
2004-10-17 20:31 ` Tomas Ebenlendr
2004-10-17 20:37 ` Marco Gerards
2004-10-17 20:42 ` Yoshinori K. Okuji
2004-10-17 20:38 ` Yoshinori K. Okuji
2004-10-17 20:37 ` Yoshinori K. Okuji [this message]
2004-10-17 20:48 ` Marco Gerards
2004-10-17 21:42 ` Yoshinori K. Okuji
2004-10-18 6:56 ` Marco Gerards
2004-10-15 10:46 ` iso9660 support 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=200410172237.05155.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.