Re: [Vserver] Vserver newbie question

2005-09-14 Thread [eMAXX] Sys-Admin 

[eMAXX] Sys-Admin wrote:



Anyway, I found out that these packages are the best way to get my 
vserver running :)



That shoud be:"Are NOT the best way   "

Vince.
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver

Re: [Vserver] Vserver newbie question

2005-09-14 Thread [eMAXX] Sys-Admin 

Daniel Hokka Zakrisson wrote:




Sounds like fix01 was used rather than fix02.


I wouldn't know, since I used precompiled debianpackages: 
http://linux-vserver.derjohn.de/
But "util-vserver (0.30.208-1)" in 
http://linux-vserver.derjohn.de/util-vserver_0.30.208-1_i386.changes 
suggest fix01


Anyway, I found out that these packages are the best way to get my 
vserver running :)


Back to the struggle ...

Regards,

Vincent Pluk
eMAXX, Netherlands
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver

Re: [Vserver] Vserver newbie question

2005-09-14 Thread Daniel Hokka Zakrisson 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

[eMAXX] Sys-Admin wrote:
| I search the irc-log and then tried this:
|~# /usr/lib/util-vserver/vprocunhide/proc/net/: Bad address
|/proc/sys/: Bad address
|/proc/sys/debug/: Bad address
|/proc/sys/dev/: Bad address
|/proc/sysvipc/: Bad address
|/proc/tty/: Bad address
|/proc/cmdline: Bad address
|/proc/cpuinfo: Bad address
|/proc/crypto: Bad address
|/proc/devices: Bad address
|/proc/execdomains: Bad address
|/proc/filesystems: Bad address
|/proc/interrupts: Bad address
|/proc/iomem: Bad address
|/proc/ioports: Bad address
|/proc/kcore: Bad address
|/proc/kmsg: Bad address
|/proc/loadavg: Bad address
|/proc/locks: Bad address
|/proc/meminfo: Bad address
|/proc/misc: Bad address
|/proc/modules: Bad address
|/proc/pci: Bad address
|/proc/slabinfo: Bad address
|/proc/stat: Bad address
|/proc/swaps: Bad address
|/proc/uptime: Bad address
|/proc/version: Bad address

Sounds like fix01 was used rather than fix02.

- --
Daniel Hokka Zakrisson
GPG id: 06723412
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFDKAuUYTbdogZyNBIRAkp/AJ47IHsrFJmux4ivDRPsTwesNXzrxQCfQaG2
a46a4k1uN9c3jGAZL+YjfgU=
=UMIl
-END PGP SIGNATURE-

___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver

Re: [Vserver] Vserver newbie question

2005-09-13 Thread Xavier Montagutelli 
On Tuesday 13 September 2005 22:32, [eMAXX] Sys-Admin wrote:
> Hi folks,
>
> Ok, I'm totally lost. I don't seem to get a vserver install to work...
> well at least not the latest version..

I am also a newbie, and I have done it with Debian recently, so let's see 
what's different.

> I'm trying to install vserver from this source:
> http://linux-vserver.derjohn.de/ on Debian Sarge. I written down the
> steps I took for this vserver installation:
[..]
> --
> [1] Wget:
>
> http://linux-vserver.derjohn.de/kernel-image-2.6.12-p3_10.00.vserver20_i386
>.deb http://linux-vserver.derjohn.de/util-vserver_0.30.208-1_i386.deb

I have used the sources from Linus 2.6.12.4 :

wget ftp://ftp.kernel.org/pub/linux/kernel/v2.6/linux-2.6.12.4.tar.bz2
wget http://www.13thfloor.at/vserver/s_rel26/v2.0/patch-2.6.12.4-vs2.0.diff

make menuconfig
more /boot/config-2.6.12.4-vs2.0-scivm-xm2
#
# Block devices
#
# CONFIG_BLK_DEV_VROOT is not set
#
# Kernel hacking
#
CONFIG_VSERVER=y
CONFIG_VSERVER_SECURITY=y
CONFIG_VSERVER_LEGACYNET=y
#
# Linux VServer
#
CONFIG_VSERVER_LEGACY=y
# CONFIG_VSERVER_LEGACY_VERSION is not set
# CONFIG_VSERVER_NGNET is not set
CONFIG_VSERVER_PROC_SECURE=y
CONFIG_VSERVER_HARDCPU=y
# CONFIG_VSERVER_HARDCPU_IDLE is not set
# CONFIG_INOXID_NONE is not set
# CONFIG_INOXID_UID16 is not set
# CONFIG_INOXID_GID16 is not set
CONFIG_INOXID_UGID24=y
# CONFIG_INOXID_INTERN is not set
# CONFIG_INOXID_RUNTIME is not set
# CONFIG_XID_TAG_NFSD is not set
# CONFIG_VSERVER_DEBUG is not set

