From: Olaf Dietsche <olaf+list.linux-kernel@olafdietsche.de>
To: ram mohan <madhaviram123@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux - open design??
Date: Tue, 14 Dec 2004 13:13:09 +0100 [thread overview]
Message-ID: <87u0qpgjsa.fsf@goat.bogus.local> (raw)
In-Reply-To: 20041214040125.70151.qmail@web90010.mail.scd.yahoo.com
ram mohan <madhaviram123@yahoo.com> writes:
> When we say Linux is open source and we have the sites
> where we can download the source from, why is not
> linux design (High Level and Low Level) not that well
> publicised? (Or is it that I am not aware of - in
> which case I would like to know where it is.)
> I am looking for a traceability matrix- where I start
> with requirements of Linux, dig into the
> design(HLD/LLD) and then the source.
There's no high level overview, AFAIK. But there are many documents
out there, describing various parts of Linux. Many of them are
outdated, but you can get an idea, how Linux works.
Linux Kernel 2.4 Internals <http://www.tldp.org/LDP/lki/>
Linux Kernel Hackers' Guide <http://www.tldp.org/LDP/khg/>
Linux Memory Management: <http://www.linux-mm.org/>
The Linux Kernel API <http://kernelnewbies.org/documents/kdoc/kernel-api/linuxkernelapi.html>
The Linux Kernel (based on 2.0.33) <http://www.tldp.org/LDP/tlk/>
and all below linux/Documentation, of course. However, if you want to
learn about the current state of Linux, you won't get around reading
the source.
Regards, Olaf.
next prev parent reply other threads:[~2004-12-14 12:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-14 3:48 Tilt Wheel Mouse Drivers Missing mike cox
2004-12-14 4:01 ` Linux - open design?? ram mohan
2004-12-14 4:54 ` Zwane Mwaikambo
2004-12-14 5:01 ` Kyle Moffett
2004-12-14 9:01 ` P.O. Gaillard
2004-12-14 8:56 ` Bernd Petrovitsch
2004-12-14 11:26 ` Helge Hafting
2004-12-14 12:13 ` Olaf Dietsche [this message]
2004-12-16 9:22 ` Got Info - Linux - open design ram mohan
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=87u0qpgjsa.fsf@goat.bogus.local \
--to=olaf+list.linux-kernel@olafdietsche.de \
--cc=linux-kernel@vger.kernel.org \
--cc=madhaviram123@yahoo.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.