linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Nick Newcomb" <nranewcomb@hotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Design Level Documentation for the Linux kernel (V2.6)
Date: Wed, 15 Jun 2005 00:34:26 +0000	[thread overview]
Message-ID: <BAY108-F279928792F980CAFB2AEDCDF20@phx.gbl> (raw)

Hi, I'm working with the Software Revolution and I thought you guys might 
like to know that we just completed the automatic generation of a full, 
design-level documentation of the LINUX kernel and associated sub-systems. 
This documentation set is made up of hyperlinked graphics and text documents 
of all the major subsystems and all of the source code fields and functions 
and is organized by complexity and file-system location. It covers the Linux 
kernel, memory management, file-system, security, cryptography, 
initialization, drivers, architecture and interprocess communication 
subsystems. Furthermore, we're offering this for... well free. I just 
thought it was something maybe you guys could use. If you would like to view 
this information, just go to:

http://www.softwarerevolution.com/jeneral/open-source-docs.html

Any questions or comments anyone might have are more than welcome. Thanks 
for your time and we hope you'll find our services useful.

~ Nick w/ TSRI



             reply	other threads:[~2005-06-15  0:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-15  0:34 Nick Newcomb [this message]
2005-06-15  1:13 ` Design Level Documentation for the Linux kernel (V2.6) Parag Warudkar
2005-06-15  1:33   ` Peter Williams
2005-06-15  1:46     ` Parag Warudkar
2005-06-15  7:00     ` Christoph Hellwig
2005-06-15  8:11       ` Geert Uytterhoeven
2005-06-17  1:48     ` Coywolf Qi Hunt
2005-06-15  1:15 ` Kyle Moffett
2005-06-15  9:19 ` Denis Vlasenko
2005-06-17  1:59   ` Coywolf Qi Hunt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BAY108-F279928792F980CAFB2AEDCDF20@phx.gbl \
    --to=nranewcomb@hotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).