-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 26 June 2003 18:58, Patrick Shanahan wrote:

* Curtis Rey [06-26-03 20:34]:

...

Does or doesnt' 8.2 support pthreads? I keep getting confilct opinions about this so I was hoping someone might be able to give me some info on this.

ls -l /usr/lib/libpthread*

The reason I was asking was that I posted a comment on the TransGaiming website complaining the the latest offering does not handle pthreads. He had stated that SuSE didn't not have pthreading but RH 9.0 did. I thought he was full of it but thought it would be better to gather some consensus on this issue. Cheers, Curtis. P.S. Please correct me if I'm wrong but are not all futrue kernels (2.5/2.6) going to have pthreading? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE++8WDiqnGhdjCOJsRApNwAJ9gY9Rk2GE38JywveRu+cOGwA7mBQCePdUX M2Y3eZqT8nU8GO6lR6UzPT4= =2rYG -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 26 June 2003 19:20, Jim Norton wrote:

...

=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On Thursday 26 June 2003 18:58, Patrick Shanahan wrote:

...

* Curtis Rey [06-26-03 20:34]:

...

Does or doesnt' 8.2 support pthreads? I keep getting confilct opinions about this so I was hoping someone might be able to give me some info on this.

ls -l /usr/lib/libpthread*

The reason I was asking was that I posted a comment on the TransGaiming=20 website complaining the the latest offering does not handle pthreads. He h= ad=20 stated that SuSE didn't not have pthreading but RH 9.0 did. I thought he w= as=20 full of it but thought it would be better to gather some consensus on this= =20 issue.

Cheers, Curtis.

P.S. Please correct me if I'm wrong but are not all futrue kernels (2.5/2.= 6)=20 going to have pthreading?

Correct me if I'm wrong here, but PThreading is not a kernel function. PThreads are implemented in a library that can be downloaded and built just like any other library. And at its core, PThreads on Linux still use some form of Fork() anyways.

My bad. I was unsure as to what extent the libs and kernel interoped. This is what I was hoping to get clarification on. As it seems that TransGaming, or a fair amount of people that contrib to the users state the SuSE is different then others and it seem that 8.2 has specific issue, most around pthreading. I have a sneaking suspicion that they are RH focused and this maybe part (if not parcel) to some of the problems I'm having and their take that this is a SuSE issue. Cheers, Curtis. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE++8jfiqnGhdjCOJsRAuPQAJ9ZrJUJaz/U+Pez5lJcg1C21zKJ4ACdHFx8 zbS1EddwgEBnGhLdiJCXZ0g= =Lu+z -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 26 June 2003 19:42, Charles Philip Chan wrote:

On Thu, 26 Jun 2003 21:32:26 -0700

Curtis Rey wrote:

...

As it seems that TransGaming, or a fair amount of people that contrib to the users state the SuSE is different then others and it seem that 8.2 has specific issue, most around pthreading.

Why should it be different? pthread is part of glibc.

Charles

Now they (wulfram, TG rep of some sort) claims that we should "Update your version of glibc. The one that came with SuSE 8.2 is somewhat broken.". The fact of the matter is I tried it with the default and a stable upgrade rpm for SuSE. They seem to want to step around the issue. Hence why I'm gatthering info. I hate contributing to something and then hearing BS from them. They have a habit of doing this. I'm pressing them and they are telling me these sorts of things. I'm along your line of thinking... What difference should it make. I guess they think that since 8.2 had a pre-release it doesn't work but like I said, "there" latest version doesn't work with the defauilt (pre-release) or the update. I think they're getting annoyed - mainly because they just release a version they say will run a host of new games and people are having issues (and SuSE users have always had this complaint). I'm beginning to think the place is populated with RH fanboys, which is no prob - right up to the point where they start dissing my Distro. Then I tend to get a bit...., let's say antagonistic. Cheers, Curtis. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE++9OQiqnGhdjCOJsRAl3/AJ9zysQN4+EFo297vWqVAC9yy1tnRwCfS8H+ WaRiC9tvYo/LdFpBt6Tl2S8= =/2P0 -----END PGP SIGNATURE-----

On Fri, 2003-06-27 at 00:18, Curtis Rey wrote:

Now they (wulfram, TG rep of some sort) claims that we should "Update your version of glibc. The one that came with SuSE 8.2 is somewhat broken.".

The fact of the matter is I tried it with the default and a stable upgrade rpm for SuSE. They seem to want to step around the issue. Hence why I'm gatthering info. I hate contributing to something and then hearing BS from them. They have a habit of doing this. I'm pressing them and they are telling me these sorts of things. I'm along your line of thinking... What difference should it make. I guess they think that since 8.2 had a pre-release it doesn't work but like I said, "there" latest version doesn't work with the defauilt (pre-release) or the update. I think they're getting annoyed - mainly because they just release a version they say will run a host of new games and people are having issues (and SuSE users have always had this complaint). I'm beginning to think the place is populated with RH fanboys, which is no prob - right up to the point where they start dissing my Distro. Then I tend to get a bit...., let's say antagonistic.

I'm using the latest Winex and was curious as well. What I was able to determine is that the pthread library that Winex wants to use from the glibc is the NPTL (Native Posix Thread Library) that is currently being developed at Redhat. Apparently Redhat 9.0 shipped with a version of this library. SuSE decided not to implement the NPTL for this release and stayed with the LinuxThreads pthread library. Personally, from looking at how fast the developer is releasing bug fixes and new releases of the NPTL library, SuSE made the correct decision to not include it with 8.2. While the library may work well it is obviously not stable yet. So my take isn't that the glibc in SuSE is somewhat broken, it is that the glibc in Redhat is somewhat experimental and possibly buggy and instable. -- Paul Varner

On Fri, Jun 27, 2003 at 09:44:24AM -0400, Charles Philip Chan wrote:

On 27 Jun 2003 08:11:41 -0500 Paul Varner wrote:

...

What I was able to determine is that the pthread library that Winex wants to use from the glibc is the NPTL (Native Posix Thread Library) that is currently being developed at Redhat.

So Redhat is not using kernel threads after all. You can get NPTL here:

http://people.redhat.com/drepper/nptl/

...

So my take isn't that the glibc in SuSE is somewhat broken, it is that the glibc in Redhat is somewhat experimental and possibly buggy and instable.

OK, so they want you to use a non-standard library then turn around and call your distro broken if it doesn't use it- this make no sense.

Not exactly. WINE does not use a thread library usually, it implements its own threading and supplies some pthread functionality. Up to some months ago it was using a hidden feature of glibc, which was removed by glibc 2.3. It was fixed in newer WINEs. WineX has similar problems and they probably need to be fixed there too. Ciao, Marcus

On Fri, 2003-06-27 at 15:44, Charles Philip Chan wrote:

On 27 Jun 2003 08:11:41 -0500 Paul Varner wrote:

...

What I was able to determine is that the pthread library that Winex wants to use from the glibc is the NPTL (Native Posix Thread Library) that is currently being developed at Redhat.

So Redhat is not using kernel threads after all.

Read the pdf white paper they have there. Specifically chapter 6 "Kernel improvements". But it's (supposedly) ABI compatible with the older linuxthreads implementation.