From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: grub-devel@gnu.org
Subject: config file
Date: Sun, 23 Jan 2005 15:28:59 +0100 [thread overview]
Message-ID: <200501231528.59397.okuji@enbug.org> (raw)
I'd like to raise an issue about the config file.
In GRUB Legacy, the structure of menu.lst is ugly, because it has a
strange state when interpretting it. The semantics is that commands are
executed until the first "title" is encounterred. Afterwards, commands
are only "remembered" as boot entries. I think it would be more
straightforward if commands are always executed.
I'd like to redesign it in GRUB 2. One example is to write a boot entry
like this:
entry "GNU/Hurd" {
root=(hd0,0)
multiboot /boot/gnumach
module /boot/serverboot
...
}
This idea is to make a boot entry a kind of shell function.
What do you think?
Okuji
next reply other threads:[~2005-01-23 15:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-23 14:28 Yoshinori K. Okuji [this message]
2005-01-23 15:06 ` config file Serbinenko Vladimir
2005-01-23 15:26 ` Vincent Pelletier
2005-01-23 15:13 ` Marco Gerards
2005-01-23 16:09 ` Yoshinori K. Okuji
2005-01-23 16:28 ` Vincent Pelletier
2005-01-23 17:02 ` Serbinenko Vladimir
2005-01-29 10:44 ` menu variable Serbinenko Vladimir
2005-01-29 13:37 ` Yoshinori K. Okuji
2005-01-29 14:34 ` Yoshinori K. Okuji
2005-01-23 16:44 ` config file chaac
2005-01-23 16:55 ` Vincent Pelletier
2005-01-23 17:23 ` Marco Gerards
2005-01-23 18:12 ` Yoshinori K. Okuji
2005-01-23 17:08 ` Marco Gerards
2005-01-27 18:57 ` chaac
2005-01-28 16:29 ` Marco Gerards
2005-02-04 8:23 ` Nico -telmich- Schottelius
2005-02-04 8:52 ` Yoshinori K. Okuji
-- strict thread matches above, loose matches on Subject: below --
2005-04-20 16:00 Sriharsha Vardhan
2007-10-01 11:33 Config file Aurelien Jarno
2016-07-26 5:55 config file nousi
2016-07-26 6:17 ` Mircea Gliga
2016-07-26 6:18 ` Nicolas Dechesne
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=200501231528.59397.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.