From: ROBERT LASSFOLK/ DC (Rlassfol_at_yrkes.syi.fi)
Date: Thu 22 Nov 2001 - 07:14:59 GMT
i'm at school right now so i can't check the command
/sbin/chbind --ip 184.108.40.206 /bin/sh
but i got vserver working late last night by first entering it and put
some service to start from rc.local.
then i exited the server and started it and it worked. got no errors in
messages and it started the service.
if i don't start anything in the server, the kernel starts printing the
modprobe problem to messages.
another thing i noticed was that if i make a service start via the setup
command in redhat and then try to start the server, it doesn't start
the service. when i enter it and check setup the service is disabled
i was wondering if if i have to use dnat to get the firewall to portfw the
service in to the vserver, or can i just point the workstation at the
vserver ip addr?
my fingers are itching to get home and continue fiddling with vserver.
i got to say that this is one of the coolest things i found on linux yet.
thanks for great software...