[Bug 958839] Re: Initrd/vmlinux symbloic links not in /boot directory on PowerPC
ojordan
958839 at bugs.launchpad.net
Sat Apr 14 19:54:44 UTC 2012
Going by an old 11.04 installation I have to hand, I would say the
problem lies in the /etc/kernel-img.conf file. It should read something
like this:
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
do_bootloader = no
do_initrd = yes
link_in_boot = yes
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to casper in Ubuntu.
https://bugs.launchpad.net/bugs/958839
Title:
Initrd/vmlinux symbloic links not in /boot directory on PowerPC
Status in “casper” package in Ubuntu:
New
Bug description:
Version: Casper 1.309
Ubuntu 12.04 Desktop ISO PowerPC
The symbolic links for initrd.img, initrd.img.old, vmlinux and
vmlinux.old are placed in the root directory of the squashfs
filesystem. These are then copied by ubiquity to the root partition
of the installed system. The initrd.img.old file also doesn't have
the correct permissions.
On previous CDs (for example 10.04) these files were placed in the
/boot directory of the squashfs filesystem.
When updating the installed system kernel the symbolic links on the
root partition are the ones that are updated, rather than in /boot
where yaboot looks. I don't know if something else also has to be
changed to correct this.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/958839/+subscriptions
More information about the foundations-bugs
mailing list