This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Problem with VMware 2.0.4 and glibc 2.2.5


On Wed, Apr 10, H . J . Lu wrote:

> On Wed, Apr 10, 2002 at 02:55:18PM +0200, Jeroen Dekkers wrote:
> > On Tue, Apr 09, 2002 at 07:32:20PM -0700, H . J . Lu wrote:
> > > I got a strange problem with glibc 2.2.5-30 from Red Hat and VMware
> > > 2.0.4. I got
> > > 
> > > VMware Workstation PANIC:
> > > 
> > > AIO: NOT_IMPLEMENTED F(566): 1081.
> > > 
> > > and VMware quitted. glibc 2.2.4-19 works fine. Has anyone seen this?
> > 
> > I saw on it on debian-devel, it's a bug in VMWare because they relied
> > on the bug in nice(). VMWare provided patches, but those are only for
> > version 3 and because VMWare is non-free software, you can't patch it
> > yourself. IMHO some people need to get plex86 in an usable state,
> > relying on crappy non-free software is always bad. And for me a nice
> > second-hand machine with the same price as a VMWare license works
> > fine. :)
> > 
> 
> It looks like glibc 2.2.5 changed the ABI for nice. Shouldn't we give
> it a new version?

With such a change an the fact, that the old, wrong behaviour is
descriped in nearly every Linux documentation which contains a
description for nice, Yes, we should give it a new version.

 Thorsten

PS: I didn't hear anything about my nice patch, which makes the current
implementation really correct?

-- 
Thorsten Kukuk       http://www.suse.de/~kukuk/        kukuk@suse.de
SuSE Linux AG        Deutschherrenstr. 15-19       D-90429 Nuernberg
--------------------------------------------------------------------    
Key fingerprint = A368 676B 5E1B 3E46 CFCE  2D97 F8FD 4E23 56C6 FB4B


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]