Amd64 (x86_64) kernels have the same name as ia32 (i386) kernels

[rew]

Binary package hint: linux-image-server

When 64-bit capable machines first appeared, installing a 64-bit userspace wasn't as attractive as it is now. Now is the time to switch (for me).

Because my system was upgraded from originally 32-bit machines, and I want to make sure I can still continue to work, should the 64-bit environment fail to work, I want to dualboot between the two systems in the transition period. (Just like I kept my old debian environment around for a while after installing Ubuntu).

The "boot" directory between the two systems needs to be shared. So I want to install the 64-bit kernel alongside the 32-bit kernel. However it turns out that this kernel's filename is exactly the same. It would be nice if in the future the 64-bit kernel would be named slightly different so that the filenames in /boot and the filenames in /lib/modules would not clash....

(I have a debian system that flawlessly runs a chrooted 64-bit ubuntu. But we upgraded the kernel to be 64-bit separately. This is something that requires running the 64-bit kernel with the 32-bit root, which requires the /lib/modules directory to be different.....)

Description: Ubuntu 9.04
Release: 9.04

linux-image-server:
  Installed: 2.6.28.11.15
  Candidate: 2.6.28.11.15
  Version table:
 *** 2.6.28.11.15 0
        500 http://nl.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

(This problem goes away automatically once 32-bit kernels start to be able to run 64-bit binaries. I'm not sure if this is going to happen soon).

[Andy Whitcroft (apw)]

This is not a bug in the linux-meta package, moving to the linux package.

[rew (r-e-wolff)]

FYI, the system that was affected by this now runs native x86_64 natty.

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in supported series, ple
ase file a new bug.