hello, > the options seem to be: > a) freeze the 2.4 vserver development at some > point, only do some updating and maintenance, > and continue with a SE-Linux/LSM version of > linux-vserver
to freeze 2.4 and concentrate on 2.6 is a good idea because 2.6 is the future and the 2.4 tree will be frozen by version 2.4.27. so the same should happen to the 2.4 version of vserver. WHEN?, i guess as soon as current under-dev features are implemented and stable? not sure.. but if you do a version based on se/lsm, doesn't that mean that one has to enable SE and has to use its tools? i haven't tried SE out yet.... having read some about it and its config scared me for trying it... :-) > 1) should the 2.4 branch be frozen, and if when? yes!.... 2.6 is the way to go when? as soon as the 2.4 branch is stable and works as expected only bugfixes should be done to the 2.4 branch after that > 2) is it bad if 2.4 and 2.6 branches diverge? no. if that eases the development op the 2.6 branch, and if changes are well documented so that people may learn them quickly, i see no problem in that > 3) is multitude (2.4/2.6/2.6SE) preferred over > development speed? there should be a frozen stable 2.4 branch IMO and it would be nice to have a 2.6 and 2.6SE branch -> taken that 2.6SE needs SE tools and is kinda complicated, and many people don't wanna use it.... dunno, as i said haven't had a closer look at SE yet if not, a single 2.6SE would suffice > 4) is a 2.4/2.6 migration path important to you? there shoulb be a good tutorial for migrating from 2.4 to 2.6 > 5) what branch 2.4, 2.6 or 2.6SE would you prefer? dunno much about SE so i would vote for 2.6... else 2.6SE > 6) what branch/version do you currently use/test? 2.4/1.24 -- regards, Georges Toth _______________________________________________ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
