[lkml]   [2002]   [May]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: To start up
On Fri, May 10, 2002 at 11:16:04PM +0300, Halil Demirezen wrote:
> I have started to be interested in developing kernels code in a such way .
> But i am interested in the network source codes .. Do i have to know all
> kernel code or just the network section to be a devoloper for the kernel-
> network section-

i don't think anyone really knows "all" kernel code. have you looked at
just how much code there is? certainly you should try to understand as
much of the "core" code as possible, as that part is reasonably small
and important. the rest is either architecture-specific stuff (i386,
sparc), major subsystems (networking, vfs), or drivers (eepro100,

whats important is gaining a general understanding of how things are
done/what to watch out for in linux kernelville. for example if you
want to write a network card driver you'd look at how an existing
driver[1] interacts with the rest of the kernel and use that as an
example. same can be said everywhere else.

hope that helps,


[1] picking the right example is an exercise in itself, maybe look at for some idea of what could be a bad

R N G G "Well, there it goes again... And we just sit
I G G G here without opposable thumbs." -- gary larson
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:26    [from the cache]
©2003-2014 Jasper Spaans. hosted at Digital Ocean