Re: kernel security upgrade bollixed need help [solved]
On 20140513_0904+0200, Filip wrote:
> On Mon, 12 May 2014 20:34:37 -0600
> Paul E Condon <pecondon@mesanetworks.net> wrote:
>
> > I was responding to a recently received security message about the
> > linux kernel in Wheezy. I thought I had things configured so that the
> > repaired kernel would come from the security repository automagically,
> > but ...
> >
> > It did appear to be downloading a new kernel and installing it, but
> > when it finished nothing appeared to have been changed. I can't retry
> > because my system appears to have set flags that the upgrade has been
> > done. but there are no new files in /boot or updated symlinks in /.
> >
>
> I installed the security update last night.
> This is what it looks like (after reboot):
>
> $ ls -l / |grep boot
> drwxr-xr-x 3 root root 4096 May 12 16:53 boot
> lrwxrwxrwx 1 root root 30 Apr 5 12:37 initrd.img -> /boot/initrd.img-3.2.0-4-amd64
> lrwxrwxrwx 1 root root 26 Apr 5 12:37 vmlinuz -> boot/vmlinuz-3.2.0-4-amd64
> $ ls -l /boot
> total 15032
> -rw-r--r-- 1 root root 129206 May 12 11:42 config-3.2.0-4-amd64
> drwxr-xr-x 2 root root 4096 May 12 16:53 grub
> -rw-r--r-- 1 root root 10276510 May 12 16:53 initrd.img-3.2.0-4-amd64
> -rw-r--r-- 1 root root 2111641 May 12 11:42 System.map-3.2.0-4-amd64
> -rw-r--r-- 1 root root 2838176 May 12 11:42 vmlinuz-3.2.0-4-amd64
> $ strings /vmlinuz|grep deb7u1
> 3.2.0-4-amd64 (debian-kernel@lists.debian.org) #1 SMP Debian 3.2.57-3+deb7u1
>
> After reboot:
> $ uname -v
> #1 SMP Debian 3.2.57-3+deb7u1
>
This correlates well with what I see on my 686/pae machine. And, in
fact, the upgrade did happen correctly. The problem was that in my
memory. I recalled that the names of the files/symlinks, vmlinuz and
initrd.img were changed to reflect the versions of their new
contents. I think the naming was done differently, but now I know to
use uname -v and string to get at what is really contained in the
file. On reflection, the way it is being done now is better than what
I remember, so I'll stick with the new reality ;-)
Thanks for the new memories.
--
Paul E Condon
pecondon@mesanetworks.net
Reply to: