Lilo gets installed on dist-upgrades, due to the kernel image recommending it. Is this intentional?
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Release Notes for Ubuntu |
Fix Released
|
Undecided
|
Colin Watson | ||
linux (Ubuntu) |
Fix Released
|
Medium
|
Andy Whitcroft | ||
Jaunty |
Fix Released
|
Medium
|
Andy Whitcroft | ||
ubiquity (Ubuntu) |
Fix Released
|
Critical
|
Colin Watson | ||
Jaunty |
Fix Released
|
Critical
|
Colin Watson | ||
update-manager (Ubuntu) |
Fix Released
|
High
|
Michael Vogt | ||
Jaunty |
Fix Released
|
High
|
Michael Vogt |
Bug Description
Lilo gets installed on dist-upgrades, due to the kernel image recommending it. Is this intentional? It would seem odd to have two bootloaders installed on dist-upgrades, effectively by default.
NOTE: that actually lilo was not installed on dist-upgrade but mearly upgraded. However lilo was not expected to be installed and therefore was not expected to be updated when the upgrade was performed.
Package: linux-image-
Priority: optional
Section: base
Installed-Size: 92196
Maintainer: Ubuntu Kernel Team <email address hidden>
Architecture: i386
Source: linux
Version: 2.6.28-4.6
Provides: fuse-module, ivtv-modules, kvm-api-4, linux-image, linux-image-2.6, ndiswrapper-
Depends: initramfs-tools (>= 0.36ubuntu6), coreutils | fileutils (>= 4.0), module-init-tools (>= 3.3-pre11-4ubuntu3)
Pre-Depends: dpkg (>= 1.10.24)
Recommends: lilo (>= 19.1) | grub
Suggests: fdutils, linux-doc-2.6.28 | linux-source-2.6.28
Conflicts: hotplug (<< 0.0.20040105-1)
Filename: pool/main/
Size: 23775268
MD5sum: a88e826290466b4
SHA1: 154b7912b272e16
SHA256: dceeac31badc318
Description: Linux kernel image for version 2.6.28 on x86/x86_64
This package contains the Linux kernel image for version 2.6.28 on
x86/x86_64.
.
Also includes the corresponding System.map file, the modules built by the
packager, and scripts that try to ensure that the system is not left in an
unbootable state after an update.
.
Supports Generic processors.
.
Geared toward desktop systems.
.
You likely do not want to install this package directly. Instead, install
the linux-generic meta-package, which will ensure that upgrades work
correctly, and that supporting packages are also installed.
Bugs: mailto:<email address hidden>
Origin: Ubuntu
Changed in linux: | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in linux: | |
assignee: | nobody → apw |
status: | Triaged → In Progress |
Changed in ubiquity: | |
status: | Triaged → Fix Committed |
description: | updated |
Changed in linux: | |
milestone: | none → jaunty-alpha-3 |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu): | |
assignee: | Andy Whitcroft (apw) → gatoseco94@hotmail.com (gatoseco94) |
Changed in linux (Ubuntu): | |
assignee: | gatoseco94@hotmail.com (gatoseco94) → Andy Whitcroft (apw) |
Talked to Hobsee a little about this on IRC. It seems that they are finding both lilo and grub installed and seeing lilo updated as they upgrade to Jaunty. I have had a look at the control files in both Intrepid and Jaunty and it is not at all clear that they are asking for this behaviour at all.
Indeed, I have two clean Intrepid installs locally one on 32bit and one on 64 bit. On the 32bit install both lilo and grub are installed, on the 64bit install only grub is installed. According to the installer logs in /var/log/apt, it appears that they were both installed during the original install.
I am not sure why one has both and the other none, though I do note the problem install is also 32bit.