Newbies as me do care about documentation ;-) The Linux kernel is
getting more complex over time, and I appreciate some kind of
architectural docs to know more about the inner workings. Personally, I
don't have all the time I would like to explore and investigate, so a
50,000-feet-point-of-view and some detailed documentation about VM,
scheduler and net are welcome.
Kernel experts as you (Linus, Andrew, Alan, Russell, Jeff and many
others whose names I must leave out as I don't have space to name them
all) probably know the inner workings better than anyone as they work
with it every day, but people new to kernel hacking need some starting
point.
> Personally, I don't write documentation. I don't much even write comments
> in my code. My personal feeling is that as long as functions are small and
> readable (and logical), and global variables have good names, that's all I
> need to do. Others - who do care about comments and docs - can do that
> part.
Well, some functions and variable names may seem readable and logical to
some, but it takes time for me to decipher some of them :-)
-- Please AVOID sending me WORD, EXCEL or POWERPOINT attachments. See http://www.fsf.org/philosophy/no-word-attachments.html Linux Registered User #287198- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/