On Sat, 8 Nov 2008, Faheem Mitha wrote:
Package: grub
Version: 0.97-47
Severity: normal
As can be seen by looking at menu.lst, update-grub generates Xen
config sections even though Xen kernels are not currently present (I
recently purged them).
Currently installed kernels follow.
orwell:/home/faheem# COLUMN=200 dpkg -l | grep linux-image
ii linux-image-2.6-vserve 2.6.26+16 Linux 2.6 image on
PPro/Celeron/PII/PIII/P4
ii linux-image-2.6-vserve 2.6.26+16 Linux 2.6 image on
PPro/Celeron/PII/PIII/P4
ii linux-image-2.6.18-6-6 2.6.18.dfsg.1-22etch2 Linux 2.6.18 image
on PPro/Celeron/PII/PIII/P4
ii linux-image-2.6.18-6-v 2.6.18.dfsg.1-22etch2 Linux 2.6.18 image
on PPro/Celeron/PII/PIII/P4
ii linux-image-2.6.18.080 custom.1.0 Linux kernel binary
image for version 2.6.18.080131
ii linux-image-2.6.26-1-v 2.6.26-8 Linux 2.6.26 image
on PPro/Celeron/PII/PIII/P4, Linux-VServe
ii linux-image-2.6.26-1-v 2.6.26-8 Linux 2.6.26 image
on PPro/Celeron/PII/PIII/P4, Linux-VServe
Based on the following output, it seems possible that update-grub
assumes that is should create a xen entry if xen is installed, even if
the kernel has no xen support, which is just retarded.
Note; after removing all xen related packages, the offending xen
entries in menu.lst disappear, as expected.
Faheem.
orwell:/home/faheem# update-grub
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found:
/boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found Xen hypervisor 3.0.3-1-i386-pae, kernel:
/vmlinuz-2.6.26-1-vserver-686-bigmem
Found kernel: /vmlinuz-2.6.26-1-vserver-686-bigmem
Found kernel: /vmlinuz-2.6.26-1-vserver-686
Found kernel: /vmlinuz-2.6.18.080131
Found kernel: /vmlinuz-2.6.18-6-vserver-686
Found kernel: /vmlinuz-2.6.18-6-686-bigmem
Found kernel: /memtest86+.bin
Updating /boot/grub/menu.lst ... done
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]