From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Idea: elimination of the normal mode
Date: Sat, 05 Jul 2008 22:08:35 +0300 [thread overview]
Message-ID: <486FC6B3.8060108@nic.fi> (raw)
In-Reply-To: <ca0f59980807051139id0af943o7dc1fbde3805aaff@mail.gmail.com>
Bean wrote:
> On Sun, Jul 6, 2008 at 2:10 AM, Vesa Jääskeläinen <chaac@nic.fi> wrote:
>> It has anything what core provides. If by this you get core smaller then I
>> am all for it. If it makes it larger then I would propose to find free space
>> from somewhere else. Core.img just have to be standalone application so user
>> can do recovery if something gets wrong in installation or something else.
>>
>> I do not know how well grub scripting is integrated to normal mode so check
>> that out first.
>
> With my suggestion, core.img would contain:
>
> minicmd + basic console interface + line scanner + fs modules
>
> It would be slightly bigger because we also add the option analyzer.
> But it may also reduce size due to better function separation.
It total size is smaller I do not care. If not, then I would pass it. I
still like the idea to separate rescue mode from "normal" shell mode.
This gives user an idea that grub has failed to load more of itself.
I think Robert has from time to time complained that core.img gets too
big sometimes to be embedded especially on raid configurations. So
increasing size with this does not sound good on my ears.
> the line scanner would read a config file, which instruct extra
> modules to be loaded For example, to archive the same function of
> normal mode, we need:
>
> advanced console interface + text menu interface + script engine.
>
> Some advantage of this scheme:
>
> 1, One set of command. Now, if we want to use command like search, we
> must also include normal.mod, whose purpose is just to provide the
> option analyzer.
Rescue is supposed to be minimal anyway.
> 2, The separation of interface and script engine.
> Interface deal with interaction with user, like draw the menu, choose
> an menu item, edit a string, etc. Script engine is responsible for the
> interpretation of commands. These two parts are independent, we
> shouldn't bundle them into a single normal.mod.This would make modules
> like graphic interface more difficult to implement.
Well interaction between textual menu, graphical menu and shell
interface will be studied anyway by Colin during his GSoC activities so
lets wait what we get from there before jumping too far.
next prev parent reply other threads:[~2008-07-05 19:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-05 2:46 Idea: elimination of the normal mode Bean
2008-07-05 12:15 ` Robert Millan
2008-07-05 17:06 ` Stefan Reinauer
2008-07-05 17:28 ` Vesa Jääskeläinen
2008-07-05 17:38 ` Stefan Reinauer
2008-07-05 17:53 ` Vesa Jääskeläinen
2008-07-05 18:00 ` Stefan Reinauer
2008-07-05 18:10 ` Vesa Jääskeläinen
2008-07-05 18:39 ` Bean
2008-07-05 19:08 ` Vesa Jääskeläinen [this message]
2008-07-05 17:32 ` Bean
2008-07-05 17:37 ` 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=486FC6B3.8060108@nic.fi \
--to=chaac@nic.fi \
--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.