# grep -i vroot /boot/config*-vserver*
/boot/config-2.6.16-2-vserver-686:CONFIG_BLK_DEV_VROOT=y
/boot/config-2.6.17-2-vserver-686:CONFIG_BLK_DEV_VROOT=y
/boot/config-2.6.18-3-vserver-686:# CONFIG_BLK_DEV_VROOT is not set
/boot/config-2.6.18-4-vserver-686:# CONFIG_BLK_DEV_VROOT is not set
Does anybody know, why it’s not compiled in since 2.6.18 anymore?
This article is based on the excellent article on 5dollarwhitebox.org.
At first install nessesary packages:
# aptitude -t sarge-backports install lvm2\
util-vserver coreutils linux-image-2.6-vserver-686
Since I started playing around with vserver there is the problem left restricting the capacity of the disk usage of the guests.
One solution may be to use one partition per vserver guest. But what to do if there is more (or less) space needed on the systems? Shutting them down and copying to bigger or smaller partition may not acceptable in any cases.
An other path can be LVM and (online-)resizeable filesystems.
If you want to use X11 forwarding through ssh you need to modify your /etc/ssh/ssh_config:
# echo “X11UseLocalhost no” > /etc/ssh/ssh_config
# /etc/init.d/ssh restart
Brunner Bäcker
Aldi
Städtischer Kinderspielplatz
Kindergarten Am Storchennest
Volksfestplatz Bayreuth
