On Thu, 15 Sep 2005 21:54:09 +1000, "ibm-main" wrote:
> ----- Original Message ----- 
> From: "MAEDA Naoaki"
> 
> > Hi Chandra,
> >
> > I believe that simplifying CKRM is the right thing to do.
> > At first glance, I have some questions and comments.
> 
> Yeah, me too.
> Humour me a little here folks - what the hell's going on   ???.
> 
> Are we forking or what  ???.
 
 Not really forking, per se.  We do have a stable version which is
 the e18 set and a few bugs have been identified with bug fixes
 available, so e19 is the update of the e18 set to 2.6.13.  There
 will also be a small consolidation version which will start folding
 some of the existing bug fixes into their original the original
 patch that introduced the problem, reducing the number of overall
 patches a fair bit.

 At the same time, a number of people have had some great ideas on
 how to simplify various areas of CKRM.  Those patches are starting
 to show up on the mailing list now for evaluation, and my initial
 impression is that all of these that I've seen thus far are excellent
 moves in the right direction.  Therefore, once they get some external
 review, I'll start pulling together an overall patch set which we'll
 call the "f" set which will for a (hopefully! ;-) short period of
 time be the "unstable" set which will contain all of the current
 new development.

 So, today, e19 is the quickest, easiest way to start using CKRM.
 Chandra is going to consolidate the patches into a mega patch for
 the CKRM sourceforge site (http://sourceforge.net/projects/ckrm) so
 that people can easily access and apply that stable set to 2.6.13.
 In some respects that will be our "control" version to ensure that
 as things change with the f series, we don't regress in terms of
 any bugs.  e19 has been pretty well tested as a set already and
 builds on a lot of well tested code.

 For people which are interested in the leading edge of development,
 they can start with Chandra's or Shailabh's or Matt's patches, apply
 them and work with them.  Any feedback generated there should be
 incorporated and will be in the "f" series of the patches, hopefully
 within a couple of weeks, maybe sooner.

> I built a 2.6.13.system (at work) when I saw Chandras posts - clean start,
> sounds good.
> Unfortunately, I had to pick the patches up from the (web-interface)
> archive, and it appears there must be a limit on the number of lines. Hence
> the patches were incomplete - I had to junk that build.
> O.K., that happens.

 We can see about putting Chandra's current set on sourceforge as well
 to avoid this problem.

> Then I get home to a truck-load of patches from Gerrit.
> So tell me - what the hell am I supposed to apply to what ???.
> I *really* would like to be involved here, but I'm new, and I just can't
> work out where you're all heading.
> 
> - do I go with Chandra on a 2.6.13 build, and look at that as the future
> direction

 Depends on what you want to do, but some of Chandra's patches will
 give you a very limited subset of what CKRM e19 can do today.  I
 *believe* his patches apply on top of 2.6.13 directly but I haven't
 actually reviewed them yet.

> - do I patch (some/any of ???) Gerrits updates on top of that

 Nope - my patches would go on top of a clean 2.6.13 build today.

> - do I add (some of) Gerrits patches to the (incomplete) e18 I am currently
> fighting with.

 Nope - e19 is a complete set - not a delta to e18.  So, best bet
 is to download linux-2.6.13, apply the e19 patch set (possibly from
 sourceforge in a few hours when Chandra rolls them all together)

 If you start with that, you have a functional CKRM environment to
 play with.

> - do I give up on this altogether, and go look at LKCD as something to
> occupy my idle hours ???.

 Well, LKCD is dead, long live kexec/kdump.  I wouldn't play with
 LKCD, personally.

 A lot of this, by the way, depends on what your goals are for contributions.
 If you want to be on the bleeding edge, Chandra's work will in part
 be the basis for that work, so you may want to get directions from
 him on how to start reviewing that and playing with that code base.

 At the same time, you might want a 2.6.13 + e19 CKRM kernel for
 comparison purposes.

 Hope that helps,

gerrit


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
ckrm-tech mailing list
https://lists.sourceforge.net/lists/listinfo/ckrm-tech

Reply via email to