Re: [Vserver] great flower page

From: Guenther Fuchs <>
Date: Sun 23 Apr 2006 - 09:28:05 BST
Message-ID: <>

Hi there,

on Sunday, April 23, 2006 at 9:57:06 AM there was posted:

e> - ability to hot-add/hot-remove IPs from running guest
This is lost? AFAIK it is still possible, using the proper context.

e> - ability to enter running/non-running guest
Running guest entering is not lost, non-running guests always started
them, so I see the actual way beeing more clear

e> - ability to hot-mount directories into running guest
This is lost? AFAIK it is still possible, using the proper context.

e> - when entering guest this info used to be displayed:
e> ipv4root is now
e> New security context is 10005
e> it's missing now
OK, that is lost. But it is not really necessary IMHO. There are other
and also easy ways to achieve that info.

e> - old vserver-build scripts created skeletons ready to be deployed, new
e> method requires quite some time for vserver-enabling newly built
e> skeletons... which is time-consuming, requires some knowledge and is
e> error-prone.
Cannot follow this problem, as I never worked / do not work with skeleton.

e> - ability to look at single vserver configuration and understand what's
e> going on ( similiar task requires running through directories, checking
e> their contents, and extensive knowledge of CURRENT way the utils works.)
e> I guess "find . -type f -ls -exec cat "{}" ';'" would be work-around
e> for this miss-feature.
I had this as a personal "problem" as well when changing to the new
scheme. As for now, since I'm working a while with the new scheme, it
is more clear and more understandable for myself then the old one. But
there's one point, I agree still with you: The examples are lost, the
relevant documentation is therefore less understandable (and not
everyone realises how to switch the stylesheet on the "flower page").
So this really could (should?) be improved to fit the previousely
reached level, yes.

e> - way of keeping heavily-commented template config for vserver. There is
e> no easy way to comment current config.

e> - generally new style trades ease of programming in primitive languages
e> for sysadmin's time. Which is great for people writing utils, not so
e> great for those forced to use them.

e> - principle of least surprise was broken, for example in 'dev', 'nodev',

regards 'n greez,
Guenther Fuchs
(aka "muh" and "powerfox")
Vserver mailing list
Received on Sun Apr 23 17:00:33 2006
[Next/Previous Months] [Main vserver Project Homepage] [Howto Subscribe/Unsubscribe] [Paul Sladen's vserver stuff]
Generated on Sun 23 Apr 2006 - 17:00:36 BST by hypermail 2.1.8