|
From: Reddog H. <red...@ho...> - 2001-10-19 13:40:37
|
Looking at the code is one thing, understanding it is another. Reading the documentation that is acompanied usualy helps a bit but..... where do you start reading to understand the kernel, to understand the workings ? Personaly this is a commen problem for this kinds of projects. You need developers but: how can they learn enough (fast) to be of use ? A little documentation (introducktion) on how it works ( on a high level like: booting of lilo, then this file is runned to load this and this bla bla) could be verry usefull. Understanding the big picture let's the small things make (more) sence. Such a document will not only help me but also any other programmer that's new to the project and wants to make an contribution to this OS. Haven't find that doc yet so it could already be out theire so i keep my eye's open. In the meantime.... i'll have to start at a /dev/random point in the code and see what happens. Rolf > If you know C/C++ then you know as much C/C++ as they do. The thing you > are lacking is the knowledge of how the OS works. Don't be afraid to > look at the code. > > Brian G. > > > p.s. I'd like to contribute, but i think my C++, C programming skills > > aren't that of the kernelteam or even close. Any Ideas how I can help ? ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |