Bug#867804: cdrom: Stretch netinst CD installs grub config file incorrectly

[Steve McIntyre]

On Tue, Jul 11, 2017 at 12:43:13PM +0100, Hazel Russman wrote:
>On Mon, 10 Jul 2017 17:50:45 +0100
>Steve McIntyre <steve at einval.com> wrote:
>> 
>> I'm wondering if *maybe* something has been confused by those lilo
>> setups, but I'll admit that I'm not sure what's happening there.

...

>No need to do that! I've found the error. I ran grub-mkconfig by hand
>and here's what it gave me:
>
>grub-mkconfig -o testfile
>Generating grub configuration file ...
>Found background image: /usr/share/images/desktop-base/desktop-grub.png
>Found linux image: /boot/vmlinuz-4.9.0-3-amd64
>Found initrd image: /boot/initrd.img-4.9.0-3-amd64
>Found Crux GNU/Linux 3.3 on /dev/sda1
>Found Linux From Scratch (7.10-rc1) on /dev/sda5
>Found Linux From Scratch (8.0-rc1) on /dev/sda6
>error: syntax error.
>error: Incorrect command.
>error: syntax error.
>Syntax error at line 226
>Syntax errors are detected in generated GRUB config file.
>Ensure that there are no errors in /etc/default/grub
>and /etc/grub.d/* files or please file a bug report with testfile.new file attached.
>
>That's why the file wasn't renamed. The script didn't fail; it did
>what it was supposed to do. And if I installed grub now, I bet it still
>wouldn't work because of those errors in the config file. I'd just end
>up with a grub prompt again. So, if you don't mind, I won't do that for
>now.
>
>Instead I'm attaching the newly-created config file,
>the /etc/defaults/grub file, and a tarball of /etc/grub.d. I could
>probably examine those files from here to Sunday and not see where the
>error was, but you will probably spot it at once!

Hi Hazel,

I *think* my first guess was right - look at the line 190 in
testfile.new:

        linux /boot/vmlinuz-4.9.6 root=/dev/sda1 ro vga = normal append = "quiet

That's blatantly broken, if nothing else for the missing closing
quotes. I'd also suspect the "vga = normal" of not doing the right
thing. This looks very like a mis-parsing of the various lilo.conf
files you have.

Could you attach those too, please? This looks like a bug for upstream
to look into, and they're going to need those files too I assume...

-- 
Steve McIntyre, Cambridge, UK.                                steve at einval.com
There's no sensation to compare with this
Suspended animation, A state of bliss