> AFAIK, Mike has offerred several things to try, but has not tried
> doing any firsthand debugging. I certainly don't fault him for
> that--- I don't think anyone should attempt debugging unless they've
> got something they can witness the problem on.
It also requires hardware, familiarity, and the actual
distribution software to do that. I know for a fact that Mike runs SuSE
(still?), so Redhat may not be in one of his testing platforms.
> I don't mean to imply that I know a lot about Red Hat. I don't,
> partiuclarly. It's just the distribution I use. Unfortunately, I
> don't know python. If I did, perhaps I could've submitted a patch by
> now. My help so far has been with bug reports and responding to more
> detailed questions about the behavior.
Ok, let's not turn this into a 'my vi is better than your emacs'
war. Let's be constructive.
By the end of this weekend, I will have a full bug-reporting
mechanism up, the FAQ online, and the links/contact pages will be updated
as well. This should make that part of things easier. I made a boatload of
changes to the site over the past week or so, and fixed a bunch of errors
in the code that drives it. I'm fixing a bunch more this weekend.
> Primarily, I get it from IDC, PC Data, Netcraft, Corel, Red Hat,
> anecdotes, and personal observation.
Noted, let's move forward with fixing the problem.
Let's identify the pieces that result in the problem manifesting
itself. So far we have Redhat 7.0. What version of Python is on that? What
version of gcc comes *WITH* it? (not the udpates). We'll go from there.
/d
