From: The Gluglug <info@gluglug.org.uk>
To: arvidjaar@gmail.com
Cc: lunar@torproject.org
Subject: Re: [bug #44238] Add support for menu.c32 and vesamenu.c32 in lib/syslinux_parse
Date: Sat, 14 Feb 2015 03:26:26 +0000 [thread overview]
Message-ID: <54DEC062.5040408@gluglug.org.uk> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
<fchmmr> Lunar^, I updated to the latest GRUB and tested those 2
patches. Tails does indeed boot as you said. However, Trisquel
ISOLINUX menu now no longer appears: I see these 3 messages: "error:
syntax error.", "error: Incorrect command.", "error: syntax error.".
This is with Trisquel 7.0 GNOME, which you can find at
https://trisquel.info/
<fchmmr> Lunar^, shall we take this to #grub?
<fchmmr> Lunar^, this is with the very first patches that you sent. I
just noticed the follow-up patches that you posted to grub-devel; I'll
try those instead.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJU3sBiAAoJEP9Ft0z50c+UDEUIAIQK0BmGQSoD51yfV4xIcvfG
xC82w8ddJICSfo2YZjSbKdcKJZvOKzxZgeudx2f2OVkta2VbHbN6qtNl2IXWxtvH
JdMAK9wb/5NQXJ16EGTOYxuzB7eXpyzsY8P44c0O1nS3UxtFsyEGWxS5Mm/JJHMD
ROGluN8D2cIgD3vnqtiOl7nOQCqx7ReOdNkUAn454KazP6N7hThtB/XGmF07i3+x
HukKTnx5s19wnottlbL+yqaQiYLpdlM3ZyXZ49ZHA0V0b6ULuM07wPe06V2n698G
Kak4fqgZsW3SipMOdMJUCSRAbrZ2+CmPUhCpzwcwlIQFVQfU+OKED+xqhkL+Jwc=
=FdlH
-----END PGP SIGNATURE-----
next reply other threads:[~2015-02-14 5:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-14 3:26 The Gluglug [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-03-17 17:40 [bug #44238] Add support for menu.c32 and vesamenu.c32 in lib/syslinux_parse The Gluglug
[not found] <20150213-163409.sv98365.64186@savannah.gnu.org>
[not found] ` <20150213-190108.sv89796.21318@savannah.gnu.org>
2015-02-13 20:20 ` Lunar
2015-02-13 20:40 ` Andrei Borzenkov
2015-02-13 21:09 ` Lunar
2015-02-14 6:15 ` Andrei Borzenkov
2015-02-14 8:22 ` Lunar
2015-02-14 17:48 ` Andrei Borzenkov
2015-03-17 17:41 ` The Gluglug
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=54DEC062.5040408@gluglug.org.uk \
--to=info@gluglug.org.uk \
--cc=arvidjaar@gmail.com \
--cc=grub-devel@gnu.org \
--cc=lunar@torproject.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.