Public bug reported:
I have a separate /boot partition which is not mounted during normal
system use.
Recent kernel packages (don't know about older ones) apparently do not
check during installation whether there is a separate /boot partition
which is not mounted.
Hence on my system, those kernel packages install their stuff *in the
/boot directory on the root partition* instead of *on the /boot
partition*.
When rebooting, hilarity ensues.
To sum up:
Expected behaviour:
Before installation, kernel packages does:
if $(df -h|grep boot>/dev/null)
else
if $(grep boot /etc/fstab>/dev/null)
then
mount /boot
Real behaviour:
None of the above.
ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
HibernationDevice: RESUME=UUID=37f65803-b3b4-49b4-bd84-c7b44da4d77d
MachineType: Dell Inc. Latitude D630
NonfreeKernelModules: nvidia
Package: linux-image-2.6.28-15-generic 2.6.28-15.52
ProcCmdLine: root=UUID=b9d0249b-a34e-4090-ba89-1594e767df6f ro quiet splash
ProcEnviron:
LANG=en_DK.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-15.49-generic
SourcePackage: linux
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386
--
things are installed in wrong place because /boot is not mounted
https://bugs.launchpad.net/bugs/457957
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