make-kpkg 

>
> [2] Install new kernel:
> ~# dpkg -i kernel-image-2.6.12-p3_10.00.vserver20_i386.deb
>
> [2a] Update /boot/grub/menu.lst to change the label so it contains "vs"
> ~# nano /boot/grub/menu.lst
>
> [3] Reboot...
>
> ---
>
> [4] Install Util-Vserver:
> ~# dpkg -i util-vserver_0.30.208-1_i386.deb

I used the sources :

wget 
http://www.13thfloor.at/vserver/s_rel26/v2.0/util-vserver-0.30.208.tar.bz2

apt-get install vlan iproute e2fslibs-dev
apt-get install dietlibc-dev beecrypt2-dev
./configure --sysconfdir=/etc --localstatedir=/var
make && make install && make install-distribution

mkdir -p /var/lock/subsys
update-rc.d vprocunhide start 74 0 2 .
update-rc.d rebootmgr start 98 2 . stop 02 0 6 .
update-rc.d vservers-default start 98 2 . stop 02 0 6 .

> [5] download and run the testscript:
> ~# wget http://vserver.13thfloor.at/Stuff/SCRIPT/testme.sh
[..]
>
> [6] So, vserver 2.0 and vserver-util should be running now:
> ~# vserver-info
[..]
> Paths:
>prefix: /usr
> sysconf-Directory: ${prefix}/etc
> cfg-Directory: ${prefix}/etc/vservers
>  initrd-Directory: $(sysconfdir)/init.d
>pkgstate-Directory: ${prefix}/var/run/vservers

these paths seems strange : under Debian, the sysconf-Directory should be /etc 
instead of /usr/etc, cfg-Direfctory should be /etc/vservers instead 
of /usr/etc/vservers, etc.

> [7] Create Vserver basedir since the default location isn't there:
> ~# mkdir /vservers

"make install-distribution" makes it for you if you compile the userland 
tools. Perhaps you forgot to "setattr --barrier /vservers" during this step ? 

> ~# mkdir /vservers/vstest01

not necessary. The next step (vserver .. build) should do it for you.

>
> [8] Create new Context/Virtual Server:
> ~# vserver vstest01 build -m debootstrap --hostname vstest01
> --netdev eth0:vs01 --interface 192.168.27.33 --context 42 -- -d sarge -m
> ftp://ftp.nl.debian.org/debian/
>
> [9] /proc/sys/kernel/vshelper contains: /sbin/vshelper, must be updated:
> ~# echo "/usr/lib/util-vserver/vshelper" >/proc/sys/kernel/vshelper

"make install-distribution" makes the link under /sbin

In your case, you could also put it in the /etc/sysctl.conf file (to make it 
persistent across reboots) :

kernel.vshelper = /usr/lib/util-vserver/vshelper

>
> [10] Then Vserver should run?
> ~# vserver vstest01 start
> /proc/uptime can not be accessed. Usually, this is caused by
> procfs-security. Please read the FAQ for more details
> http://www.linux-vserver.org/index.php?page=Linux-Vserver+FAQ

That's normal (from what I have understood) : the default is that everything 
is protected, you have to unlock things under /proc

> I search the irc-log and then tried this:
> ~# /usr/lib/util-vserver/vprocunhide

Normally, this script is called by /etc/init.d/vprocunhide during the boot 
process of the host system (if your Debian package configures it correctly). 
The files to "unhide" are listed 
in /usr/lib/util-vserver/defaults/vprocunhide-files (or 
in /etc/vservers/.defaults/apps/vprocunhide/files if that file exists)

> /proc/net/: Bad address
[.. every file to unhide with an error ..]
> I have no clue what this means anyone?

I don't have any idea about that. Do you use devfs ? On my machine, there's no 
devfs.

You could also try some basic commands :

cat /pro

[Vserver] Vserver newbie question

2005-09-13 Thread [eMAXX] Sys-Admin 

Hi folks,

Ok, I'm totally lost. I don't seem to get a vserver install to work... 
well at least not the latest version..


I'm trying to install vserver from this source: 
http://linux-vserver.derjohn.de/ on Debian Sarge. I written down the 
steps I took for this vserver installation:


-
Vserver 2.0 Installation on Debian Sarge current running 2.6.8 kernel

Used info:
- http://linux-vserver.org/Step-by-Step+Guide+2.6

Used sources:
- http://linux-vserver.derjohn.de/
- http://vserver.13thfloor.at/Stuff/SCRIPT/testme.sh

--
[1] Wget:
   
http://linux-vserver.derjohn.de/kernel-image-2.6.12-p3_10.00.vserver20_i386.deb

   http://linux-vserver.derjohn.de/util-vserver_0.30.208-1_i386.deb
  
[2] Install new kernel:

   ~# dpkg -i kernel-image-2.6.12-p3_10.00.vserver20_i386.deb
  
