On Tue, Mar 28, 2006 at 02:54:09AM -0600, Corey Wright wrote:
> On Tue, 28 Mar 2006 09:33:19 +0200
> Peter Mann <Peter.Mann@tuke.sk> wrote:
> > i welcome some cooperation from experienced users with supporting
> > ubuntu dapper kernel with stable vserver 2.0.x patch ... no new
> > features, just updated patch every time dapper kernel changes - like
> > vserver 1.2.10 and vanilla kernel 2.4
> as i said in response to Tom Coetser, i don't remember any ubuntu
> security update breaking a vserver patch + merge patch (as something
> always fails from the beginning), so once a vserver patch is developed
> for ubuntu's 2.6.15, it should apply for a long time.
> the harder task is backporting any relevant bug fixes in later vserver
> releases to 184.108.40.206 (or whatever version everybody settles on).
> and the merging isn't the hard part, but instead just knowing that
> something needs to be backported. i doubt every fix Herbert applies to
> the current vserver (stable or unstable) he takes into consideration
> every previous release and if its applicable.
> rhel has had long release cycles (3 years?), so how have people using
> both rhel and vserver handled it? of course i think i remember rhel's
> kernels being aggressively patched, maybe requiring vserver users to
> forgo those kernels totally.
> > so who can support dapper vserver kernel?
> > Gerald Hochegger <email@example.com> ???
> > Herbert Poetzl <firstname.lastname@example.org> ???
sure I _could_ support a dapper vserver kernel, but,
and here is the important fact, this would not scale ...
in the very near future, I'd be supporting 20 different
kernels from at least 10 different distros, and there
would be no time left for development, so some other
model is required to solve this, and it's actually
quite simple ...
a) somebody steps up as 'new' maintainer for a dapper
vserver kernel (preferable stable and devel)
b) that somebody commits himself/herself to tracking
changes in dapper _and_ vserver in the forseeable
c) that person contacts me and we arrange to do an
initial port on that kernel, something which can
be considered a _known_good_ state
d) extensive testing has to follow, we don't want to
have folks run into merge issues, this is where
the dapper-vserver community comes into play
e) all changes to stable and devel are released in
small patches, which the maintainer has to check
and if required discuss with me
f) feedback from the dapper-vserver community, may
if be bugs, issues or feature requests will go
to that person, which will filter them and, if
applicable relay them to mainstream development
PS: this seems to work with Micah Anderson and debian
kernels so why shouldn't it work with other distros
> why not let it be community supported, using this mailing list for
> discussion and ubuntu's wiki for documentation? just a thought as this
> is open source after all. (maybe if its important enough to people,
> Herbert could be convinced to support ubuntu specifically with the
> right monetary incentive. i'm content doing it myself every 6 months.)
> Vserver mailing list
Vserver mailing list
Received on Tue Mar 28 10:31:25 2006