All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Capello <luca@pca.it>
To: Robert Millan <rmh@aybabtu.com>
Cc: ML GRUB-devel <grub-devel@gnu.org>, 390473@bugs.debian.org
Subject: Re: Bug#390473: grub2: menuentry stanza doesn't accept $ { } in variable substitutions
Date: Tue, 24 Oct 2006 23:21:05 +0200	[thread overview]
Message-ID: <87wt6pl8am.fsf@gismo.pca.it> (raw)
In-Reply-To: 20061024132909.GA15375@khazad.dyndns.org

[-- Attachment #1: Type: text/plain, Size: 1755 bytes --]

reopen 390473
retitle 390473 grub2: menuentry stanza with additional $ or { causes boot panic
found 390473 1.95-1
thanks

Hi Robert!

NB: forwarding again to grub-devel, but setting M-F-T and R-T to the
bug, Robert (I hope you don't mind) and myself.

On Tue, 24 Oct 2006 15:29:09 +0200, Robert Millan wrote:
> Closing due to lack of response.

I'm sorry, I was quite busy in the last weeks and I never finished my
answer.
>
> 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" { $ }
>
> The panic is similar to the error generated with a $ at the
> beginning of the grub.cfg file.  While in the latter case grub2 can
> continue booting, in n the former case the only way to solve it is
> to boot with a rescue CD and remove the offending characters from
> grub2.cfg.

I reopened the bug and I changed the title to reflect the situation.

BTW, I just tested with the latest grub_1.95-1, the error is still
present, thus I added the information to the BTS.

Thx, bye,
Gismo / Luca

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

  parent reply	other threads:[~2006-10-24 21:21 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         ` Luca Capello [this message]
     [not found]           ` <20061025174949.GD28301@khazad.dyndns.org>
2006-10-30  9:21             ` Bug#390473: " Luca Capello

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=87wt6pl8am.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.