Hello Community,
i have installed all the wonderfull new things, like vserver 1.2.1 and
vserver tools 0.29. all working well... But the new VServer tools cause a
fault in order newvserver:
-
vm-dev1:~# newvserver
bash: /usr/sbin/newvserver: /usr/bin/shellmod: bad interpreter: No such file
or
On Sat, Dec 13, 2003 at 03:15:45PM +0100, Kern Wolfgang wrote:
Hello Community,
i have installed all the wonderfull new things, like vserver 1.2.1 and
vserver tools 0.29. all working well... But the new VServer tools cause a
fault in order newvserver:
-
vm-dev1:~# newvserver
bash:
Thanks for this info, herbert ;)
Regards
Kern Wolfgang
-Ursprüngliche Nachricht-
Von: Herbert Poetzl [mailto:[EMAIL PROTECTED]
Gesendet: Samstag, 13. Dezember 2003 15:27
An: Kern Wolfgang
Cc: [EMAIL PROTECTED]
Betreff: Re: [Vserver] Error in newvserver
On Sat, Dec 13, 2003 at
[EMAIL PROTECTED] (Bodo Eggert) writes:
dietlibc doesn't define uint64_t if __STRICT_ANSI__ is set, and
-std=c99 defines __STRICT_ANSI__.
Reported several times to [EMAIL PROTECTED] but not fixed yet :(
Btw, same happens with 'inline'.
To compile it, I had to add -U __STRICT_ANSI__ after
On Fri, Dec 12, 2003 at 08:10:09PM +, Jonathan Sambrook wrote:
Hi Jonathan!
I totally agree that uts_sem isn't the apropriate
to use in this place(s), but I don't see how this
could cause a deadlock/panic as there is nothing
to lock/panic if the rw sem is held for write ...
Hello Community!
another bugfix release of the second linux-vserver
stable release (1.22) is available at
http://www.13thfloor.at/vserver/s_release/v1.22/
you can download all-in-one patches for 2.4.21/22
and 2.4.23 as well as tar archives of all the
splitups ...
this release fixes a