From: "Vladimir G. Ivanovic" <vladimir@acm.org>
To: "Dunn, Charles" <CDunn@empirix.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Kernel build problem
Date: Wed, 01 Sep 2004 09:23:55 -0700 [thread overview]
Message-ID: <200409011623.i81GNtSC011621@bach.leonora.org> (raw)
In-Reply-To: Your message of "Wed, 01 Sep 2004 11:57:06 EDT." <2A9AA9C52024F94A96634E39B9858FF166B969@empwilex1.empirix.com>
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.
--- Vladimir
--
Vladimir G. Ivanovic http://leonora.org/~vladimir
Palo Alto, CA 94306 +1 650 678 8014
>>>>> "cd" == Charles Dunn <Dunn> writes:
>> It is a pity that
>> RedHat do not want kdb, it means that RH users have a lot of trouble
>> trying to debug their systems. OTOH SuSE are happy to include kdb in
>> their distributions.
cd>
cd> I agree 1000%! I went around and around with RH sales about this. No
cd> complaints about the sales person, she really tried to get to the bottom
cd> of why this is the way it is, and she even found the answer.. In talking
cd> with her it was clear that in 99% of her conversations with RH engineers
cd> the attitude was one of: "Debuggers produce bad fixes. Always. Debuggers
cd> are evil."..
cd>
cd> This is like blaming forks for a person being overweight. Any tool can
cd> be used badly. No debugger is a substitute for understanding the code
cd> and producing a good solution. But a debugger can illuminate specific
cd> problem causes and shorten the debug cycle like few other tools can...
cd> This whole debugger thing with RH has been frustrating beyond words. We
cd> may even switch from RH to SuSe because of this, but mostly because RH
cd> seems to enjoy making life hard for embedded products makers who want to
cd> use RH. We are building VoIP test equipment and want to use RH as the OS
cd> inside.. They are making us jump through hoops that Microsoft hasn't
cd> even thought of yet. It's getting close to the point where it would be
cd> cheaper per box sold to have Windows inside than Linux.. Am I crazy or
cd> is that just a tad upside down from where Linux is supposed to be
cd> going???
cd>
cd> -Charlie Dunn
cd> Empirix Inc.
cd>
cd>
cd>
cd> ---------------------------
cd> Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.
next parent reply other threads:[~2004-09-01 16:24 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 ` Vladimir G. Ivanovic [this message]
2004-09-01 18:45 ` Kernel build problem Erik Mouw
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=200409011623.i81GNtSC011621@bach.leonora.org \
--to=vladimir@acm.org \
--cc=CDunn@empirix.com \
--cc=linux-scsi@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 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.