On 5/31/07, Noah yan <noah.yan at gmail.com> wrote: > John, > > thanks for your answer and i am glad that we are starting a > constructive discussion to do some real code work. there are so many > things that we can do along with what sun lab and others are doing. > see inline ... > > On 5/31/07, John Sonnenschein <johnsonnenschein at gmail.com> wrote: > > On 5/31/07, Noah yan <noah.yan at gmail.com> wrote: > > > John, > > > > > > let me ask: what is your status of building and testing the current > > > available code base? > > > > I've got it built & it boots on my little G4 mac mini. It fails to set > > up it's memory along the way > That is an area we can work on it, actually I am interested too to > make it working on Mac machines. But in the past six months, my > graduation takes most of time and I donot have enough to look at it > closely. > > anyway, this is the way I contribute the inetboot to the project. I > first look at those tasks that no body is working on and I am > interested. then I post to the community that I want to do that so > that everybody knows I am doing it. Then I do it and in the middle, > communicating with the community publically (also privately) about > various issues to get help and suggestions.
See, and that's just the thing. When you've got no idea where to start at all, it would be at least nice to be able to read a blog/mailing list/etc to see what's been done, if not to just ensure you're not writing stuff that's done, then at least for inspiration > > In a sense, perhaps. I very much believe in open development. If > > you're asking what I'd like to see, I'd like to see a kernel that > > completely works. That's just wishful thinking though and I don't > > expect a couple guys could get that much work done in that little > > time. A kernel that boots to single user would be nice if possible, > > but again, I have no idea what the status of the project is because > > it's been hidden behind sun's firewall for so long there's no way to > > guess what's going on > believe me, there are only three guys in sun labs working on this > project and there are so many things to do in order to get a kernel on > a single-user prompt. They are doing the most important part and doing > their best to reach such a milestone. I donot buy the idea of > releasing some code that is trapped in the middle and gives us no clue > what is going on. releasing just some code in the middle of nowhere doesn't do anyone any good, sure. But releasing code incrementally does a world of good. Even if you don't have a prompt to do anything at, if you've got a kernel that'll boot up to some defined point you can work with it & code against it. It's much easier to code-test-code than it is to code against a black box which may or may not work, and you won't find out until the next code drop that contains a vital prerequisite piece of code for what you're working on that you won't see for 6 months. -- PGP Public Key 0x437AF1A1 Availiable on hkp://pgp.mit.edu
