On Thu, 2006-08-17 at 19:40 -0700, PerfectReign wrote:

Jan Engelhardt wrote:

...

...

Hi Everyone

Could someone please help me to or give me a possible solution to this problem which I am encountering when trying to update Suse 10.1 with "software upater"?

Stop hijacking threads.

So in order to fix my problems with YaST and Zen, I need to stop hijacking threads?

Hmm. Interesting advice. Not quite sure how it helps, but I'll give it a try.

So how about everyone's favorite t-shirt? What is the best t-shirt slogan you've seen today?

On the front: Stop HI-jacking threads On the back: Stop top posting :-) -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu August 17 2006 19:40, PerfectReign wrote:

Jan Engelhardt wrote:

...

...

Hi Everyone

Could someone please help me to or give me a possible solution to this problem which I am encountering when trying to update Suse 10.1 with

"software upater"?

...

Stop hijacking threads.

So in order to fix my problems with YaST and Zen, I need to stop hijacking threads?

Hmm. Interesting advice. Not quite sure how it helps, but I'll give it a try.

When a thread is highjacked the archives get seriously hosed. If someone starts a thread, such as "Xserver fails with new fglrx drivers" and then some, two or three posts (pick any number) with a new subject heading (such as) "Apache won't load my media files" then how is one supposed to A) continue to troubleshoot the original request to help figure out why ATI drivers don't work well with others (an ongoing problem), B) how does one help the guy with his Apache problem without confusing the matters more - because there's the potential for a mix-mashed thread rambling form ATi issue to Apache issue and back and forth, to and fro, etc.., etc.., yada, yads.... And finally C) wherein many refer to the mail list archives for answer that have often been answered numerous times and feel the need not to post over the desire to do a search in the archive to see if the answer is indeed there - hence the hosing of the archives. Let's say I do a search for "Joystick config in Wine" and indeed I find a thread dealing with this. But low and behold after two posts, one stating the problem and another asking for the contents of the debug output file, the third message in the thread isn't about the original subject at all but about "Xen kernel module fails and spits out kernel oops"! Well I've just wasted my time trying to search the archive for my problem and if someone seaches the archive for "Xen and kernel oops" will find it, but mixed in with other things they don't care about - that also depends on the type of search they do. If they just search the starting threads they'll never find an answer for Xen and kernel oops because it buried under a thread that started out with "Joystick config in Wine" - the answers is indeed there but not as easily found as if it (Xen and kernel oops) had it very own thread. The fourth thing is that it is in a way considered rude and by many unprofessional - the mark of an amateur and/or someone that could give a damn about others and just wants everyone to drop what they're doing and answer their question - screw the other guy type of mentality (not suggesting this is you - however if the shoe fits.... :) ). So, please take this into consideration when you need to post to get answers (it also - highjacking - tends to get your question ignored, at least by many of the true guru's on the list). HTH and Cheers. Curtis. - -- Spammers Beware: Trespassers will be shot, survivors will be shot again! "The only problem with capitalism is capitalists, they're so damn greedy!" President Herbert Hoover -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFE5S+77CQBg4DqqCwRAvaDAKDnMHXsnwyjZy8qqq0iJJznTKn4RgCgyAu7 6UjNZqJInAsY9oH5U1gi3vg= =TL9R -----END PGP SIGNATURE-----