Re: [Vserver] Host and guest compatability

From: Michael S. Zick <>
Date: Wed 09 Aug 2006 - 15:58:26 BST
Message-Id: <>

On Wed August 9 2006 09:30, Jim Wight wrote:
> On Wed, 2006-08-09 at 08:50 -0500, Michael S. Zick wrote:
> > Since the chroot command does not change the context (or namespace) then
> > it must be the act of trying to run in a different context that breaks
> > something.
> >
> > My guess, the dynamic library handling.
> >
> > Try executing /lib/ in the guest context, see if you get a
> > normal report out of it. It should print its build information,
> > including its version.
> What command is required to accomplish that?

The file is an executable.

Just substitute "/lib/" for where you are using "/usr/bin/env"
in your testing.

Or build your own command out of the low level tools, similar too:

chbind --ip ${VADDRESS} -- vcontext --create --xid ${VID} --chroot -- \
/usr/bin/env -i HOSTNAME=${VROOT} HOME=/root TERM="${TERM}" PS1='\u:\w\$ ' \
PATH='/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin' /bin/bash --login +h

I use the above to give myself a command shell inside a vserver context without
"starting" the vserver - the above is independent of the vserver config files.

(Note the "+h" on the Bash command - you need to make Bash drop its path hashing

Vserver mailing list
Received on Wed Aug 9 15:58:58 2006

[Next/Previous Months] [Main vserver Project Homepage] [Howto Subscribe/Unsubscribe] [Paul Sladen's vserver stuff]
Generated on Wed 09 Aug 2006 - 15:59:03 BST by hypermail 2.1.8