^S/^Q problem in SV/AT 2.4 (a resolution!)

[John Plocher]

In article <May.25.18.41.10.1989.3473 at geneva.rutgers.edu> hedrick at geneva.rutgers.edu (Charles Hedrick) writes:
>Do you fix kernel problems on Suns too?

No, I am in the Portable Window Systems group.  Our charter is to make
Sun's windowing software portable between different OS's and hardware
platforms.  Often this means actually porting the code to the new
platforms, but we would like to focus on portability issues rather than
porting issues.

In practice, we are porting.  Right now we are involved in porting the
X11/NeWS Merged window server to AT&T Unix Vr3 on the WGS 6386.  We are
using both the 1600x1200 Monochrome Cornerstone Video System and the
EGA/VGA.

My development environment (there are 6 of us) consists of a 25Mhz 386
clone, lots of disk space, and a Sigma VGA.  Other setups we have are
Compaqs (W/Compaq VGA) and AT&T WGS 6386s (W/AT&T EGA & VGA).  Everyone
else is using ATT Unix V/386 3.2 with Micom/Interlan TCP/IP boards and
software.  I am using Wollongong TCP/IP + NFS (Love it).  I'm not
using Everex Unix because they don't have TCP avaliable yet.  Ditto
ISC.

By the end of the Summer we should be running this stuff on a 386 under
Vr4 :-) - I will keep the group posted on that adventure!

The server we are developing uses a "standard" Console Driver ioctl()
to get the resolution et al from the driver, so it should run under ISC
and Everex's Unix also.  This is an AT&T Unix specific ioctl which
queries the console driver about the hardware resolution of the
screen.  Another ioctl which manages the virtual consoles is also
utilized.  Vendors are free to implement ioctls however the wish, so
this isn't a standard as such, but ISC and Everex shouldn't have
changed things that much from the ATT supplied descriptions...

   -John Plocher