> > As an aside, I tend to find that I learn virtually nothing from sitting down
> > and reading source code. I do, however, learn a great deal by tracing source
> > code in an attempt to examine a particular execution path in detail.
>
> I kind of agree. I've learned much about Linux this way
> [but I've learned even more by trying to write kernel code]
>
> I started first by tracing the code from boot to init, then each
> system call while making plenty of notes along the way.
How exactly do you go about tracing code from to init?
there is a lot of src there and finding functions when your new to the
structure could be hard.
Cheers Adam
>
> It is not the best coded or documented source around, but you
> soon discover that the kernel is simple in overall design.
> Just try not to get bogged down too much in the details at first.
>
> --
> Andrew E. Mileski mailto:aem@netcom.ca
>