Re: Need help understanding kernel version numbers [message #11905 is a reply to message #11903] |
Wed, 11 April 2007 10:25 ![Go to previous message Go to previous message](/theme/ovz3/images/up.png) ![Go to next message Go to previous message](/theme/ovz3/images/down.png) |
jarcher
Messages: 91 Registered: August 2006 Location: Smithfield, Rhode Island
|
Member |
|
|
Ah, thanks very much Thorsten, I see how it works now. Is there a way to
tell from the version number if a deb file has a test kernel or a stable
one?
--On Wednesday, April 11, 2007 11:44 AM +0200 Thorsten Schifferdecker
<tsd@debian.systs.org> wrote:
> Hi Jim,
>
> Ola has updated the debianized OpenVZ Linux kernel to new Debian Linux
> Kernel Source :
>
> " linux-image-2.6.18-openvz-amd64_028.18-2.6.18-12-1_amd64.deb " :
>
> linux-image-2.6.18-openvz-amd64 ...
>
> 028.18.1
> \_> OpenVZ Kernel Patch 028test018.1
> (-> http://packages.debian.org/stable/devel/kernel-patch-openvz )
>
> 2.6.18-12-1
> \_> Debian Linux Kernel Source
> (-> http://packages.debian.org/stable/devel/linux-source-2.6.18)
>
> Regards,
> Thorsten
>
> Jim Archer schrieb:
>> Hi All...
>>
>> I have always been confused by the kernel version numbers and I finally
>> decided to just look stupid and ask.
>>
>> I am currently running:
>>
>> actual:/home/jim/openvz/kernels# uname -a
>> Linux actual.registrationtek.com 2.6.18-openvz-amd64 #1 SMP Mon Mar 12
>> 21:59:13 UTC 2007 x86_64 GNU/Linux
>> actual:/home/jim/openvz/kernels#
>>
>>
>> The file name for the deb package for this version is:
>>
>> linux-image-2.6.18-openvz-amd64_028.18-2.6.18-11-1_amd64.deb
>>
>> I see that there is now:
>>
>> linux-image-2.6.18-openvz-amd64_028.18.1-2.6.18-12-1_amd64.d eb
>>
>>
>> This file has a date of April 11, 2007, so I know it's newer. But how
>> can I tell from the version numbers? Both are 028.18 but the newer one
>> has a lower number, .1-2, than the older one, which has 6. So what's
>> the proper way to parse this?
>>
>> Also, is there a posted list of changes? I'm running OpenVZ in
>> production now and so prefer not to risk an upgrade and reboot unless
>> necessary.
>>
>> Thanks!
>>
>> Jim
>>
|
|
|