[Bug 52679] Re: link_in_boot not set correctly

Rolf Leggewie 52679 at bugs.launchpad.net
Mon Oct 3 01:43:27 UTC 2011


** Changed in: livecd-rootfs (Ubuntu Dapper)
       Status: In Progress => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/52679

Title:
  link_in_boot not set correctly

Status in “linux-source-2.6.15” package in Ubuntu:
  Invalid
Status in “livecd-rootfs” package in Ubuntu:
  Fix Released
Status in “linux-source-2.6.15” source package in Dapper:
  Invalid
Status in “livecd-rootfs” source package in Dapper:
  Won't Fix

Bug description:
  The Linux kernel upgrades for dapper quietly fail because they update
  the initrd.img and vmlinux symlinks in /, but not the ones in /boot
  which yaboot uses.  The result is that after reboot I'm still using
  the old (vulnerable) kernel.

  This copy of dapper was a fresh install just after dapper came out,
  and /etc/yaboot.conf hasn't been altered by hand - it always referred
  to /boot/initrd.img and /boot/vmlinux (and .old symlinks, which don't
  exist).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/52679/+subscriptions




More information about the foundations-bugs mailing list