Sheldon Knight wrote:
I have just built and successfully run a Redhat Linux 2.6.18.3 vserver
vs2.1.1.2 patched kernel and installed util-vserver-0.30.210 tools.
When I ran testme.sh I go the following output. What have I missed?
More specifically, how on earth did you manage to get this? I.e. what
commands did you use? Also, why did you go with an old version of the tools?
Use dietlibc: no (you have been warned)
You really should install dietlibc and use that.
Available APIs:
legacy,compat,v11,fscompat,v13obs,v13,net,oldproc,olduts
How did you manage to build the legacy API? I haven't been able to build
that for a while.
build/host: x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu
...
syscall(2) invocation: traditional
vserver(2) syscall#: 273/glibc
Well, this is wrong. First of all, you probably should use the
alternative or at least fast syscall invocation. Secondly, the syscall
number is 236 on x86_64. How you got these values is beyond me, only
thing I can think of is something like a mix of x86 and x86_64.
--
Daniel Hokka Zakrisson
GPG id: 06723412
GPG fingerprint: A455 4DF3 990A 431F FECA 7947 6136 DDA2 0672 3412
_______________________________________________
Vserver mailing list
[email protected]
http://list.linux-vserver.org/mailman/listinfo/vserver
