From: Christian Mayrhuber (christian.mayrhuber_at_gmx.net)
Date: Fri 01 Oct 2004 - 13:34:15 BST
On Friday 01 October 2004 13:23, Bjoern Steinbrink wrote:
> Hi Christian
> On Fr, 2004-10-01 at 12:18, Christian Mayrhuber wrote:
> > Hi,
> > I'm currently in trying out the experimental vs1.92 and
> > the new utils on debian.
> A lot of issues have been fixed since 1.9.2, currently there a 1.9.3-rc1
> patch that applies to 2.6.9-rc3.
The basic things should be working, no?
> > I've built a test vserver with the debootstrap method:
> > # vserver test build --netdev dummy0 --interface \
> > 192.168.1.1/24 -m debootstrap -- -d sarge
> > and tried to start it.
> > # vserver diglib start
> > Error: /proc must be mounted
> > To mount /proc at boot you need an /etc/fstab line like:
> > /proc /proc proc defaults
> > In the meantime, mount /proc /proc -t proc
> > Failed to parse ps-output
> > /usr/local/sbin/vserver: line 540: ip: command not found
> > /usr/local/sbin/vserver: line 542: ip: command not found
> > Starting system log daemon: syslogd.
> > Starting kernel log daemon: klogd.
> > Starting MTA: exim4.
> > Starting internet superserver: inetd.
> > Starting deferred execution scheduler: atd.
> > Starting periodic command scheduler: cron.
> > /proc is mounted of course.
vprocunhide did the trick.
I didn't know that the proc entries are hidden even ctx0.
Thanks, Bert De Vuyst,
iproute was missing.
The utils seem to work now.
Btw, "vserver test stop" shuts down
eth0, instead of just dummy0.
# cat /etc/vservers/test/interfaces/dev
Any ideas why this is happening?
I'll experiment a bit further.
-- lg, Chris _______________________________________________ Vserver mailing list Vserver_at_list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver