Re: [cobalt-users] [Qube3] Cobalt Qube3 Kernel v7.0 update

[Mike Kelley <mkelley@xxxxxxxxx>]

At 08:55 AM 01/03/2003 +0000, you wrote:
><SNIP>
>> >Linux version 2.2.16C33_III+VPN (root@xxxxxxxxxxxxxxxxxxx)
>
>> Did you verify the MD5 checksum? From
>> http://sunsolve.sun.com/patches/cobalt/qube3.eng.html the last kernel
>> update Qube3-All-Kernel-4.0.1-2.2.16C33-III+VPN-1.pkg was posted 2002-11-07
>> with a MD5 Check Sum: c46b934a5c2f9e1a7505f67eb92b58aa
></snip>
>
>Hi Mike,
>
>Good thinking, however I let bluelineq do all the work, so i didn't
see/touch 
>the pkg file myself, so I was worried i'd had a dns poison attack or 
>something along those lines.
>
>Can any other Qube3 owners do:
>
>cat /proc/version
>
>for me, and tell me what their kernel reports as. If they're all the same
then 
>i'm not too worried really!
>
>Regards,
>Andy
>http://www.raqpak.com/
>
>
>_____________________________________
>cobalt-users mailing list
>cobalt-users@xxxxxxxxxxxxxxx
>To subscribe/unsubscribe, or to SEARCH THE ARCHIVES, go to:
>http://list.cobalt.com/mailman/listinfo/cobalt-users
>
Andy, 

(This old kernel)
cat /proc/version
Linux version 2.2.16C32_III+VPN (root@xxxxxxxxxxxxxx) (gcc version
egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Fri Nov 9 23:43:07 PST
2001

I use a "notification only" Bluelinq process so I can go onsite for the
kernel updates. YMMV but the packages are in /home/packages on this Qube.
Also, I vaguely remember a thread on a cobalt list that Bluelinq refuses to
install an improperly signed package.  ...processing...  In fact you can
set this feature in the Bluelinq -> settings -> advanced tab and feel
confident that only signed packages will be installed on your Qube. HTH
Mike Kelley
Standard and non-standard disclaimers apply