Your message dated Tue, 16 Jun 2009 22:35:54 +0200
with message-id <[email protected]>
and subject line Re: Bug#532653: grub2: debconf extracts only the first command
argument to the linux kernel from /boot/grub/menu.lst
has caused the Debian Bug report #532653,
regarding grub2: debconf extracts only the first command argument to the linux
kernel from /boot/grub/menu.lst
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
532653: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=532653
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: grub2
Version: 1.96+20090317-1
Severity: normal
When installing grub2, one is first asked whether to chainload grub, afterwards
which arguments should be configured
for the linux kernel. In the last question, the text field only shows the first
argument, in my case
acpi_sleep=s3_bios, but the arguments afterwards (usbcore.autosuspend=1
rootfstype=ext4) are not shown.
Given that mostly experienced users will install grub2 i’m filing this bug as
severity: normal, however for
example the rootfstype=ext4 option would prevent my system from booting if not
specified.
-- Package-specific info:
*********************** BEGIN /proc/mounts
/dev/mapper/x200-root / ext4
rw,noatime,errors=remount-ro,commit=600,barrier=1,data=ordered 0 0
/dev/sda1 /boot ext3 rw,noatime,errors=continue,commit=600,data=ordered 0 0
*********************** END /proc/mounts
*********************** BEGIN /boot/grub/device.map
(hd0) /dev/sda
*********************** END /boot/grub/device.map
*********************** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
set default=0
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry "Debian GNU/Linux, linux 2.6.30-7" {
set root=(hd0,1)
search --fs-uuid --set e2c78c62-2617-4203-90d1-7760f11d28b2
linux /vmlinuz-2.6.30-7 root=/dev/mapper/x200-root ro
acpi_sleep=s3_bios usbcore.autosuspend=1 rootfstype=ext4
initrd /initrd.img-2.6.30-7
}
menuentry "Debian GNU/Linux, linux 2.6.30-7 (recovery mode)" {
set root=(hd0,1)
search --fs-uuid --set e2c78c62-2617-4203-90d1-7760f11d28b2
linux /vmlinuz-2.6.30-7 root=/dev/mapper/x200-root ro single
acpi_sleep=s3_bios usbcore.autosuspend=1 rootfstype=ext4
initrd /initrd.img-2.6.30-7
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_memtest86+ ###
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file is an example on how to add custom entries
### END /etc/grub.d/40_custom ###
*********************** END /boot/grub/grub.cfg
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (600, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30-7 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages grub2 depends on:
ii grub-pc 1.96+20090317-1 GRand Unified Bootloader, version
grub2 recommends no packages.
grub2 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Am Donnerstag, den 11.06.2009, 21:59 +0200 schrieb Michael Stapelberg:
> Hi Felix,
>
> * [11.06.09 21:49]:
> > I just tried it out myself, but with the current experimental version.
> > It worked fine. I had `x=y a=b c=d' appended to kopt in menu.lst then
> > installed grub2 and choose to chainload it and /etc/default/grub had all
> > parameters and also the generated grub.cfg.
> > The part in the postinst which changes the GRUB_CMDLINE_LINUX
> > in /etc/default/grub has been last modified on 6th May and this only to
> > escape / and \
> > So are you sure that this was with 1.96+20090317-1 and not some earlier
> > version?
> It was precisely with the version reported in the bug, I never used another
> grub2 package.
Hi,
I just tried the current squeeze version out and it had the same
problem. As I expected the grub-pc.postinst isn't different in the part
which deals with the kopt between that and current sid version.
The only difference is we introduced a new template so that there's now
an empty line after the grub-pc/linux_cmdline template, but it would be
very weird if that would be the reason for this.
Anyway closing the bug as this seems to be really fixed now in sid and
it should arrive in 4-5 days squeeze.
Though if you want to test this again you'd need to purge grub-pc else
the question isn't asked again.
--
Felix Zielcke
--- End Message ---
