Hi,
On Mon, Apr 18, 2005 at 06:18:04PM +0200, Ola Lundqvist wrote:
>
> Thanks a lot! It has been on my todo list, but I have not done
> this yet. Have you tested this, and if so in what cases.
>
yes, I have tested it to some extent. Of course I cannot test each and
every option. I did something like:
$ newvserver --hostname vs-test9 --domain some.domain --ip 192.168.0.1
This works fine for me.
The options "--arch" "--dist" "--mirror" should still work the same,
they are given to vserver as arguments to debootstrap. I only removed
some legacy stuff, so there is still the same code for the other
options, except "--copy-vreboot", "--no-copy-vreboot" and
"--fakeinit". Still TODO is "--fakeinit" and other flags like
"nprocs", but they can probably all be supported by the
vserver-build "--flags" argument. I didn't check the one-to-one
equivalence of the configuration (/etc/vservers/vserver-name.conf on
the one hand and /etc/vservers/vserver-name/* on the other hand).
I'm currently writing some local extensions to "vserver ... build" by
adding a file /etc/vservers/.distributions/sarge/initpost (I need some
files copied from the host to the new vserver; this is not possible
with --post-install-script of newvserver). In principle it should even
be easily possible to put the whole stuff of newvserver into such
initpre/initpost scripts. Then newvserver would just be a very short
wrapper script around "vserver ... build" and both creation methods
("vserver ... build" and newvserver) would be equivalent. What do you
think?
regards
Daniel
--
-----------------------------------------------------------------
Daniel Hermann, Institut fuer Theorie der Kondensierten Materie
Universitaet Karlsruhe Tel: ++49 (0)721 608-3588
Postfach 6980 Fax: ++49 (0)721 608-7779
76128 Karlsruhe, Germany email: [EMAIL PROTECTED]
-----------------------------------------------------------------
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
