Re: [Vserver] VServer seems to work fine basicaly on hppa too -) (just some question)
On Fri, Dec 16, 2005 at 02:55:34PM +0100, Joel Soete wrote: Hello Herbert, [123]# succeeded. verify /mnt/test/file_3053: -+(-)-i-+(-) ~ i---E [124]# failed. this is caused by the legacy kernel API support ... if enabled it will blend through the iunlink as flag 'E' on reiserfs (still investigating if that is a bug, or if some tools really used that one ...) best, Herbert ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] VServer seems to work fine basicaly on hppa too -) (just some question)
[...] testme works fine: # ./testme.sh-0.14 -v Linux-VServer Test [V0.14] Copyright (C) 2003-2005 H.Poetzl chcontext is working. chbind is working. chcontext 0.30.209 -- allocates/enters a security context This program is part of util-vserver 0.30.209 Copyright (C) 2004 Enrico Scholz This program is free software; you may redistribute it under the terms of the GNU General Public License. This program has absolutely no warranty. Linux 2.6.14.3-vs2.1.0-rc10-pa0-d32up parisc/0.30.209/0.30.209 [Ea] (0) VCI: 0002:0001 263 03000116 ([EMAIL PROTECTED]) (gcc version 4.0.3 20051201 (prerelease) (Debian 4.0.2-5)) #2 Wed Dec 7 12:07:47 CET 2005 --- [000]# chcontext true chcontext --ctx 45678 true [000]# succeeded. [001]# chcontext --ctx 45678 egrep 'context|VxID' /proc/self/status [001]# succeeded. [011]# chcontext --secure --ctx 45678 mknod /tmp/testme.sh-0.14.x4zqUF/node c 0 0 [011]# succeeded. [031]# chcontext --hostname zaphod.21379 uname -a | grep -q zaphod.21379 [031]# succeeded. [101]# chbind --ip 192.168.0.42 true [101]# succeeded. [102]# chbind --ip 192.168.0.1/255.255.255.0 --ip 10.0.0.1/24 true [102]# succeeded. [201]# chcontext --ctx 45678 --flag fakeinit bash -c 'test $$ -eq 1' [201]# succeeded. [202]# chcontext --flag fakeinit bash -c 'test $$ -eq 1' [202]# succeeded. OTC testfs.sh-0.11 failed after a return (no messaged)? I have a quick look and testfs -v -F ext2 (help example) launch mkfs.ext2 /dev/zero manualy this cmdl is querying: mke2fs 1.38 (30-Jun-2005) /dev/zero is not a block special device. Proceed anyway? (y,n) though. (please exaplain me what is it supposed to do and detect as pb?) check testfs.sh -h and you will find that you can specify a device, which will be used to create various filesystems on, and verify the different aspects of attributes, barrier and xid tagging because those tests are destructive, the default is the /dev/zero device, which will not work :) Yes cool ;-) something like this is supposed to work, given that you have support for the filesystems: dd if=/dev/zero of=/var/tmp/200MB.img bs=1M count=200 losetup /dev/loop0 /var/tmp/200MB.img mkdir /mnt/test testfs.sh -D /dev/loop0 -M /mnt/test -x mmm not 'supposed' any more: that works ;-) # ./testfs.sh-0.11 -D /dev/loop0 -M /mnt/test -x Linux-VServer FS Test [V0.10] Copyright (C) 2005 H.Poetzl Linux 2.6.14.3-vs2.1.0-rc10-pa0-d32up parisc/0.30.209 VCI: 0002:0001 263 03000116 (ugid24) --- testing ext2 filesystem ... [000]# succeeded. xid related tests ... [001]# succeeded. [002]# succeeded. [011]# succeeded. [012]# succeeded. [014]# succeeded. [015]# succeeded. [019]# succeeded. [020]# succeeded. [021]# succeeded. [022]# succeeded. [023]# succeeded. [024]# succeeded. [025]# succeeded. [026]# succeeded. [027]# succeeded. [028]# succeeded. [033]# succeeded. [034]# succeeded. [035]# succeeded. [037]# succeeded. xattr related tests ... [101]# succeeded. [102]# succeeded. [103]# succeeded. [104]# succeeded. [106]# succeeded. [108]# succeeded. [109]# succeeded. [112]# succeeded. [113]# succeeded. [114]# succeeded. [115]# succeeded. [116]# succeeded. [117]# succeeded. [118]# succeeded. [119]# succeeded. [121]# succeeded. [122]# succeeded. [123]# succeeded. [124]# succeeded. [199]# succeeded. --- testing ext3 filesystem ... [000]# succeeded. xid related tests ... [001]# succeeded. [002]# succeeded. [011]# succeeded. [012]# succeeded. [014]# succeeded. [015]# succeeded. [019]# succeeded. [020]# succeeded. [021]# succeeded. [022]# succeeded. [023]# succeeded. [024]# succeeded. [025]# succeeded. [026]# succeeded. [027]# succeeded. [028]# succeeded. [033]# succeeded. [034]# succeeded. [035]# succeeded. [037]# succeeded. xattr related tests ... [101]# succeeded. [102]# succeeded. [103]# succeeded. [104]# succeeded. [106]# succeeded. [108]# succeeded. [109]# succeeded. [112]# succeeded. [113]# succeeded. [114]# succeeded. [115]# succeeded. [116]# succeeded. [117]# succeeded. [118]# succeeded. [119]# succeeded. [121]# succeeded. [122]# succeeded. [123]# succeeded. [124]# succeeded. [199]# succeeded. --- testing xfs filesystem ... [000]# failed. (xfs format failed) --- testing reiser filesystem ... [000]# failed. (reiserfs format failed) --- testing jfs filesystem ... [000]# failed. (jfs format failed) (well, as I din't include xfs, jfs nore reiserfs in my kernel: o xfs showed some pb a time ago (k 2.6.8.1) need to re-test o jfs tested a very very long time ago (need also to retest o reiserfs (afair) was broken a longest time ago (iirc k 2.4), since I never read any successfull report, though.) The additional question is (may be non sense but thought): those chroot disk was also bootable, so if I want to reboot I would just have to write and run a script which will would restore /dev /etc/init.d and corresponding rc?.d? well, it might be an option to use udev to populate the dev
Re: [Vserver] VServer seems to work fine basicaly on hppa too -) (just some question)
Hello Herbert, [...] dd if=/dev/zero of=/var/tmp/200MB.img bs=1M count=200 losetup /dev/loop0 /var/tmp/200MB.img mkdir /mnt/test testfs.sh -D /dev/loop0 -M /mnt/test -x mmm here are some more test results (i.e. xfs, reiserfs jfs): --- testing xfs filesystem ... [000]# succeeded. xid related tests ... [001]# succeeded. mount: /mnt/test not mounted already, or bad option [002]# succeeded. [011]# succeeded. [012]# succeeded. [014]# succeeded. cat: /mnt/test/file_2: No such file or directory cat: /mnt/test/file_3: No such file or directory [015]# succeeded. [019]# succeeded. [020]# succeeded. [021]# succeeded. [022]# succeeded. [023]# succeeded. [024]# succeeded. cat: /mnt/test/file_2: No such file or directory cat: /mnt/test/file_3: No such file or directory [025]# succeeded. [026]# succeeded. tee: /mnt/test/file_2: Permission denied tee: /mnt/test/file_3: Permission denied [027]# succeeded. [028]# succeeded. [033]# succeeded. [034]# succeeded. cat: /mnt/test/file_1: No such file or directory [035]# succeeded. tee: /mnt/test/file_1: Permission denied tee: /mnt/test/file_2: Permission denied [037]# succeeded. xattr related tests ... [101]# succeeded. [102]# succeeded. [103]# succeeded. [104]# succeeded. chmod: changing permissions of `/mnt/test/dir_3053': Operation not permitted chmod: changing permissions of `/mnt/test/dir_3053': Operation not permitted [106]# succeeded. [108]# succeeded. [109]# succeeded. [112]# succeeded. [113]# succeeded. [114]# succeeded. [115]# succeeded. chmod: changing permissions of `/mnt/test/file_3053': Operation not permitted chmod: changing permissions of `/mnt/test/file_3053': Operation not permitted chmod: changing permissions of `/mnt/test/file_3053': Operation not permitted chmod: changing permissions of `/mnt/test/file_3053': Operation not permitted chmod: changing permissions of `/mnt/test/file_3053': Operation not permitted chmod: changing permissions of `/mnt/test/file_3053': Operation not permitted [116]# succeeded. [117]# succeeded. [118]# succeeded. [119]# succeeded. [121]# succeeded. [122]# succeeded. [123]# succeeded. [124]# succeeded. [199]# succeeded. --- testing reiser filesystem ... mkfs.reiserfs 3.6.19 (2003 www.namesys.com) [000]# succeeded. xid related tests ... [001]# succeeded. mount: /mnt/test not mounted already, or bad option [002]# succeeded. [011]# succeeded. [012]# succeeded. [014]# succeeded. cat: /mnt/test/file_2: No such file or directory cat: /mnt/test/file_3: No such file or directory [015]# succeeded. [019]# succeeded. [020]# succeeded. [021]# succeeded. [022]# succeeded. [023]# succeeded. [024]# succeeded. cat: /mnt/test/file_2: No such file or directory cat: /mnt/test/file_3: No such file or directory [025]# succeeded. [026]# succeeded. tee: /mnt/test/file_2: Permission denied tee: /mnt/test/file_3: Permission denied [027]# succeeded. [028]# succeeded. [033]# succeeded. [034]# succeeded. cat: /mnt/test/file_1: No such file or directory [035]# succeeded. tee: /mnt/test/file_1: Permission denied tee: /mnt/test/file_2: Permission denied [037]# succeeded. xattr related tests ... [101]# succeeded. [102]# succeeded. [103]# succeeded. [104]# succeeded. chmod: changing permissions of `/mnt/test/dir_3053': Operation not permitted chmod: changing permissions of `/mnt/test/dir_3053': Operation not permitted [106]# succeeded. [108]# succeeded. [109]# succeeded. [112]# succeeded. [113]# succeeded. verify /mnt/test/file_3053: -+(-)-i-+(-) ~ - [114]# failed. [115]# succeeded. chmod: changing permissions of `/mnt/test/file_3053': Operation not permitted chmod: changing permissions of `/mnt/test/file_3053': Operation not permitted chmod: changing permissions of `/mnt/test/file_3053': Operation not permitted chmod: changing permissions of `/mnt/test/file_3053': Operation not permitted chmod: changing permissions of `/mnt/test/file_3053': Operation not permitted chmod: changing permissions of `/mnt/test/file_3053': Operation not permitted [116]# succeeded. [117]# succeeded. [118]# succeeded. [119]# succeeded. [121]# succeeded. [122]# succeeded. [123]# succeeded. verify /mnt/test/file_3053: -+(-)-i-+(-) ~ i---E [124]# failed. [199]# succeeded. --- testing jfs filesystem ... [000]# succeeded. xid related tests ... [001]# succeeded. mount: /mnt/test not mounted already, or bad option [002]# succeeded. [011]# succeeded. [012]# succeeded. [014]# succeeded. cat: /mnt/test/file_2: No such file or directory cat: /mnt/test/file_3: No such file or directory [015]# succeeded. [019]# succeeded. [020]# succeeded. [021]# succeeded. [022]# succeeded. [023]# succeeded. [024]# succeeded. cat: /mnt/test/file_2: No such file or directory cat: /mnt/test/file_3: No such file or directory [025]# succeeded. [026]# succeeded. tee: /mnt/test/file_2: Permission denied tee: /mnt/test/file_3: Permission denied [027]# succeeded. [028]# succeeded. [033]# succeeded. [034]# succeeded. cat: /mnt/test/file_1: No such file or directory [035]#
Re: [Vserver] VServer seems to work fine basicaly on hppa too -) (just some question)
On Fri, Dec 16, 2005 at 02:55:34PM +0100, Joel Soete wrote: Hello Herbert, [...] dd if=/dev/zero of=/var/tmp/200MB.img bs=1M count=200 losetup /dev/loop0 /var/tmp/200MB.img mkdir /mnt/test testfs.sh -D /dev/loop0 -M /mnt/test -x mmm here are some more test results (i.e. xfs, reiserfs jfs): --- testing xfs filesystem ... [000]# succeeded. xid related tests ... [001]# succeeded. mount: /mnt/test not mounted already, or bad option [002]# succeeded. [011]# succeeded. [012]# succeeded. [014]# succeeded. cat: /mnt/test/file_2: No such file or directory cat: /mnt/test/file_3: No such file or directory [015]# succeeded. [019]# succeeded. [020]# succeeded. [021]# succeeded. [022]# succeeded. [023]# succeeded. [024]# succeeded. cat: /mnt/test/file_2: No such file or directory cat: /mnt/test/file_3: No such file or directory [025]# succeeded. [026]# succeeded. tee: /mnt/test/file_2: Permission denied tee: /mnt/test/file_3: Permission denied [027]# succeeded. [028]# succeeded. [033]# succeeded. [034]# succeeded. cat: /mnt/test/file_1: No such file or directory [035]# succeeded. tee: /mnt/test/file_1: Permission denied tee: /mnt/test/file_2: Permission denied [037]# succeeded. xattr related tests ... [101]# succeeded. [102]# succeeded. [103]# succeeded. [104]# succeeded. chmod: changing permissions of `/mnt/test/dir_3053': Operation not permitted chmod: changing permissions of `/mnt/test/dir_3053': Operation not permitted [106]# succeeded. [108]# succeeded. [109]# succeeded. [112]# succeeded. [113]# succeeded. [114]# succeeded. [115]# succeeded. chmod: changing permissions of `/mnt/test/file_3053': Operation not permitted chmod: changing permissions of `/mnt/test/file_3053': Operation not permitted chmod: changing permissions of `/mnt/test/file_3053': Operation not permitted chmod: changing permissions of `/mnt/test/file_3053': Operation not permitted chmod: changing permissions of `/mnt/test/file_3053': Operation not permitted chmod: changing permissions of `/mnt/test/file_3053': Operation not permitted [116]# succeeded. [117]# succeeded. [118]# succeeded. [119]# succeeded. [121]# succeeded. [122]# succeeded. [123]# succeeded. [124]# succeeded. [199]# succeeded. --- testing reiser filesystem ... mkfs.reiserfs 3.6.19 (2003 www.namesys.com) [000]# succeeded. xid related tests ... [001]# succeeded. mount: /mnt/test not mounted already, or bad option [002]# succeeded. [011]# succeeded. [012]# succeeded. [014]# succeeded. cat: /mnt/test/file_2: No such file or directory cat: /mnt/test/file_3: No such file or directory [015]# succeeded. [019]# succeeded. [020]# succeeded. [021]# succeeded. [022]# succeeded. [023]# succeeded. [024]# succeeded. cat: /mnt/test/file_2: No such file or directory cat: /mnt/test/file_3: No such file or directory [025]# succeeded. [026]# succeeded. tee: /mnt/test/file_2: Permission denied tee: /mnt/test/file_3: Permission denied [027]# succeeded. [028]# succeeded. [033]# succeeded. [034]# succeeded. cat: /mnt/test/file_1: No such file or directory [035]# succeeded. tee: /mnt/test/file_1: Permission denied tee: /mnt/test/file_2: Permission denied [037]# succeeded. xattr related tests ... [101]# succeeded. [102]# succeeded. [103]# succeeded. [104]# succeeded. chmod: changing permissions of `/mnt/test/dir_3053': Operation not permitted chmod: changing permissions of `/mnt/test/dir_3053': Operation not permitted [106]# succeeded. [108]# succeeded. [109]# succeeded. [112]# succeeded. [113]# succeeded. verify /mnt/test/file_3053: -+(-)-i-+(-) ~ - hmm, that looks broken .. maybe a parisc issue? will verify when I get home ... [114]# failed. [115]# succeeded. chmod: changing permissions of `/mnt/test/file_3053': Operation not permitted chmod: changing permissions of `/mnt/test/file_3053': Operation not permitted chmod: changing permissions of `/mnt/test/file_3053': Operation not permitted chmod: changing permissions of `/mnt/test/file_3053': Operation not permitted chmod: changing permissions of `/mnt/test/file_3053': Operation not permitted chmod: changing permissions of `/mnt/test/file_3053': Operation not permitted [116]# succeeded. [117]# succeeded. [118]# succeeded. [119]# succeeded. [121]# succeeded. [122]# succeeded. [123]# succeeded. verify /mnt/test/file_3053: -+(-)-i-+(-) ~ i---E [124]# failed. [199]# succeeded. --- testing jfs filesystem ... [000]# succeeded. xid related tests ... [001]# succeeded. mount: /mnt/test not mounted already, or bad option [002]# succeeded. [011]# succeeded. [012]# succeeded. [014]# succeeded. cat: /mnt/test/file_2: No such file or directory cat: /mnt/test/file_3: No such file or directory [015]# succeeded. [019]# succeeded. [020]# succeeded. [021]# succeeded. [022]# succeeded. [023]# succeeded. [024]# succeeded. cat: /mnt/test/file_2: No such file or
Re: [Vserver] VServer seems to work fine basicaly on hppa too -) (just some question)
Hello Herbert, On Tue, Dec 13, 2005 at 05:20:22PM +0100, Joel Soete wrote: Hello All, Great the kernel was booting fine; just grep the upstream util-vserver tools and hack lib/syscall-faalback.h to match __NR_vserver 263 for hppa to build it with default debian pkg configure options ;-) As I already had some chroot disks that I used for severall test (glibc, ...) and I wouldn't like to re-install a debian debootstrap, I sounds reasonable ... use a vserver build -m skeleton ;-) and gather some more info to start my vserver named DebSid: # vserver-stat CTX PROC VSZ RSS userTIME sysTIME UPTIME NAME 0 68 134.3M 49.3M 7m32s62 28m01s19 4h14m54 root server 49153 15 76.8M 22.5M 0m05s31 0m14s53 2h47m02 DebSid [...] and after stolen an ipv4 address and configure nic, ssh, ...: ssh 10.24.252.111 Linux patst007 2.6.15-rc1-pa3-d32up #8 Mon Nov 14 13:01:04 CET 2005 parisc GNU/Linux excellent, so the patch worked fine for you on 2.6.15-rc1-pa3? mmm, no sorry I didn't pay attention: this message stand in fact in the /etc/motd of the vps (updated last time I booted actualy with another testing 2.6.15-rc1-pa3-d32up kernel); I need to check to update this motd when the vps is started. Apologies for confusion ;-( could you give the testme.sh and testfs.sh a spin on that machine? testme works fine: # ./testme.sh-0.14 -v Linux-VServer Test [V0.14] Copyright (C) 2003-2005 H.Poetzl chcontext is working. chbind is working. chcontext 0.30.209 -- allocates/enters a security context This program is part of util-vserver 0.30.209 Copyright (C) 2004 Enrico Scholz This program is free software; you may redistribute it under the terms of the GNU General Public License. This program has absolutely no warranty. Linux 2.6.14.3-vs2.1.0-rc10-pa0-d32up parisc/0.30.209/0.30.209 [Ea] (0) VCI: 0002:0001 263 03000116 ([EMAIL PROTECTED]) (gcc version 4.0.3 20051201 (prerelease) (Debian 4.0.2-5)) #2 Wed Dec 7 12:07:47 CET 2005 --- [000]# chcontext true chcontext --ctx 45678 true [000]# succeeded. [001]# chcontext --ctx 45678 egrep 'context|VxID' /proc/self/status [001]# succeeded. [011]# chcontext --secure --ctx 45678 mknod /tmp/testme.sh-0.14.x4zqUF/node c 0 0 [011]# succeeded. [031]# chcontext --hostname zaphod.21379 uname -a | grep -q zaphod.21379 [031]# succeeded. [101]# chbind --ip 192.168.0.42 true [101]# succeeded. [102]# chbind --ip 192.168.0.1/255.255.255.0 --ip 10.0.0.1/24 true [102]# succeeded. [201]# chcontext --ctx 45678 --flag fakeinit bash -c 'test $$ -eq 1' [201]# succeeded. [202]# chcontext --flag fakeinit bash -c 'test $$ -eq 1' [202]# succeeded. OTC testfs.sh-0.11 failed after a return (no messaged)? I have a quick look and testfs -v -F ext2 (help example) launch mkfs.ext2 /dev/zero manualy this cmdl is querying: mke2fs 1.38 (30-Jun-2005) /dev/zero is not a block special device. Proceed anyway? (y,n) though. (please exaplain me what is it supposed to do and detect as pb?) [...] The additional question is (may be non sense but thought): those chroot disk was also bootable, so if I want to reboot I would just have to write and run a script which will would restore /dev /etc/init.d and corresponding rc?.d? well, it might be an option to use udev to populate the dev (on a real boot) and just clense them before you use it as guest ... Or is it possible to instruct vserver to use better a /dev.vserver as well as /etc/init.d.vserver, ...? you could also do some --bind mounting on guest startup (see pre/post scripts and fstab) and of course if security is not an issue for your guests, you could also let them run with the fully populated /dev (well I just discover this proj about 2 weeks ago so still have planty to learn ;-) ) Effectively for the moment I am not already worry on security of the guest vps but more of application started (as motd update ;-)), also the option pre/post scripts would certainly take my first attention. (btw: am I wrong: the init of guest vps only run the rc2.d scripts (here the default run level in /etc/inittab) and not previous levels? what would be the best way: move all request startup script in /etc/verserver/DebSid...?) Thanks a lot, Joel --- A free anti-spam and anti-virus filter on all Scarlet mailboxes More info on http://www.scarlet.be/ ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] VServer seems to work fine basicaly on hppa too -) (just some question)
On Thu, Dec 15, 2005 at 01:48:51PM +0100, Joel Soete wrote: Hello Herbert, On Tue, Dec 13, 2005 at 05:20:22PM +0100, Joel Soete wrote: Hello All, Great the kernel was booting fine; just grep the upstream util-vserver tools and hack lib/syscall-faalback.h to match __NR_vserver 263 for hppa to build it with default debian pkg configure options ;-) As I already had some chroot disks that I used for severall test (glibc, ...) and I wouldn't like to re-install a debian debootstrap, I sounds reasonable ... use a vserver build -m skeleton ;-) and gather some more info to start my vserver named DebSid: # vserver-stat CTX PROC VSZ RSS userTIME sysTIME UPTIME NAME 0 68 134.3M 49.3M 7m32s62 28m01s19 4h14m54 root server 49153 15 76.8M 22.5M 0m05s31 0m14s53 2h47m02 DebSid [...] and after stolen an ipv4 address and configure nic, ssh, ...: ssh 10.24.252.111 Linux patst007 2.6.15-rc1-pa3-d32up #8 Mon Nov 14 13:01:04 CET 2005 parisc GNU/Linux excellent, so the patch worked fine for you on 2.6.15-rc1-pa3? mmm, no sorry I didn't pay attention: this message stand in fact in the /etc/motd of the vps (updated last time I booted actualy with another testing 2.6.15-rc1-pa3-d32up kernel); I need to check to update this motd when the vps is started. Apologies for confusion ;-( could you give the testme.sh and testfs.sh a spin on that machine? testme works fine: # ./testme.sh-0.14 -v Linux-VServer Test [V0.14] Copyright (C) 2003-2005 H.Poetzl chcontext is working. chbind is working. chcontext 0.30.209 -- allocates/enters a security context This program is part of util-vserver 0.30.209 Copyright (C) 2004 Enrico Scholz This program is free software; you may redistribute it under the terms of the GNU General Public License. This program has absolutely no warranty. Linux 2.6.14.3-vs2.1.0-rc10-pa0-d32up parisc/0.30.209/0.30.209 [Ea] (0) VCI: 0002:0001 263 03000116 ([EMAIL PROTECTED]) (gcc version 4.0.3 20051201 (prerelease) (Debian 4.0.2-5)) #2 Wed Dec 7 12:07:47 CET 2005 --- [000]# chcontext true chcontext --ctx 45678 true [000]# succeeded. [001]# chcontext --ctx 45678 egrep 'context|VxID' /proc/self/status [001]# succeeded. [011]# chcontext --secure --ctx 45678 mknod /tmp/testme.sh-0.14.x4zqUF/node c 0 0 [011]# succeeded. [031]# chcontext --hostname zaphod.21379 uname -a | grep -q zaphod.21379 [031]# succeeded. [101]# chbind --ip 192.168.0.42 true [101]# succeeded. [102]# chbind --ip 192.168.0.1/255.255.255.0 --ip 10.0.0.1/24 true [102]# succeeded. [201]# chcontext --ctx 45678 --flag fakeinit bash -c 'test $$ -eq 1' [201]# succeeded. [202]# chcontext --flag fakeinit bash -c 'test $$ -eq 1' [202]# succeeded. OTC testfs.sh-0.11 failed after a return (no messaged)? I have a quick look and testfs -v -F ext2 (help example) launch mkfs.ext2 /dev/zero manualy this cmdl is querying: mke2fs 1.38 (30-Jun-2005) /dev/zero is not a block special device. Proceed anyway? (y,n) though. (please exaplain me what is it supposed to do and detect as pb?) check testfs.sh -h and you will find that you can specify a device, which will be used to create various filesystems on, and verify the different aspects of attributes, barrier and xid tagging because those tests are destructive, the default is the /dev/zero device, which will not work :) something like this is supposed to work, given that you have support for the filesystems: dd if=/dev/zero of=/var/tmp/200MB.img bs=1M count=200 losetup /dev/loop0 /var/tmp/200MB.img mkdir /mnt/test testfs.sh -D /dev/loop0 -M /mnt/test -x The additional question is (may be non sense but thought): those chroot disk was also bootable, so if I want to reboot I would just have to write and run a script which will would restore /dev /etc/init.d and corresponding rc?.d? well, it might be an option to use udev to populate the dev (on a real boot) and just clense them before you use it as guest ... Or is it possible to instruct vserver to use better a /dev.vserver as well as /etc/init.d.vserver, ...? you could also do some --bind mounting on guest startup (see pre/post scripts and fstab) and of course if security is not an issue for your guests, you could also let them run with the fully populated /dev (well I just discover this proj about 2 weeks ago so still have planty to learn ;-) ) Effectively for the moment I am not already worry on security of the guest vps but more of application started (as motd update ;-)), also the option pre/post scripts would certainly take my first attention. (btw: am I wrong: the init of guest vps only run the rc2.d scripts (here the default run level in /etc/inittab) and not previous levels? what would be the best way: move all request startup script in /etc/verserver/DebSid...?) there are different init styles, one (plain) calls the 'real' init process inside the guest, the other (sysv)
Re: [Vserver] VServer seems to work fine basicaly on hppa too ; -) (just some question)
On Tue, Dec 13, 2005 at 05:20:22PM +0100, Joel Soete wrote: Hello All, Great the kernel was booting fine; just grep the upstream util-vserver tools and hack lib/syscall-faalback.h to match __NR_vserver 263 for hppa to build it with default debian pkg configure options ;-) As I already had some chroot disks that I used for severall test (glibc, ...) and I wouldn't like to re-install a debian debootstrap, I sounds reasonable ... use a vserver build -m skeleton ;-) and gather some more info to start my vserver named DebSid: # vserver-stat CTX PROCVSZRSS userTIME sysTIMEUPTIME NAME 0 68 134.3M 49.3M 7m32s62 28m01s19 4h14m54 root server 49153 15 76.8M 22.5M 0m05s31 0m14s53 2h47m02 DebSid enter it too: # ps -ef UIDPID PPID C STIME TTY TIME CMD root 1 0 0 14:05 ?00:00:52 init [2] root 5294 1 0 14:05 ?00:00:00 /sbin/syslogd 103 5318 1 0 14:05 ?00:00:00 /usr/bin/dbus-daemon-1 --system root 5340 1 0 14:05 ?00:00:00 /usr/bin/netserver root 5355 1 0 14:05 ?00:00:02 /usr/bin/X11/xfs -daemon root 5367 1 0 14:05 ?00:00:00 /usr/sbin/xinetd -pidfile /var/run/xinetd.pid -stayalive daemon5408 1 0 14:05 ?00:00:00 /usr/sbin/atd root 5411 1 0 14:05 ?00:00:00 /usr/sbin/cron root 5426 1 0 14:05 ?00:00:00 /usr/sbin/gdm root 5704 5693 0 14:37 pts/100:00:01 /bin/bash -login root 6418 1 0 15:51 ?00:00:00 /usr/sbin/sshd root 6421 6418 0 15:52 ?00:00:00 sshd: jso [priv] jso 6423 6421 0 15:52 ?00:00:00 sshd: [EMAIL PROTECTED]/6 jso 6424 6423 0 15:52 pts/600:00:00 -bash root 6434 6424 0 15:52 pts/600:00:00 su - root 6435 6434 0 15:52 pts/600:00:00 -su root 7573 5704 0 17:02 pts/100:00:00 ps -ef and after stolen an ipv4 address and configure nic, ssh, ...: ssh 10.24.252.111 Linux patst007 2.6.15-rc1-pa3-d32up #8 Mon Nov 14 13:01:04 CET 2005 parisc GNU/Linux excellent, so the patch worked fine for you on 2.6.15-rc1-pa3? could you give the testme.sh and testfs.sh a spin on that machine? The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. You have new mail. Last login: Tue Dec 13 15:50:52 2005 from wsjso.internal.mce.org debvs007:~ $ su - Password: [EMAIL PROTECTED]:~# ls -lrt total 24 drwx-- 2 root root 4096 Nov 23 2003 Mail -rw-r--r-- 1 root root 26 Apr 20 2005 Vjso drwxr-xr-x 2 root root 4096 Oct 5 15:26 tmp drwxr-xr-x 2 root root 4096 Oct 5 15:51 var drwxr-xr-x 2 root root 4096 Nov 3 19:09 bin drwxr-xr-x 2 root root 4096 Dec 13 14:19 Man [...] (well just basics, I still have to see which startup script I need to start/stop at the reboot/shutdown and other stuff I would like to test as xdmcp, ...) The additional question is (may be non sense but thought): those chroot disk was also bootable, so if I want to reboot I would just have to write and run a script which will would restore /dev /etc/init.d and corresponding rc?.d? well, it might be an option to use udev to populate the dev (on a real boot) and just clense them before you use it as guest ... Or is it possible to instruct vserver to use better a /dev.vserver as well as /etc/init.d.vserver, ...? you could also do some --bind mounting on guest startup (see pre/post scripts and fstab) and of course if security is not an issue for your guests, you could also let them run with the fully populated /dev HTH, Herbert Or doesn't it make any more sense at all because of vserver itself? Thanks again for all help, Joel --- NOTE! My email address is changing to ... @scarlet.be Please make the necessary changes in your address book. ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
