Maarten Engelen wrote:
> Maybe the main disadvantage of vserver is that it's a beta version (0.10). 
> FreeVSD has had much more time to prove itself in a production environment. 

Vserver actually runs quite well in production environment, but is still under
heavy development (and of course, every new release needs some testing, before
taken in production).

> (Kind of funny, in vserver you can execute a vhalt command to shutdown your 
> virtual server, but you can't get it to start up again by yourself :-) 

Can you start your server up again, if you halt it, without pushing any buttons ?
Actually, that can easily be fixed by a script on the hostserver environment.

Klavs Klavsen wrote:
> vserver requires a kernel patch. freevsd doesn't. I'm unfortunately not 
> clever enough to figure out, if that means that freevsd is less safe 
> than vserver, or if vserver is just troublesome as it can't use the 
> standard kernel. 

This question actually not got answered at all.

I've been running vserver for a while, but I allways look around, if there
should be any better alternatives.

So what advantages are there in the way freevsd is done ?

A bit about the vserver concept, if now known: Here we are talking about a
security context on the kernel level, that works a bit like a bsd jail. The
vserver gets chrooted in his "root" directory and is limited with the
capabilities and ip-adress assigned to the vserver. The user of the vserver has
full root-rights inside his jail and can not see other ip-adresses, filesystems
and processes beyond hos own.

Regards,
Martin List-Petersen
martin at list-petersen dot dk
--
You have the body of a 19 year old.  Please return it before it gets wrinkled.

------------------------- The freeVSD Support List --------------------------
Subscribe:   mailto:[EMAIL PROTECTED]?body=subscribe%20freevsd-support
Unsubscribe: mailto:[EMAIL PROTECTED]?body=unsubscribe%20freevsd-support
Archives:    http://freevsd.org/support/mail-archives/freevsd-support
-----------------------------------------------------------------------------

Reply via email to