PLDWWW: Vserver

[hawk]

Author: hawk   Date: Thu Nov 15 21:13:58 2007 GMT
Module: PLDWWW   URL: http://www.pld-linux.org/Vserver?action=diff&rev2=96&rev1=95
---- Log message:


---- Page affected: Vserver

---- Diffs:

================================================================
  source src { unix-stream("/dev/log"); internal(); };
  }}}
  
- === running openvpn inside vserver ===
+ === Running openvpn inside vserver ===
  
  * you need to create ''/dev/net/tun'':
  {{{
@@ -355, +355 @@

  # echo CAP_NET_ADMIN >> /etc/vservers/test/bcapabilities
  }}}
  
- === can't use ssh xauth forwarding ===
+ === Can't use ssh xauth forwarding ===
  
  workaround: disable {{{X11UseLocalhost}}} in {{{sshd_config}}}
  
@@ -369, +369 @@

  
  or in .defaults (to disable for all guests).
  
- === not enough space on /tmp ===
+ === Not enough space on /tmp ===
  
  Just after installation in each vserver 16MB RAM-based filesystem is mounted in /tmp. If you want your /tmp filesystem to be bigger, reside on diffrent device or not be mounted at all see {{{/etc/vservers/test/fstab}}}.
  
- === disabling interface ===
+ === Disabling interface ===
  it's very convenient to disable some interface so it won't be activated on vserver boot
  {{{
  # touch /etc/vservers/test/interfaces/0/disabled
  }}}
  
- === display mounts of each xid (vserver) ===
+ === Display mounts of each xid (vserver) ===
  {{{
  for a in /proc/virtual/[0-9]*; do \
   xid=$(basename $a /); \
@@ -409, +409 @@

  
  Install {{{util-vserver-init}}} package, read and edit {{{/etc/sysconfig/vservers}}}.
  
- === vservers startup order ===
+ === Vservers startup order ===
  Sometimes it may happen that you need to be sure that one of the vservers is started before the others - e.g. it provides some service that other depend on. Vserver provides an easy way to do this - let's assume that ''test2'' vserver depends on ''test'' and ''foo'' vservers:
  {{{
  # echo test >> /etc/vservers/test2/apps/init/depends 
@@ -455, +455 @@

  }}}
  
  
+ === Vserver guest on physical console ===
+ 
+ If you wish to have your guest vserver available on physical console, lets say, {{{/dev/tty2}}} do following:
+  * comment out tty2 in {{{/etc/inittab}}} on host machine
+ 
+ {{{
+ #2:2345:respawn:/sbin/mingetty tty2
+ }}}
+ 
+  * copy /dev/tty2 from host machine as /vservers/name/dev/tty2
+  * comment out all ttys in /vservers/etc/inittab except tty2, it is good idea to comment all ttys anyway to suppress errors like
+ 
+ {{{
+ INIT: Id "1" respawning too fast: disabled for 5 minutes
+ }}}
+ 
+  * press ALT+F2 and login to your guest vserver :)
+ 
+ 
- === running 32 bit vserver on an 64 bit host ===
+ === Running 32 bit vserver on an 64 bit host ===
  
  With recent PLD util-vserver package you can setup it by using one of commands below:
  {{{
@@ -473, +492 @@

  }}}
  
  
- === package built for different operating system (linux) ===
+ === Package built for different operating system (linux) ===
  
  When setting up vservers on Th with recent poldek one might run into an error with message:
  {{{
@@ -488, +507 @@

  
  or by upgrading to util-vserver-0.30.213-5 or later (th versions).
  
- === can't upgrade FHS package ===
+ === Can't upgrade FHS package ===
  
  You will be most likely get error like:
  {{{