<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">2014-03-08 8:27 GMT+04:00 Kir Kolyshkin <span dir="ltr"><<a href="mailto:kir@openvz.org" target="_blank">kir@openvz.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><div class="">
<div>On 03/07/2014 06:21 PM, spameden wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>
<div>Btw, Kir, there is no version anymore in uname -a.<br>
<br>
Could you fix this at least to display current version, e.g.
instead of:<br>
<br>
# uname -r<br>
2.6.32-openvz-amd64<br>
<br>
</div>
display:<br>
# uname -r<br>
2.6.32-openvz-042stab084.17-amd64<br>
</div>
</div>
</blockquote>
<br></div>
Again, it is the same as in stock Debian kernel. While their version
is 3.2.54-2,<br>
uname shows 3.2.0-4.</div></blockquote><div><br></div><div>Partly true...<br><br>$ uname -a<br>Linux hostname 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux<br><br></div><div>as you can see there is actual version at the end..<br>
</div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000"><div class=""><br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div><br>
</div>
<div>and also consider reverting to the old system if you can..<br>
</div>
</div>
</blockquote>
<br>
<br></div>
Yeah, I guess I should do it, just waiting for someone who knows
Debian<br>
more than me to chime in.</div></blockquote><div><br></div><div>OK, thanks for the info. <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><div><div class="h5"><br>
<blockquote type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div><br>
</div>
</div>
</div>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">2014-03-07 18:45 GMT+04:00 Narcis
Garcia <span dir="ltr"><<a href="mailto:informatica@actiu.net" target="_blank">informatica@actiu.net</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I think that is a good strategy to have a main package to be
manually<br>
installed:<br>
linux-image-openvz-amd64<br>
linux-image-openvz-686<br>
<br>
But fully versioned as its dependencies (042stab084.26)<br>
And with a dependency to a version-named package, such as:<br>
linux-image-2.6.32-42.84.26-openvz-amd64<br>
<br>
In this way, upgrading the main package this will install
the new<br>
versions of dependencies. I think that this is the way
Debian works, and<br>
this allows to have old and new files installed
simultaneously.<br>
<br>
To have the old and new kernels allow to test new one before
removing<br>
old one.<br>
<br>
<br>
El 07/03/14 02:28, Kir Kolyshkin ha escrit:<br>
<div>> On 03/02/2014 02:01 PM, spameden wrote:<br>
>><br>
>><br>
>><br>
</div>
<div>>> 2014-03-03 0:38 GMT+04:00 Ola
Lundqvist <<a href="mailto:ola@inguza.com" target="_blank">ola@inguza.com</a><br>
</div>
>> <mailto:<a href="mailto:ola@inguza.com" target="_blank">ola@inguza.com</a>>>:<br>
<div>>><br>
>> Hi<br>
>><br>
>> Problem fixed now.<br>
>> I had fixed the problem temporarily, but I
had forgotten to<br>
>> upgrade to the debarchiver version with the
fix so it will not<br>
>> happen again. Now I have done the upgrade and
fixed the problem<br>
>> properly.<br>
>><br>
>><br>
>> I think it's not fixed properly:<br>
>><br>
>> 1) wrong version of linux-image:<br>
>> # dpkg -l|grep linux-image-openvz<br>
>> ii linux-image-openvz-amd64<br>
>> 042+1 amd64 OpenVZ
Linux kernel<br>
>> (meta-package)<br>
>><br>
>> 2) # ls /boot |grep openvz<br>
>> config-2.6.32-openvz-042stab084.17-amd64<br>
</div>
>> *config-2.6.32-openvz-amd64*<br>
>> initrd.img-2.6.32-openvz-042stab084.17-amd64<br>
>> *initrd.img-2.6.32-openvz-amd64*<br>
>> System.map-2.6.32-openvz-042stab084.17-amd64<br>
>> *System.map-2.6.32-openvz-amd64*<br>
>> vmlinuz-2.6.32-openvz-042stab084.17-amd64<br>
>> *vmlinuz-2.6.32-openvz-amd64*<br>
<div>>><br>
>> so now we are missing usual version here in the
package.. that's<br>
>> actually very bad ... can you look into it?<br>
>><br>
>> many thanks.<br>
><br>
</div>
<div>> This is intentional, and I changed it
after looking into how default<br>
> Debian kernel is packaged/versioned.<br>
><br>
> If you take a look, they have [meta]package
linux-image-amd64 which requires<br>
> package linux-image-3.2.0-4-amd64. The latter
(currently) has a version of<br>
> 3.2.54-2 and this version is changed (incremented)
with every release, while<br>
> package name stays the same
(linux-image-3.2.0-4-amd64). Also, vzkernel<br>
> name stays the same -- it is
/boot/vmlinuz-3.2.0-4-amd64 in different<br>
> versions.<br>
> I am using the very same approach now for OpenVZ
kernels.<br>
><br>
</div>
<div>> Previously I was adding the VZ version
(i.e. 042stab0xy.z) into kernel<br>
> package name,<br>
> and it was added to vmlinuz and the /lib/modules
directory name as well.<br>
</div>
<div>> The problem<br>
> is, you need to specify a different dependency in<br>
> linux-image-openvz-amd64 metapackage,<br>
> and apt-get upgrade complains that it can't upgrade
the system since a<br>
> new version<br>
> of an installed package (linux-image-amd64) requires
a package that is<br>
> not installed yet.<br>
> The problem could be fixed by running dist-upgrade,
but eventually I<br>
> decided that<br>
> this message is a hint that I package openvz kernels
improperly, that<br>
> lead me to<br>
> looking into a way standard Debian kernels are
packaged and implementing it<br>
> the same way for OpenVZ kernels.<br>
><br>
</div>
<div>> I am not a Debian guru and am very open
to suggestions on how to improve<br>
> this.<br>
> Perhaps we can return to the older versioning scheme
and ask people to<br>
> use dist-upgrade.<br>
> Or maybe I am totally missing something. Please help.<br>
><br>
</div>
> Kir.<br>
<div>
<div>><br>
><br>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@openvz.org" target="_blank">Users@openvz.org</a><br>
> <a href="https://lists.openvz.org/mailman/listinfo/users" target="_blank">https://lists.openvz.org/mailman/listinfo/users</a><br>
><br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@openvz.org" target="_blank">Users@openvz.org</a><br>
<a href="https://lists.openvz.org/mailman/listinfo/users" target="_blank">https://lists.openvz.org/mailman/listinfo/users</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Users mailing list
<a href="mailto:Users@openvz.org" target="_blank">Users@openvz.org</a>
<a href="https://lists.openvz.org/mailman/listinfo/users" target="_blank">https://lists.openvz.org/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@openvz.org">Users@openvz.org</a><br>
<a href="https://lists.openvz.org/mailman/listinfo/users" target="_blank">https://lists.openvz.org/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div></div>