From: Jacques Gelinas (jack_at_solucorp.qc.ca)
Date: Fri 01 Mar 2002 - 02:19:59 GMT
vserver 0.13
Change log
1. Bug fixes
1.1. Dynamic system call number, a glitch
Since vserver 0.11, the vserver utility are able to probe the kernel
to find the number of the system calls new_s_context and set_ipv4root.
The same binaries may be used with different kernels (where the new
system calls have different numbers).
This was done because the two system calls are not official( reserved
in the official kernel) and probably won't be until we have covered
more grounds...
vserver-0.12 uncovered a flaw where the file /proc/self/status was not
properly parsed. But there was another gotcha. When used with an older
kernel (older than 2.4.17ctx-8), the utility were using the values in
/usr/include/asm/unistd.h. Unfortunately, those values are dependent
on the kernel currently installed on your computer. If it is a 2.4.18
kernel, the system calls have different number than on older 2.4.17
kernel.
To make the story short, the vserver-0.13 utilities are not relying
on kernel headers for their default, so work with older kernel as well
as the new 2.4.17ctx-8 or 2.4.18ctx-8. They have been tested on
2.4.17ctx-6. Please upgrade.
---------------------------------------------------------
Jacques Gelinas <jack_at_solucorp.qc.ca>
vserver: run general purpose virtual servers on one box, full speed!
http://www.solucorp.qc.ca/miscprj/s_context.hc