[comp.windows.x] X on Xenix/386

dyer@spdcc.UUCP (02/17/87)

>NOOOOOOOOOO!!!!!!!  DO NOT COUNT ON X ONLY RUNNING ON 4.X MACHINES!!!!!
>
>We have ported X to System V Xenix/386, and intend on doing more of the
>similar.  If you want your application to run in all environments, follows
>standard "portable code" procedures and use generic calls, or use ifdefs, etc.

I'd like to know what IPC model(s) you chose for implementing X on System V
Xenix/386.  Do you rely on external network cards like the Excelan TCP/IP
board for all the IPC?  I had understood that using their on-board 'sockets'
for IPC within a single machine was unusually inefficient (warning, this
was gleaned from an Excelan techie at Uniforum, and not from direct experience.)
Do you optimize intramachine operations using System V facilities like
shared memory?

Finally, my Intel 386 card is coming soon; once I get my hands on SCO's
386 Xenix, how can I then obtain X?
-- 
Steve Dyer
dyer@harvard.HARVARD.EDU
dyer@spdcc.COM aka {linus,wanginst,bbnccv,harvard,ima,ihnp4}!spdcc!dyer

jdm@gssc.UUCP (02/18/87)

i appologize for the wording in my previous posting regarding GSS's X 
implementation.  i should have said, "we are porting," rather than, 
"we have ported."  

we *did* have a running demonstration running at uniform using microsoft system 
v xenix/386, but this is not a released product.  i cannot divulge any info on
the status of this product or any of the technical details.  your best bet is
the trade rags since uniforum.

IMPORTANT: my posting was *not* intended to make any pre-mature announcements, 
but rather to address the question of, "is it okay to write my X application to
never run on anything but BSD?"

the obvious answer is, "no."  even though certain aspects of most any 
application - especially X applications - must utilize certain OS dependent
functions, such as sockets, it is wise to isolate these as much as possible for
ifdefing in a similar function on another OS.  

'nuff said.

-- 
-- jdm
in real life:  John D. Miller, Graphic Software Systems, Inc., Beaverton OR
...!{tektronix!verdix}!sequent!gssc!jdm