Hi Ben, I do not think it is a matter of sticking up for anyone. I did not say that you as a development team should switch it out like we had to do.
I simply said maybe the INFORMATION could be passed to the mpg321 Team. What they do with that information to determine what about that particular lib file made the difference is up to them. We do not pretend to know what about this lib file change-out made the difference, but something about it did. It was just a snipet of information, nothing more. If the mpg321 Team can't use the information, or are already onto the specific issues that make theirs (the version running under 8.2) not work on some corrupted files, then that's great, but if we all keep what information we glean through trial and error from each other, where will we be. Many sets of eyes are better than a few, or one. I am not saying to go BACK to anything...I am saying that on 8.2 this made a difference for us...and it was not on only one Mandrake 8.2 computer, but TWO. Like I said, I can not even begin to speak for anything in 9.0, because I don't have that version. What you all do with this small tidbit of information is your business. But don't blow folks off for sharing a piece of information that worked for them, not only on one computer, but two! and at least find out why! Thanks for taking the time to write. Bambi Ben Reser wrote: > On Mon, Sep 30, 2002 at 10:18:18PM -0400, Fran Parker wrote: > >>Why thank you so much for your wonderful attitude. >> >>This did work. I do not have 9.0, so I can't talk for 9.0. >> >>And despite your smug attitude Han, this fix did work quite well with >>8.2. If all developers were as closed minded as you are, it is no >>wonder Linux distros are becoming so autonomous and not learning from >>either other where appropriate. >> >>This cooker does deal with updates to 8.2 as well as 9.0 does it not? >> >>Thanks for nothing, Han. >> > > I can't believe I'm going to do this but I'm gonna stick up for Han > here. He wasn't saying we shouldn't look at RedHat to see why their > stuff works. While granted that the major on this library is the same. > Just blindly switching it out doesn't really resolve the problem. > > I'm not sure I'd call it the dumbest piece of advice. But it's > certainly not the resolution to your problem. At best it helps point > the way to where the problem really is. > > If indeed the problem is replicatable on other machines and going back > to 2.2.4 solves it. Then we'll need to look at the differences between > those version to determine what the problem really is. > >