[2a] Update /boot/grub/menu.lst to change the label so it contains "vs"

   ~# nano /boot/grub/menu.lst
  
[3] Reboot...


---

[4] Install Util-Vserver:
   ~# dpkg -i util-vserver_0.30.208-1_i386.deb
  
[5] download and run the testscript:
   ~# wget http://vserver.13thfloor.at/Stuff/SCRIPT/testme.sh


   ~# chmod +x testme.sh
   ~# ./testme.sh

   Output of the test script::
  
   Linux-VServer Test [V0.13] Copyright (C) 2003-2005 H.Poetzl

   chcontext is working.
   chbind is working.
   Linux 2.6.12-p3 i686/0.30.208/0.30.208 [Ea] (0)
   VCI:  0002:0001 273 0376
   ---
   [000]# succeeded.
   [001]# succeeded.
   [011]# succeeded.
   [031]# succeeded.
   [101]# succeeded.
   [102]# succeeded.
   [201]# succeeded.
   [202]# succeeded.   


[6] So, vserver 2.0 and vserver-util should be running now:
   ~# vserver-info
   Versions:
  Kernel: 2.6.12-p3
  VS-API: 0x00020001
util-vserver: 0.30.208; Aug 12 2005, 01:59:02
  
   Features:
  CC: i486-linux-gnu-gcc, 
i486-linux-gnu-gcc (GCC) 4.0.2 20050725 (prerelease) (Debian 4.0.1-3)
 CXX: i486-linux-gnu-g++, 
i486-linux-gnu-g++ (GCC) 4.0.2 20050725 (prerelease) (Debian 4.0.1-3)

CPPFLAGS: ''
  CFLAGS: '-Wall -g -O2 -std=c99 -Wall 
-pedantic -W -funit-at-a-time'
CXXFLAGS: '-g -O2 -ansi -Wall -pedantic -W 
-fmessage-length=0 -funit-at-a-time'

  build/host: i486-pc-linux-gnu/i486-pc-linux-gnu
Use dietlibc: yes
  Build C++ programs: yes
  Build C99 programs: yes
  Available APIs: 
compat,v11,v13,fscompat,net,oldproc,olduts

   ext2fs Source: e2fsprogs
   syscall(2) invocation: alternative
 vserver(2) syscall#: 273/glibc
  
   Paths:

  prefix: /usr
   sysconf-Directory: ${prefix}/etc
   cfg-Directory: ${prefix}/etc/vservers
initrd-Directory: $(sysconfdir)/init.d
  pkgstate-Directory: ${prefix}/var/run/vservers
   Kernelheaders: 
/lib/modules/2.6.11.john-win4lin-1-ath64/build/include

 vserver-Rootdir: /vservers
  
  


---

[7] Create Vserver basedir since the default location isn't there:
   ~# mkdir /vservers
   ~# mkdir /vservers/vstest01

[8] Create new Context/Virtual Server:   
   ~# vserver vstest01 build -m debootstrap --hostname vstest01 
--netdev eth0:vs01 --interface 192.168.27.33 --context 42 -- -d sarge -m 
ftp://ftp.nl.debian.org/debian/
  
[9] /proc/sys/kernel/vshelper contains: /sbin/vshelper, must be updated:

   ~# echo "/usr/lib/util-vserver/vshelper" >/proc/sys/kernel/vshelper

[10] Then Vserver should run?
   ~# vserver vstest01 start
   /proc/uptime can not be accessed. Usually, this is caused by

   procfs-security. Please read the FAQ for more details
   http://www.linux-vserver.org/index.php?page=Linux-Vserver+FAQ



I search the irc-log and then tried this:
   ~# /usr/lib/util-vserver/vprocunhide 
   /proc/net/: Bad address

   /proc/sys/: Bad address
   /proc/sys/debug/: Bad address
   /proc/sys/dev/: Bad address
   /proc/sysvipc/: Bad address
   /proc/tty/: Bad address
   /proc/cmdline: Bad address
   /proc/cpuinfo: Bad address
   /proc/crypto: Bad address
   /proc/devices: Bad address
   /proc/execdomains: Bad address
   /proc/filesystems: Bad address
   /proc/interrupts: Bad address
   /proc/iomem: Bad address
   /proc/ioports: Bad address
   /proc/kcore: Bad address
   /proc/kmsg: Bad address
   /proc/loadavg: Bad address
   /proc/locks: Bad address
   /proc/meminfo: Bad address
   /proc/misc: Bad address
   /proc/modules: Bad address
   /proc/pci: Bad address
   /proc/slabinfo: Bad address
   /proc/stat: Bad address
   /proc/swaps: Bad address
   /proc/uptime: Bad address
   /proc/version: Bad address

I have no clue what this means anyone?

Regards,

Vincent Pluk
eMAXX, Neth