> > In spite of stiff opposition, and with loosing a lot of important
> > functionality in the process...
> hmm, what kind of functionality was lost, IYO?
- ability to hot-add/hot-remove IPs from running guest
- ability to enter running/non-running guest
- ability to hot-mount directories into running guest
- when entering guest this info used to be displayed:
ipv4root is now 127.2.0.1 127.3.0.3
New security context is 10005
it's missing now
- old vserver-build scripts created skeletons ready to be deployed, new
method requires quite some time for vserver-enabling newly built
skeletons... which is time-consuming, requires some knowledge and is
error-prone.
- ability to look at single vserver configuration and understand what's
going on ( similiar task requires running through directories, checking
their contents, and extensive knowledge of CURRENT way the utils works.)
I guess "find . -type f -ls -exec cat "{}" ';'" would be work-around
for this miss-feature.
- way of keeping heavily-commented template config for vserver. There is
no easy way to comment current config.
- generally new style trades ease of programming in primitive languages
for sysadmin's time. Which is great for people writing utils, not so
great for those forced to use them.
- principle of least surprise was broken, for example in 'dev', 'nodev',
I'm sure there's more, I'd be happy to hear that there are plans to fix
those..
-- Key fingerprint = 40D0 9FFB 9939 7320 8294 05E0 BCC7 02C4 75CC 50D9 Total Existance Failure _______________________________________________ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserverReceived on Sun Apr 23 17:08:39 2006