It works fine - and it should work fine for the next versions with a filename change only :) Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 10580 [details] vserver utilities I think it should go in app-emulation/vserver :)
Created attachment 10593 [details] vserver-0.22.ebuild - with patch I added a patch to the ebuild - that makes it compatible with Gentoo (and other) init systems that do not use /etc/rc.d/rc {0-6}. you just set S_START="/sbin/rc default" and S_STOP="/sbin/rc shutdown" in your /etc/vservers/<vserver-name>.conf p.s. that dir isn't created, but I could put that in the ebuild - and a sample conf and .sh ? otherwise newvserver script will create one - but it can't handle generating gentoo servers - and needs RPM utility to make redhat and other vservers.
I tested this ebuild and it works flawlessly. Please note that the "fakeinit" flag should not be used in your gentoo vservers configuration file, otherwise the STARTCMD / STOPCMD patch will be ineffective and the vserver will not boot properly. Also, to be of any interest, this package needs a patched kernel. The wolk-sources kernel contains the required patch, but a ctx-sources or vserver-sources ebuild could be useful.
I tested too -- also no problems. For the patched kernel-sources see bug #24619
I just updated the patch, so it applies cleanly with vserver-0.23. All that is needed is to rename the vserver ebuild to 0.23 and it will work like a charm ;) How is it looking to get this in the tree? Anything you want from me? I'll gladly throw up a changelog if you are considering throwing it in :)
great... I worked perfectly here !! :c) It only remains to be put into the official portage tree. But I can't see any license nor any (c) copyright in this package ? <ironic> because it is in the public domain, I can get it, put my company's copyright on it, and publish it under an open source but totally proprietary license... great !! Thanks for your work klavs ! </ironic> Be careful to put _your_ copyright and the licence you've chosen (maybe an OSI certified if you want Gentoo Linux integrate it) into your package's file. It can seem useless... but as my example shows, it is not !!
Created attachment 15590 [details] vserver-0.23.ebuild - using patch from my site. Just upgraded it to 0.23, added the GPLv2 statement :) and wrote a Changelog.
Created attachment 15591 [details] Changelog
the vserver-0.23 I thought was released, was actually "just" a Debian version of 0.22. the vserver-0.22 ebuild still works fine - so use that :) OOOPS - I messed up, sorry.
0.23 is available on ftp://ftp.solucorp.qc.ca/pub/vserver/ It may not be _offical_ as the website only lists 0.22, but is works for me.
vserver-0.22 don't work w/ the ctx17a kernel patch :c/ I tried two things then... - renaming the patch and the ebuild from -0.22 to -0.23 -> it worked but w/ hunks on patch - removing the patch lines from the ebuild. Works well but I still don't have try everything.
a few updates are available: latest release is 0.28 (Klavs patch needs to be ported -- I just hardcoded his original version). this bug is related to the new #33906 -- maybe we can both have in portage?
i think we can close this one as util-vserver (the successor if vserver) is in-portage now (see bug #45053 and bug #45729).
Yup. I've been running kernel-2.6 and theres still no vserver patch for that, so I haven't been using it - thus no upgrade :) *** This bug has been marked as a duplicate of 45053 ***
@klavs: there is a vserver-patch for 2.6 (well, it's not marked stable, but what is this days? ;) have a look at: http://www.linux-vserver.org/ (a good meta-page for vservser- stuff), or directly at http://www.13thfloor.at/vserver/e_patches/vs-26x/ if it works for you it would be nice to have a 2.6-ebuild (sys-kernel/vserver-sources are in-portage since yesterday :)
I patched my kernel gentoo-dev-sources-2.6.4-r1 with the vserver patches, and it went fine (only had to resolve a few myself :) It seems to run fine enough - the kernel is stable, and vserver <vservername> enter works too - and sets up an interface for the vserver. I'm not using vserver anymore - went too long with 2.4 with USAGI patch, and 2.6 without vserver support :) When I get the time, I could start looking at vserver again - IMHO we need either a vserver-baselayout - or a USE option for baselayout, to fix the baselayout for a vserver. It needs to be easy to run Gentoo-vservers (and other distros too, but thats not our problem is it :)
