** Changed in: ubiquity (Ubuntu)
Importance: Untriaged => High
** Summary changed:
- Linux upgrade doesn't update symlinks used by yaboot
+ link_in_boot not set correctly
** Description changed:
- Binary package hint: linux-image-2.6.15-26-powerpc
-
The Linux kernel upgrades for dapper qu
I can confirm this behavior on a fresh install from a 6.06 Kubuntu PPC
CD. I installed, rebooted, set up the network, and did an upgrade,
nothing else (well, I set the color scheme for KDE), and yaboot.conf is
looking in /boot but /boot has the old symlinks.
I can provide the CD image if you'd li
Thus, this affects the desktop CD only. Adam, can you have a look at
fixing livefs.sh to be in sync with base-installer on this?
(Longer-term, we should move to "link_in_boot yes" on all architectures.
This is very likely to require modifications to some bootloader
installer scripts, and possibly
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,
On Tue, Jul 11, 2006 at 08:08:54PM -, Ben Collins wrote:
> 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.
What writes the initial /etc/kernel-img.conf? It doesn't app
On Tue, Jul 11, 2006 at 07:56:56PM -, Brian Campbell wrote:
> On Tue, Jul 11, 2006 at 07:41:55PM -, Matt Zimmerman wrote:
> >
> > What's in /etc/kernel-img.conf? Perhaps you edited it?
>
> do_symlinks = yes
> relative_links = yes
> do_bootloader = no
> do_bootfloppy = no
> do_i
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.
** Changed in: linux-source-2.6.15 (Ubuntu)
Status: Unconfirmed => Rejected
--
Linux upgrade doesn't update symlinks us
