Activity log for bug #52679

Date Who What changed Old value New value Message
2006-07-11 19:22:01 Brian Campbell bug added bug
2006-07-11 20:08:54 Ben Collins linux-source-2.6.15: status Unconfirmed Rejected
2006-07-11 20:08:54 Ben Collins linux-source-2.6.15: statusexplanation Yeah, link_in_boot should be yes for your purposed. Perhaps something else changed it on your system without your knowledge, but nothing in dapper should have done that.
2006-07-11 20:13:12 Matt Zimmerman bug added subscriber Ubuntu Installer Team
2006-07-12 00:26:29 Colin Watson bug assigned to ubiquity (Ubuntu)
2006-07-12 00:29:12 Colin Watson ubiquity: status Unconfirmed Confirmed
2006-07-12 00:29:12 Colin Watson ubiquity: statusexplanation Matt: link_in_boot defaults to no on i386, so I'm not sure where you got your result from ... Brian: In installs from the alternate install CD, the initial /etc/kernel-img.conf is written by the base-installer component of the installer; it won't be owned by any package, as you observe. However, I've just checked and it seems that the live filesystem build script does not match the behaviour of base-installer; they default link_in_boot to no regardless of the architecture. Either ubiquity should fix this up, or the live filesystem build script should be fixed.
2006-07-12 00:29:33 Colin Watson bug added subscriber Adam Conrad
2006-09-16 07:46:55 Colin Watson ubiquity: importance Untriaged High
2006-09-16 07:46:55 Colin Watson ubiquity: statusexplanation Matt: link_in_boot defaults to no on i386, so I'm not sure where you got your result from ... Brian: In installs from the alternate install CD, the initial /etc/kernel-img.conf is written by the base-installer component of the installer; it won't be owned by any package, as you observe. However, I've just checked and it seems that the live filesystem build script does not match the behaviour of base-installer; they default link_in_boot to no regardless of the architecture. Either ubiquity should fix this up, or the live filesystem build script should be fixed.
2006-09-16 07:47:19 Colin Watson description Binary package hint: linux-image-2.6.15-26-powerpc 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). 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).
2006-09-16 07:47:19 Colin Watson title Linux upgrade doesn't update symlinks used by yaboot link_in_boot not set correctly
2006-10-05 08:54:47 Colin Watson ubiquity: status Confirmed In Progress
2007-07-23 13:47:36 Martin Pitt ubiquity: statusexplanation dapper 6.06.2 won't have new live CDs, moving back to dapper-updates
2008-02-28 17:43:09 Colin Watson linux-source-2.6.15: status New Invalid
2008-02-28 17:43:23 Colin Watson livecd-rootfs: importance Undecided High
2008-02-28 17:43:23 Colin Watson livecd-rootfs: status New In Progress
2008-02-28 17:43:23 Colin Watson livecd-rootfs: milestone dapper-updates
2008-02-28 17:44:07 Colin Watson livecd-rootfs: status In Progress Fix Released
2008-02-28 17:44:07 Colin Watson livecd-rootfs: milestone dapper-updates
2011-10-03 01:43:27 Rolf Leggewie livecd-rootfs (Ubuntu Dapper): status In Progress Won't Fix