From: Horst von Brand <vonbrand@inf.utfsm.cl>
To: jmerkey@comcast.net
Cc: linux-kernel@vger.kernel.org, jmerkey@drdos.com
Subject: Re: kallsyms 2.6.8 address ordering
Date: Thu, 19 Aug 2004 16:10:41 -0400 [thread overview]
Message-ID: <200408192010.i7JKAffv005998@laptop14.inf.utfsm.cl> (raw)
In-Reply-To: Message from jmerkey@comcast.net of "Thu, 19 Aug 2004 18:10:25 GMT." <081920041810.18883.4124ED110002BABC000049C32200748184970A059D0A0306@comcast.net>
jmerkey@comcast.net said:
> I've noticed that LKML of late is unresponsive to a lot bug posts
This is a community of _volunteers_, if you want your particular itch
scratched ASAP, shop for a maintenance contract.
> and
> that email is being blocked for a lot of folks.
I've been on this list for quite some time, and this is the very first time
I hear anything about such a thing. Care to elaborate?
[Yes, there are people who are almost universally on killfiles of the lead
hackers, but that is their own fault... and the list managers don't need
to bann anybody that way ;-]
> It smells like partisan
> politics based on economic motivations and its not really "open" any more
> when people stoop to this level of behavior.
Proof, please.
> That aside:
> kallsyms in 2.6.8 is presenting module symbol tables with out of order
> addresses in 2.6.X. This makes maintaining a commercial kernel debugger
> for Linux 2.6 kernels nighmareish.
If you want that fixed so you can make money off Linux, you'd better well
pay for the privilege of having your particular desires taken care of.
Probably off this list, as kernel debuggers in general are persona non
grata here, commercial software meddling with the inards of the kernel even
less wellcome.
[...]
> I don't expect a response so I'll keep coding around the broken Linux 2.6
> code but I wanted to post a record of this so perhaps someone will think
> about over-engineering systems which should be left alone.
This is probably just working to get the most out of the kernel, and the
constraint of "making kernel debuggers easy to write" just isn't in the
requirements. The kernel hackers (rightly so, IMVHO) reserve the right to
change interfases at the drop of a hat. If third parties get burned, just
too bad.
--
Dr. Horst H. von Brand User #22616 counter.li.org
Departamento de Informatica Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria +56 32 654239
Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513
next prev parent reply other threads:[~2004-08-19 20:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 18:10 jmerkey
2004-08-19 18:19 ` Christoph Hellwig
2004-08-19 18:30 ` Rik van Riel
2004-08-19 18:40 ` Richard B. Johnson
2004-08-19 19:00 ` Robin Holt
2004-08-20 11:42 ` Paulo Marques
2004-08-19 20:10 ` Horst von Brand [this message]
2004-08-19 18:26 jmerkey
2004-08-19 18:33 ` Christoph Hellwig
2004-08-19 19:14 jmerkey
2004-08-19 19:22 jmerkey
2004-08-19 19:24 jmerkey
2004-08-19 19:27 jmerkey
2004-08-19 19:42 ` David S. Miller
2004-08-19 22:07 ` Julien Oster
2004-08-19 22:40 jmerkey
2004-08-19 23:11 ` Francois Romieu
2004-08-19 22:43 jmerkey
2004-08-20 1:23 ` Horst von Brand
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=200408192010.i7JKAffv005998@laptop14.inf.utfsm.cl \
--to=vonbrand@inf.utfsm.cl \
--cc=jmerkey@comcast.net \
--cc=jmerkey@drdos.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
all inboxes | Powered by JetHome®