> Anyone who wants to contribute to the project, but can't code, here is your
> chance. Don't worry about discussing in depth what the files should contain.
> Just write something and we will go from there.
Hi,
What I think would be good is a file describing very basically how the kernel works,
what bits get executed in what order etc.
I'm intrested in ELKS for a number of reasons;
a-I want to learn more about the Linux kernel, and OSs in general
b-I want to hack my Psion 3c
c-I want to enhance my programming skills, and learn C/asm
The only thing I have found which helps with (a) is in the kernel hackers guide. It
would be nice to have something directly applicable to ELKS. That way people using
ELKS to learn (like me) could go through this file, and read the source code in the
order it is executed, and maybe, just maybe, cotton on to what's happening.
Maybe this is just a waste of time though. What do others think?
Adam
