From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: grub-devel@gnu.org
Subject: some design issues
Date: Mon, 14 Feb 2005 22:25:36 +0100 [thread overview]
Message-ID: <200502142225.36773.okuji@enbug.org> (raw)
I'd like to hear your opinions about some design-related issues.
Currently, GRUB 2 uses grub.cfg as the name of a default config file. I
chose this, according to a private discussion between me and Jeremy
Katz. He pointed out that the user did not find a config file if it was
menu.lst, because he/she simply ran "locate grub". So the Red Hat
version of GRUB legacy makes a symlink to menu.lst as grub.conf. I said
that this name does not fit in 8.3 format. He agreed but he didn't want
to discuss what name should be better.
I think the name "menu.lst" is really strange, so I don't like it. But I
don't know if grub.cfg is nice. What do you think? I sometimes think
that "grubrc" might be better (like "bashrc").
Next thing. I think it is a bad idea to make the variable for a menu
global, because this is not compatible with having multiple nested
menus. But some commands want to access information on the environment
(such as current menu). I can think of two ways to address this issue:
1. Pass one more argument to each command. This argument would be a
pointer to struct context, and contains a pointer to current menu, etc.
2. Provide global functions to access information. These functions would
have to use global variables.
I don't know which is better.
Okuji
next reply other threads:[~2005-02-14 21:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-14 21:25 Yoshinori K. Okuji [this message]
2005-02-15 6:14 ` some design issues Paul
2005-02-15 16:24 ` Hollis Blanchard
2005-02-15 22:15 ` Yoshinori K. Okuji
2005-02-15 19:41 ` Marco Gerards
2005-02-15 22:17 ` Yoshinori K. Okuji
2005-02-16 18:05 ` Marco Gerards
2005-02-16 20:49 ` Yoshinori K. Okuji
2005-02-15 20:24 ` Vincent Pelletier
2005-02-15 22:23 ` Yoshinori K. Okuji
2005-02-16 16:01 ` Serbinenko Vladimir
2005-02-16 21:07 ` Yoshinori K. Okuji
2005-02-17 16:03 ` Serbinenko Vladimir
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=200502142225.36773.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.