From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Normal mode linux and multiboot loaders
Date: Wed, 15 Sep 2004 11:47:13 +0200 [thread overview]
Message-ID: <200409151147.13857.okuji@enbug.org> (raw)
In-Reply-To: <87llfcpdyf.fsf@marco.marco-g.com>
On Wednesday 15 September 2004 02:34, Marco Gerards wrote:
> Now I have tested this a bit more. I found a small problem with
> fshelp and the command line parser when using GNU/Hurd. Because
> everything can be used as multiboot argument I disabled the argument
> parser for this command. I've also disabled the code that replace
> environment variables because GNU/Hurd uses variables with the same
> syntax in its bootscripts and it conflicts. :/
Honestly speaking, I think Hurd should change. Since arguments to a
Multiboot kernel do not have to be shell-like, Hurd can use a very
different way, while GRUB has a good reason to behave like a shell.
For example, Ruby uses #{...} for substitutions in strings. Hurd can use
the same, and this does not conflict with GRUB. Or, Python's %(...)s is
also nice.
If Hurd does not want to change, you should quote arguments rather than
changing the semantics. I don't like inconsistency.
> I can upload a GRUB 2 floppy somewhere including a grub.cfg and GRUB
> 2 patched with this patch so people can test GRUB 2. Please tell me
> if you want that and I will do so.
I don't think binary distributions are useful at the moment, since GRUB
2 is not stable. But it is nice to provide a script to make an image
easily.
Okuji
next prev parent reply other threads:[~2004-09-15 9:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-13 18:11 Normal mode linux and multiboot loaders Marco Gerards
2004-09-13 21:43 ` Yoshinori K. Okuji
2004-09-15 0:34 ` Marco Gerards
2004-09-15 9:47 ` Yoshinori K. Okuji [this message]
2004-09-15 14:40 ` 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=200409151147.13857.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.