lubuntu-qa team mailing list archive

[Karl Anliot <kanliot@xxxxxxxxx>]

On Sat, Sep 15, 2012 at 2:15 AM, UH <uhtlmk@xxxxxxxxxxxxxx> wrote:
> 2012/9/14 Karl Anliot <kanliot@xxxxxxxxx>:
>> On Fri, Sep 14, 2012 at 3:29 PM, UH <uhtlmk@xxxxxxxxxxxxxx> wrote:
>>> I was away a long time (to gain a living doing outdoor - so no
>>> computer nothing . . .) but now, there is an "avalanche" of updates.
>>> And i notice, i'm still having the same problem when it comes to
>>> kernel updates like i published here:
>>>
>>> http://ubuntuforums.org/showthread.php?t=1918246&page=6
>>> (follow all about wrong placement of the symlinks vmlinux etc)
>>>
>>
>> That's a long thread.  What exactly is this regards to?  Please summarize.
>> cheers!
>
> Ok! When there is a kernel upgrade the symlink files (vmlinux,
> initrd.img and initrd.img.old) are placed to "/" and not to "/boot"
> (where they should be!).
>
> In addition: The vmlinux-x.x.x-xx-powerpc-smp has the wrong rights:
>
> Owner: root (correct)
> Group: root
> Rights
> Owner: read & write (correct)
> Group: nothing (wrong: should be read only)
> Others: nothing (wrong: should be read only) After correcting that (as
> root, obviously) boot into 3.2.0-17 works.
>
> This errors happen systematically with *ANY* kernel upgrade. As said
> before, i suspect this happens because of the script which might be
> taken from the i386 version which uses grub (and for grub the
> placement would be correct).
>
> But i'm wondering i'm nearly he only one encountering this problem
> (there was one confirmation in the thread -
> http://ubuntuforums.org/showpost.php?p=11722982&postcount=55 ).

yup i have some vmlinuz.old and initrd.img.old files sitting in /
I just assumed Linux Tovarlds put them there.