lubuntu-qa team mailing list archive

[UH <uhtlmk@xxxxxxxxxxxxxx>]

I checked around and i see this:

My lubuntu-disk is partitioned as follows:

sdc1: 32kb (Apple openrom) sdc2: bootstrap, sdc3: "/" (ext4), sdc4:
swap, sdc5 (8kb): extra

Now, on the top level of sdc3 i see there are 3 symlinks:

vmlinux (points to /boot/vmlinux-3.2.0-17-powerpc)
initrd.img (points to /boot/initrd.img-3.2.0-17-powerpc)
initrd.img.old (points to /boot/initrd.img-3.2.0-16-powerpc)

In the /boot directory there are all the 3.2.0-17 and 3.2.0-16 files
but also 2 symlinks (vmlinux and initrd.img which points to the
3.2.0-16 files).

Then i checked the /etc/yaboot.conf file. It looks like this (i didn't
touch it at all!):

--------------
## yaboot.conf generated by the Ubuntu installer
##
## run: "man yaboot.conf" for details. Do not make changes until you have!!
## see also: /usr/share/doc/yaboot/examples for example configurations.
##
## For a dual-boot menu, add one or more of:
## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ

boot="/dev/disk/by-id/ieee1394-0001a300000586c7:000428:0000-part2"
device=/pci@f4000000/firewire@e/node@0001a300000586c7/sbp-2/@0
partition=3
root="UUID=7393551e-1a0f-4461-8d87-82f4c75d8203"
timeout=50
install=/usr/lib/yaboot/yaboot
magicboot=/usr/lib/yaboot/ofboot
enablecdboot

image=/boot/vmlinux
	label=Linux
	read-only
	initrd=/boot/initrd.img
	append="quiet splash"

image=/boot/vmlinux.old
	label=old
	read-only
	initrd=/boot/initrd.img.old
	append="quiet splash"
--------------

So, it looks to me that, the update manager did something wrong: It
should have put the 3 files i now find on the top level into the /boot
directory and to rename the already existing symlinks to *.old. The
yaboot.conf file, which as far as i understand, commands the boot
procedure, doesn't look to the "/" directory but into /boot . . . Or
am i getting something wrong here?
. . .
Now, my question should/could i do this by hand - for the moment? Or
will i have to edit the yaboot.conf file?

But, in any case, in a funtional system it should work without bricolage, IMHO


2012/2/20 Ulrich Hausmann <uhausmann@xxxxxxxxxx>:
> Ok, i reinstalled the kernel metapackage and to be sure the 3.2.0-17,
> but even after a reboot 3.2.0-16 is loaded . . .
>
> 2012/2/20 Michael Rawson <michaelrawson76@xxxxxxxxx>:
>> Quick check: you have rebooted?
>>
>> Mine's working great...:L
>>
>> On Mon, 20 Feb 2012 18:20:58 +0100
>> UH <uhtlmk@xxxxxxxxxxxxxx> wrote:
>>
>>> I got by the update manager the above kernel but checking with the
>>> system profiler i see that the previous kernel (3.2.0-16) is still
>>> running. I also looked into /boot and saw that vmlinux is pointing to
>>> 3.2.0-16. Now, i'm afraid by the hassle to deal with yaboot and ybin,
>>> especially on an external (bootable) hd. But frankly, i do not
>>> understand, why the upgrade did not take place automatically . . . (?)
>>>
>>> TIA for any help!
>>>
>>> --
>>> Mailing list: https://launchpad.net/~lubuntu-qa
>>> Post to     : lubuntu-qa@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~lubuntu-qa
>>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>> --
>> Michael Rawson <michaelrawson76@xxxxxxxxx>
>>
>> --
>> Mailing list: https://launchpad.net/~lubuntu-qa
>> Post to     : lubuntu-qa@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~lubuntu-qa
>> More help   : https://help.launchpad.net/ListHelp