got through hunk #41 today. aparently, the new mail account i set up is broken. makes it hard to extend an olive branch to the old simple openmosix team.
technically, about a year ago, we butted heads. they wanted to drag the dev work to a more modern kernel, before geting core openmosix components stabilized. i went my way, they went theirs.. and seem to have been inactive all of 2008.
I've asked a friend to contact them, while i'm fighting my mail. I hope he's a bit more political than I am, I think I have spent too much time on irc with kernel hackers. :)
i was always of the opinion we should be documenting and fixing the current 2.6.17 tree, rather than trying to keep up with the kernel itsself. while i know the kernels dveloped some new APIs, and merged some code that we're still "maintaining" (in-kernel sockets, kgdb), I'm of the opinion that until we can prove 2.6.17 isn't going to work, we should be trying to fix our code, not introduce new bugs during repeated porting efforts.
Hunk 41 was interesting. It contains the logic for moving from kernelspace to userspace for an openmosix process, as well as several other kernel<->openmosix APIs. It seems most of the code we've added to kernel .c files calls something in this patch.
Google has indexed the new site URL. this time I disabled two trac modules that were confusing google, and that we were not using (the milestones, and the timelines). we're going a bit too slow to use them.
I'm still disapointed we couldnt come up with a zombie themed name for the project. after all, we're slowly moving forward, and looking for BRAAAINS...
oh! and we got git set up. we don't have anonymous git set up, but the usage problem isn't getting docs out (thats what trac is for), but for syncing my two laptops. and best of all, it wasn't done by me. i actually have help for a change. now, its too bad my help is so well spoken and highly educated in physics/maths. holding a conversation has a tendancy to make me feel two feet tall. :)