History of VServerUtilitiesInstall

Note: There are different branches of the vserver utilities available. This chapter talks about the 'alpha' utilities, which support the most options and are the newest.

== Debian SID (a.k.a. Debian Unstable) ==

<code>

apt-get install util-vserver

</code>

== Fedora Core ==

TODO

== Mandriva ==

TODO

== Ubuntu ==

TODO

== Compilation from Source ==

This chapter has been taken from [Step-by-Step Guide 2.6], but with simplifications and little adaptions.

The kernel alone won't help you, you also need some tools to exploit all those new features you got, so let's get them. The latest tools can be found [here]. I'll use util-vserver 0.30.210 in this document, you should use whatever is latest.

=== Get the sources ===

As a first step, of course, we need to get the sources.

<code>

# Go to our source directory

cd ~/src

# Get the sources for alpha util-vserver

wget http://www.13thfloor.at/~ensc/util-vserver/files/alpha/util-vserver-0.30.210.tar.bz2

# Extract the sources

tar xjf util-vserver-0.30.210.tar.bz2

</code>

Now that we got our sources, we need to do the usual steps: configure, make, make install. While configuring the tools you may get some error messages about missing stuff, for example dietlibc, vconfig and e2fs headers. The error messages are accompanied by explanations what you should do, so read them carefully. You can also specify --without xalan or --without dietlibc as a workaround.

<code>

# Switch to the util-vserver source directory

cd util-vserver-0.30.210

# Configure the sources (you may want to adjust settings here, the defaults work, but may not suite your needs)

./configure

# Build the tools

make

# Become root

su

# Install the tools

make install

# Back to our regular user

exit

</code>

Now we got our tools in place and we're ready to build our first vserver!

=== Testing ===

Oh, wait, we're not ready yet! To be sure that your setup works fine, we got a test script that checks some basic functionality. So download the [testme.sh] script and check if everything's fine.

<code>

# Back to our source directory

cd ~/src

# Get the script

wget http://vserver.13thfloor.at/Stuff/SCRIPT/testme.sh

# Make it executable

chmod +x testme.sh

# Become root

su

# Run the test script

./testme.sh

# Back to our regular user

exit

</code>

---

This page is part of the VServerManual.