Bug#465144: menu.lst: wrong default entry 0saved
Hello,
the problem is in legacy/update-grub
grub_set_default starting on line 1050
set_default_value() {
if [ $use_grub_set_default = true ] ; then
grub-set-default $1
else
value=$1
newmenu=$(tempfile)
sed -e s/^[[:blank:]]*default[[:blank:]]*[[:digit:]]*\(.*\)/default
${value}\1/;b $menu $newmenu
cat $newmenu $menu
rm -f $newmenu
unset newmenu
fi
}
For me this regexp looks a bit stupid.
default optional numberanything is converted to default $valueanything
If that \1 is removed then it's just default 0.
If you want to regenerate menu.lst with chainloading grub2,
# LET_US_TRY_GRUB_2=true /usr/lib/grub-legacy/update-grub
--
Felix Zielcke
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#465144: menu.lst: wrong default entry 0saved
I'd rather have /boot/grub cleaned up from any grub legacy cruft, everything imported into grub2 and simply make grub2 bullet proof, so the chain-loading workaround is no longer necessary If you choose to chainload then debconf tells you to use upgrade-from-grub-legacy which cleans up grub-legacy's file from /boot/grub But else neither grub-legacy's files nor grub2's files are cleaned up from /boot/grub Please see 470400 Is this 0saved problem still an issue with current grub-legacy and grub-pc versions in sid? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#465144: menu.lst: wrong default entry 0saved
Robert Millan wrote: On Mon, Feb 11, 2008 at 01:08:48AM +0100, Michael Biebl wrote: Robert Millan wrote: On Sun, Feb 10, 2008 at 11:25:45PM +0100, Michael Biebl wrote: Package: grub-pc Version: 1.96+20080209-1 Severity: normal After installing grub-pc, I got the option to chainload grub2 from /boot/grub/menu.lst, which I chose. I use default saved in /boot/grub/menu.lst After the installation this entry was changed to default 0saved which is obviously wrong. How does GRUB Legacy react to this oddity? The saved default boot entry will not be selected. It falls back to boot the first boot entry. That is the intended behaviour. When you uninstall grub-pc, is menu.lst restored to a sane state? (either default 0 or default saved) I had re-run dpkg-reconfigure grub-pc and disabled the chain-loading. Now rerunning dpkg-reconfigure grub-pc and enabling chain-loading again doesn't update /boot/grub/menu.lst. So I can't tell if menu.lst is restored to a sane state after removing grub-pc. What I can tell though is that uninstalling grub-pc leaves *a lot* of cruft in /boot/grub/. I'm not sure, if the chain-loading idea is so great. I'd rather have /boot/grub cleaned up from any grub legacy cruft, everything imported into grub2 and simply make grub2 bullet proof, so the chain-loading workaround is no longer necessary. Would seem to be a cleaner solution to me. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#465144: menu.lst: wrong default entry 0saved
On Mon, Feb 11, 2008 at 01:08:48AM +0100, Michael Biebl wrote: Robert Millan wrote: On Sun, Feb 10, 2008 at 11:25:45PM +0100, Michael Biebl wrote: Package: grub-pc Version: 1.96+20080209-1 Severity: normal After installing grub-pc, I got the option to chainload grub2 from /boot/grub/menu.lst, which I chose. I use default saved in /boot/grub/menu.lst After the installation this entry was changed to default 0saved which is obviously wrong. How does GRUB Legacy react to this oddity? The saved default boot entry will not be selected. It falls back to boot the first boot entry. That is the intended behaviour. When you uninstall grub-pc, is menu.lst restored to a sane state? (either default 0 or default saved) -- Robert Millan GPLv2 I know my rights; I want my phone call! DRM What use is a phone call… if you are unable to speak? (as seen on /.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#465144: menu.lst: wrong default entry 0saved
Package: grub-pc
Version: 1.96+20080209-1
Severity: normal
After installing grub-pc, I got the option to chainload grub2 from
/boot/grub/menu.lst, which I chose.
I use
default saved
in /boot/grub/menu.lst
After the installation this entry was changed to
default 0saved
which is obviously wrong.
Cheers,
Michael
-- Package-specific info:
*** BEGIN /proc/mounts
rootfs / rootfs rw 0 0
none /sys sysfs rw,nosuid,nodev,noexec 0 0
none /proc proc rw,nosuid,nodev,noexec 0 0
udev /dev tmpfs rw 0 0
/dev/sda6 / ext3 rw,relatime,errors=remount-ro,user_xattr,acl,data=ordered 0 0
/dev/sda6 /dev/.static/dev ext3
rw,errors=remount-ro,user_xattr,acl,data=ordered 0 0
tmpfs /lib/init/rw tmpfs rw,nosuid 0 0
usbfs /proc/bus/usb usbfs rw,nosuid,nodev,noexec 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
devpts /dev/pts devpts rw,nosuid,noexec 0 0
fusectl /sys/fs/fuse/connections fusectl rw 0 0
/dev/sda7 /home reiserfs rw,relatime 0 0
/dev/sda3 /mnt/gemeinsam vfat
rw,nosuid,nodev,uid=1000,gid=1000,fmask=,dmask=,codepage=cp437,iocharset=iso8859-1,utf8
0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,nosuid,nodev,noexec 0 0
/dev/sda1 /mnt/windows fuseblk
rw,nosuid,nodev,user_id=0,group_id=1000,default_permissions,allow_other 0 0
/dev/scd0 /media/Data iso9660 ro,nosuid,nodev 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/update-grub using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
set default=0
set timeout=5
set root=(hd0,6)
if font (hd0,6)/usr/share/grub/unicode.pff ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
terminal gfxterm
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod tga
if background_image
(hd0,6)/usr/share/images/desktop-base/debian-blueish-wallpaper-640x480.tga ;
then
set color_normal=black/black
set color_highlight=magenta/black
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_hurd ###
### END /etc/grub.d/10_hurd ###
### BEGIN /etc/grub.d/10_linux ###
menuentry Debian GNU/Linux, linux 2.6.24.1 {
linux (hd0,6)/boot/vmlinuz-2.6.24.1 root=/dev/sda6 ro
initrd (hd0,6)/boot/initrd.img-2.6.24.1
}
menuentry Debian GNU/Linux, linux 2.6.24.1 (single-user mode) {
linux (hd0,6)/boot/vmlinuz-2.6.24.1 root=/dev/sda6 ro single
initrd (hd0,6)/boot/initrd.img-2.6.24.1
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry Memory test (memtest86+) {
linux (hd0,6)/boot/memtest86+.bin
}
### END /etc/grub.d/20_memtest86+ ###
*** END /boot/grub/grub.cfg
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (300, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.24.1
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages grub-pc depends on:
ii base-files4.0.2 Debian base system miscellaneous f
ii debconf [debconf-2.0] 1.5.19 Debian configuration management sy
ii libc6 2.7-6 GNU C Library: Shared libraries
ii liblzo2-2 2.02-3 data compression library
ii libncurses5 5.6+20080203-1 Shared libraries for terminal hand
grub-pc recommends no packages.
-- debconf information:
* grub-pc/chainload_from_menu.lst: true
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#465144: menu.lst: wrong default entry 0saved
On Sun, Feb 10, 2008 at 11:25:45PM +0100, Michael Biebl wrote: Package: grub-pc Version: 1.96+20080209-1 Severity: normal After installing grub-pc, I got the option to chainload grub2 from /boot/grub/menu.lst, which I chose. I use default saved in /boot/grub/menu.lst After the installation this entry was changed to default 0saved which is obviously wrong. How does GRUB Legacy react to this oddity? -- Robert Millan GPLv2 I know my rights; I want my phone call! DRM What use is a phone call… if you are unable to speak? (as seen on /.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#465144: menu.lst: wrong default entry 0saved
Robert Millan wrote: On Sun, Feb 10, 2008 at 11:25:45PM +0100, Michael Biebl wrote: Package: grub-pc Version: 1.96+20080209-1 Severity: normal After installing grub-pc, I got the option to chainload grub2 from /boot/grub/menu.lst, which I chose. I use default saved in /boot/grub/menu.lst After the installation this entry was changed to default 0saved which is obviously wrong. How does GRUB Legacy react to this oddity? The saved default boot entry will not be selected. It falls back to boot the first boot entry. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
