Ron Heron wrote:
Michael, you obviously didn't take this mail for what it was intended. Please read my comments to yours. I was looking for positive feedback.
Me too.
I cannot agree. Personal observation. I had fewer problems on older releases.
Ah, you see? Not very useful statement. Not even an example was given.
I was specifically addressing upgrades. Problems are problems. I post problems and responses to this list. It is for that. I was addressing the fact that it seems to me, that the SuSE upgrades are unreliable.
And your point is? People will always have problems. Try to make just ONE program so usefriendly that there will be no questions at all. I'm trying this right now for the ORacle 8.1.6 installation, and the longer I think about every single step the more desperate I get. I cannot do it. Someone's gonna cry for help whatever I do. So I still consider your statement useless. I promise you'll find lots of problem reports here for all time this list exists.
I have had no problems working with kernels on past SuSE distros, or on other distros. Thanks, but I do know what I am doing.
Then you will have no problems getting it to work, period. I'm the example that shows this is true. I DO use SuSE Linux, you know...
b) Correct, the stock 2.2.16 is next to unusable. This is why the SuSE 2.2.16 is a 2.2.16 + several MB of patches, for both stability and features. Where is the SuSE 2.2.16?
How about ftp://ftp.suse.com/pub/suse/i386/update/6.4/kernel-2.2.16/
??? Thanks for the detailed bug report. Again, a general statement. I will post details when I start squishing the problems. But, to answer the sarcasm, why didn't SuSE include mpg123 if there are at least three packages that require it?
Which package requires it? Did you file a bug report? I've had no problems listening to any mp3's, don't know which package yo used. By the way, mpg123 is in 7.0, don't know about 6.4.
It wasn't pretty :) But - did you read what I said here? It was on the SuSE mailing list where I learned that Yast or Sax2 was wiping out the .Xsession file from the root account. I replaced that with a backup, and problem solved. Not a big deal. The big deal was that the X would not even start using the SuSE upgrade.
Did you file a bug report (feedback@suse.de)? Of course it's bad.
Now, as a suse employee, do you have anything constructive to offer? I am trying to learn linux,
I have a lot of constructive help to offer, even setting up somebodys Oracle server for free (plus data migration) on a box 10000 km away over the Internet on the weekend. But, I demand a constructive contribution from you as well. You get what you give, at least from me. Other people will always help you, regardless of what you do, and I guess that's better for business.
and come up with a nice, stable box. I also use a test box for playing around on. Your message says "F-u, you're a moron, if you want our software, don't mess with it, and don't expect it to be our fault when it doesn't work" Is that the way you meant it to read?
I simple read from your email, without knowing you. -- Michael Hasenstein http://www.suse.de/~mha/ SuSE Linux AG, Nuernberg (Germany) SuSE Inc., Oakland, California (US) -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq