On Tue, 13 May 1997, Robert Black wrote:

> To be fair we have had a few new drivers written but unless you use one of the
> affected cards you are unlikely to have noticed.

  Does that mean the autobuild kernels have new drivers in as they're 
written?  How else are we going to have noticed drivers changing?  

> 
> > Sorry to rant, but I really, really hope things get better.

  Well, to be quite frank from what I see things are going very well.
We have a very useable system (My kernel hasn't crashed since January - 
at least not without considerable stupidity on my part).

  The only niggle I have which hasn't been addressed lately (unless the
new console code has to come first) is the lack of development of X. It
still crashes regularly. When the size of the X server reaches ~20MB (I
have a 24MB system) it starts to go wobbly, then dies with a memory fault. 
  This happens about once a day

  Some programs don't even start up in X (i.e. sunsoft wabi)

Wabi 2.0 for SPARC-Solaris 
Copyright 1993, 1994 Sun Microsystems, Inc. All Rights Reserved.
Unrecoverable Error in Wabi
X Window System Error: BadValue (integer parameter out of range for 
operation) Sequence=451, Value=0xfc
Wabi will exit now.
Recursive Wabi Fatal Error
X Window System Error: BadValue (integer parameter out of range for 
operation) Sequence=451, Value=0xfc

and I can't change my ctrl and caps_lock keys about with xmodmap

garp:~> xmodmap capsctrl.xmodmap 
X Error of failed request:  BadValue (integer parameter out of range for 
operation)
  Major opcode of failed request:  118 (X_SetModifierMapping)
  Value in failed request:  0xfc
  Serial number of failed request:  16
  Current serial number in output stream:  16

  Oops!  I seem to have ranted.

  What I was originally going to say was that I'm very impressed with the 
professionalism and ability to get thgings done shown by the kernel team, 
and that's why I'm going to pop along to wakefield to see what new 
goodies they have in store.

Ale.