From: LA Walsh <law@sgi.com>
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: To Linus: kdb in 2.4?
Date: Tue, 13 Feb 2001 13:53:52 -0800 [thread overview]
Message-ID: <3A89ACF0.142CB71B@sgi.com> (raw)
I'm wondering about the possibility of re-examining the idea of a kernel debugger
option distributed with 2.4.
I'm thinking that it could be a great teaching tool to break and examine structures,
variables, process states, as well as an aid to people who may not have a grasp
of the entire kernel but need to write device drivers.
It's easy for someone who's "grown up" with Linux to know it all so thoroughly
that such a tool seems fluff. But even the best mechanics on new cars use complex
diagnostic tools to do car repair. Sure there may be experts that designed the engine
that wouldn't need it, but large numbers of people need to repair cars or modify them for
their purposes. Having tools to aid in that isn't so much a crutch as it is
a learning tool. It's like being able to look at the characters of the alphabet
individually before one learns to comprehend the entirety of the writings of Buddha.
Certainly Buddha doesn't need to know how to read to know his own writings -- and
certainly, if everyone meditates and 'evolves' to their Buddha nature, they wouldn't
need to read the texts or recognize the letters either.
But not everyone is at the same place on the mountain (or even the same mountain, for
that matter).
In wisdom, one would, I posit, understand others are in different places and may
find it useful to have tools to learn to read before they comprehend.
Just my 2-4 cents on the matter...
--
L A Walsh | Trust Technology, Core Linux, SGI
law@sgi.com | Voice: (650) 933-5338
next reply other threads:[~2001-02-13 22:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-13 21:53 LA Walsh [this message]
2001-02-14 0:07 ` To Linus: kdb in 2.4? Jeff Dike
-- strict thread matches above, loose matches on Subject: below --
2001-02-13 23:14 Hacksaw
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=3A89ACF0.142CB71B@sgi.com \
--to=law@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox