From: Erik Mouw <erik@harddisk-recovery.com>
To: "Vladimir G. Ivanovic" <vladimir@acm.org>
Cc: "Dunn, Charles" <CDunn@empirix.com>, linux-scsi@vger.kernel.org
Subject: Re: Kernel build problem
Date: Wed, 1 Sep 2004 20:45:57 +0200 [thread overview]
Message-ID: <20040901184557.GG7005@harddisk-recovery.com> (raw)
In-Reply-To: <200409011623.i81GNtSC011621@bach.leonora.org>
On Wed, Sep 01, 2004 at 09:23:55AM -0700, Vladimir G. Ivanovic wrote:
> To be fair, it's not really a Red Hat issue, but rather Linus's belief
> that debuggers lead to patching symptoms rather than fixing the
> underlying problem.
FYI, here is the complete quote:
"The debugger is akin to giving the _rabbits_ a bazooka. The poor wolf
doesn't get any sharper teeth. Yeah, it sure helps against wolves.
They explode in pretty patterns of red drops flying _everywhere_. Cool.
But it doesn't help against a rabbit gene pool that is slowly
deteriorating because there is nothing to keep them from breeding, and no
darwin to make sure that it's the fastest and strongest that breeds.
You mentioned how NT has the nicest debugger out there.
Contemplate it."
- Linus Torvalds
Feel free to start a discussion about this on linux-kernel, but be
forewarned that it usually ends in a flamewar.
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
next prev parent reply other threads:[~2004-09-01 18:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2A9AA9C52024F94A96634E39B9858FF166B969@empwilex1.empirix.com>
2004-09-01 16:23 ` Kernel build problem Vladimir G. Ivanovic
2004-09-01 18:45 ` Erik Mouw [this message]
2004-09-01 18:50 ` Bryan Henderson
1999-06-11 10:44 Kernel Build Problem Andrew Linfoot
-- strict thread matches above, loose matches on Subject: below --
1998-12-22 23:26 kernel build problem Alex deVries
1998-12-23 4:44 ` ralf
1998-12-24 15:31 ` Alex deVries
1998-12-25 17:14 ` ralf
1998-12-26 4:08 ` Alex deVries
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=20040901184557.GG7005@harddisk-recovery.com \
--to=erik@harddisk-recovery.com \
--cc=CDunn@empirix.com \
--cc=linux-scsi@vger.kernel.org \
--cc=vladimir@acm.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 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.