> maybe they will update/re-package util-vserver
> for debian on user request ...
bugreport about it not working correctly with vs1.x should be enough.
But maybe one should package util-vserver and upload it as independant
package?
--
Key fingerprint = 40D0 9FFB 9939 7320 8294 05E0 BCC7 02C4 7
On Tuesday, November 25, 2003 6:14 PM NZT,
Cédric Veilleux <[EMAIL PROTECTED]> wrote:
> Simon,
>
> Congrats for your good work! I have reviewed your work and I am sure
it
> will be very useful for a lot of us.
>
thanks!
> Do you think there could be a way of using skels to handle vserver
> upgr
Simon,
Congrats for your good work! I have reviewed your work and I am sure it will
be very useful for a lot of us.
Do you think there could be a way of using skels to handle vserver upgrades?
Would it be possible to propagate the changes made to a skel to the
individual vserve
Hi everyone!
I am pleased to announce the release of something I've been working on a
little while now: VSkel!
I have added a page on the Wiki about it (hope that is okay...) here:
http://www.linux-vserver.org/index.php?page=VSkel
WHAT IS IT?
VSkel is a script for creating and maintaining
On Mon, Nov 24, 2003 at 10:30:21PM +, Jonathan Sambrook wrote:
> As you may remember, DSVR use the s_context kernel patch in an extremely
> non-standard manner. This means we stress the s_context patch in
> different ways to the standard vserver userspace utils (of either
> flavour).
>
> I've
On Mon, Nov 24, 2003 at 11:05:58PM +0100, Christian Mayrhuber wrote:
> Dariush Pietrzak wrote:
> >>Works as advertised.
> >>Tested with kernel-2.6.0-test9 and e2fsprogs headers.
> >
> >I'm getting lost,
> > how does util-vserver 0.26 differ from vserver 0.26 package that I got
> >here in debian pa
As you may remember, DSVR use the s_context kernel patch in an extremely
non-standard manner. This means we stress the s_context patch in
different ways to the standard vserver userspace utils (of either
flavour).
I've been being driver mad for months by a system lockup which occurs on
some machin
Dariush Pietrzak wrote:
Works as advertised.
Tested with kernel-2.6.0-test9 and e2fsprogs headers.
I'm getting lost,
how does util-vserver 0.26 differ from vserver 0.26 package that I got
here in debian package?
There are two different versions of the vserver utilities, the original
ones from Jaq
> Works as advertised.
> Tested with kernel-2.6.0-test9 and e2fsprogs headers.
I'm getting lost,
how does util-vserver 0.26 differ from vserver 0.26 package that I got
here in debian package?
--
Key fingerprint = 40D0 9FFB 9939 7320 8294 05E0 BCC7 02C4 75CC 50D9
Namagumi namagomi namagoroshi
__
Works as advertised.
Tested with kernel-2.6.0-test9 and e2fsprogs headers.
--
lg, Chris
___
Vserver mailing list
[EMAIL PROTECTED]
http://list.linux-vserver.org/mailman/listinfo/vserver
[EMAIL PROTECTED] (Bert De Vuyst) writes:
>> No, 'vrpm' creates a new context without doing any ip configuration.
>
> OK. I was looking at the vrpm code to see if I could make a
> vapt-get utility for debian.
alpha branch has a vapt-get for Red Hat based systems. It runs in
host ctx and calls the
On Monday 24 November 2003 15:03, Enrico Scholz wrote:
> > Correct me if I'm wrong, but I think it's not a good idea.
> > Why? Some people have a backup of there vservers on a spare machine in
> > case there serverhardware fails. If they run vrpm on the spare machine,
> > vrpm will startup the vse
On Mon, Nov 24, 2003 at 02:34:37PM +0100, Bert De Vuyst wrote:
>
> Hello,
Hi Bert!
> After looking at the code of tool vrpm (part of vserver and util-vserver), I
> have some questions.
>
> 1. The location of /vservers is hardcoded in this tool.
> I think it's at better idea use the option VSER
On Mon, Nov 24, 2003 at 03:27:03PM +1100, Charles Dale wrote:
> Hmm can someone else answer this one please, I've lost track of what
> happened to the Per Context Quota & Disk Limit patches after 1.0. Herbert
> did they get merged into the main patch?
Sure, thanks so far, Chuck!
Quota Hashes, Con
On Mon, Nov 24, 2003 at 12:29:09PM +0100, Ake van der Meer wrote:
> Hi Herbert,
>
> >From linux-vserver.org it wasn't obvious to me how to best file a
> problem or bug report.
currently, the best way is via the mailing list ...
> Last weekend I upgraded several machines from ctx17 to vs1.00, and
[EMAIL PROTECTED] (Bert De Vuyst) writes:
> After looking at the code of tool vrpm (part of vserver and util-vserver), I
> have some questions.
>
> 1. The location of /vservers is hardcoded in this tool.
Not in util-vserver. In stable branch, this value is set at ./configure time.
In alpha branc
- Original Message -
From: "Bert De Vuyst" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, November 24, 2003 1:34 PM
Subject: [Vserver] vrpm code questions
>
> Hello,
>
> After looking at the code of tool vrpm (part of vserver and util-vserver),
I
> have some questions.
>
> 1.
Hello,
After looking at the code of tool vrpm (part of vserver and util-vserver), I
have some questions.
1. The location of /vservers is hardcoded in this tool.
I think it's at better idea use the option VSERVERS_ROOT=/vservers in this
script and to use $VSERVERS_ROOT inside the script.
In cas
18 matches
Mail list logo
