On Wed, May 21, 2008 at 11:42:47AM +0200, Olivier Berger wrote: > It seems that the linux-image-2.6.22-3-vserver-686 contains patch version > 2.2.0.5 (see #482177), which should have included the fix for your problem. > > So I guess that Bastian was right in closing the bug.
According to the changelog, package version 2.6.22-5 did contain patch version 2.2.0.4 (and I'm quite sure it was the bad one of the two releases called 2.2.0.4). So closing the bug on Nov 2 was wrong. But on Nov 4, package version 2.6.22-6 was released, which contained vserver patch version 2.2.0.5. That should have finally fixed the bug indeed. So, as far as I can tell, the report can be closed for version 2.6.22-6 and later. Regards, Jan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
