From: Luca Capello <luca@pca.it>
To: 390473@bugs.debian.org
Cc: ML GRUB-devel <grub-devel@gnu.org>, Robert Millan <rmh@aybabtu.com>
Subject: Re: Bug#390473: grub2: menuentry stanza doesn't accept $ { } in variable substitutions
Date: Mon, 30 Oct 2006 10:21:44 +0100 [thread overview]
Message-ID: <87mz7ef9av.fsf@gismo.pca.it> (raw)
In-Reply-To: <20061025174949.GD28301@khazad.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 2185 bytes --]
Hello!
Again, forwarding to grub-devel, but setting M-F-T and R-T to the bug,
Robert and myself.
On Wed, 25 Oct 2006 19:49:49 +0200, Robert Millan wrote:
> On Tue, Oct 24, 2006 at 11:21:05PM +0200, Luca Capello wrote:
>> > On Sat, Oct 14, 2006 at 09:36:57PM +0200, Robert Millan wrote:
>> [something already present in the bug report]
>> >> According to upstream (IRC), this behaviour is consistent with
>> >> GRUB2 having its own variable support (and namespace..). So you
>> >> really need to use this new syntax (I'll take this into account
>> >> for my work on update-grub2).
>> >>
>> >> Can we close this bug now?
>>
>> While the original bug can be considered close, the boot panic
>> remains, as I explained in my first post:
>> On Sun, 01 Oct 2006 15:54:00 +0200, Luca Capello wrote:
>> > After a `grub-install /dev/hda` and a reboot, grub2 entered in a
>> > panic state at boot. Hopefully, the panic is reproducible, even
>> > on qemu: create the following stanza (you can substitute $ with a
>> > second { ):
>> >
>> > menuentry "test" { $ }
>> >
>
> That's because of syntax error. Both $ and { are reserved
> characters and must be used consistently.
I agree on this, but apart from the boot panic the main problem is the
lack of documentation, either upstream (including the wiki) and in the
Debian package: nowhere $ and { are described as reserved characters.
Obviously, the bug can hit only a very limited subset of users, the
one that want to test grub2 with GNU/Hurd.
> AFAICT, upstream doesn't consider this a bug. If you disagree, can
> you take this up with them?
I haven't receive any public answer from upstream and I cannot
understand why this won't be a bug: grub-install doesn't show any
error when installing such a config file, resulting in the boot panic,
which IMHO is a real problem.
I won't close this bug until a clear solution will be taken: this
could be a (big) warning somewhere about reserved characters
(primarily upstream, but specifically in the NEWS.Debian or
README.Debian could be OK, too) or a technical solution which will
avoid the boot panic.
Thx, bye,
Gismo / Luca
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2006-10-30 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061002151012.GA31110@khazad.dyndns.org>
[not found] ` <87wt7hhe2x.fsf@gismo.pca.it>
2006-10-03 11:48 ` grub2: menuentry stanza doesn't accept $ { } in variable substitutions Luca Capello
[not found] ` <8764ex20rb.fsf@gismo.pca.it>
[not found] ` <20061014193657.GA2927@khazad.dyndns.org>
[not found] ` <20061024132909.GA15375@khazad.dyndns.org>
2006-10-24 21:21 ` Bug#390473: " Luca Capello
[not found] ` <20061025174949.GD28301@khazad.dyndns.org>
2006-10-30 9:21 ` Luca Capello [this message]
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=87mz7ef9av.fsf@gismo.pca.it \
--to=luca@pca.it \
--cc=390473@bugs.debian.org \
--cc=grub-devel@gnu.org \
--cc=rmh@aybabtu.com \
/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.