Thanks again, I'm not very smart but a persistent person, so maybe I'll last thousand years trying until I'll master C and the source code but I will.

2012/4/27 John Floren <john@jfloren.net>
Good luck! The kernel is pretty readable and small enough to really
sit down and know what all the files are doing. Be warned that some of
the C is going to be in Plan 9's particular idiom, but in general you
can learn good practices from it. If you want to learn about writing
Plan 9 programs in general, check out the stuff under /sys/src/cmd.

John

On Fri, Apr 27, 2012 at 1:42 PM, Isaac Cortés <isaac18490@gmail.com> wrote:
> Thanks a lot  to everyone, I'm planing (my english sucks too) to learn about
> O.S. and C with this project, 'cause I'm kind of Hipster Student
> Informatic's
>
>
> 2012/4/27 John Floren <john@jfloren.net>
>>
>> On Fri, Apr 27, 2012 at 1:25 PM, Lyndon Nerenberg <lyndon@orthanc.ca>
>> wrote:
>> > Download the installation image from the website, gunzip, mount the
>> > resulting ISO image, then look in <mountpoint>/sys/src.
>>
>> Easier option: grab
>> http://plan9.bell-labs.com/sources/extra/plan9.tar.bz2, untar it, look
>> under plan9/sys/src/9 for the kernel source.
>>
>> john
>>
>
>
>
> --
>
>
>
> “But JavaSchools also fail to train the brains of kids to be adept, agile,
> and flexible enough to do good software design (and I don’t mean OO
> “design”, where you spend countless hours rewriting your code to rejiggle
> your object hierarchy, or you fret about faux “problems” like has-a vs.
> is-a). You need training to think of things at multiple levels of
> abstraction simultaneously, and that kind of thinking is exactly what you
> need to design great software architecture.”
>
>
>
>




--



“But JavaSchools also fail to train the brains of kids to be adept, agile, and flexible enough to do good software design (and I don’t mean OO “design”, where you spend countless hours rewriting your code to rejiggle your object hierarchy, or you fret about faux “problems” like has-a vs. is-a). You need training to think of things at multiple levels of abstraction simultaneously, and that kind of thinking is exactly what you need to design great software architecture.”