Date: Tue, 28 Feb 1995 18:30:38 -0800 From: hasty@netcom.com (Amancio Hasty Jr) To: hackers@FreeBSD.org Subject: iBCS2 and word perfect... Message-ID: <199503010230.SAA06929@netcom14.netcom.com>
next in thread | raw e-mail | index | archive | help
I have not been able to download the 35MB yet... So while I am waiting for my next window of opportunity to download the mother of all word processors. I decided to take a look at the Linux iBCS2 implementation: The local X interface is simplistic. It assumes only one local X server exists and assumes that the pathname of the Unix domain socket for local connections is always /tmp/.X11-unix/X0. The SCO code opens both /dev/X0R and /dev/spx, writes a single byte to /dev/X0R, reads a message from /dev/X0R with getmsg then writes this message to /dev/spx with putmsg and closes /dev/X0R. This establishes the /dev/spx file descriptor as a connection to the X server listening on /dev/X0R. We ignore all activity on the /dev/X0R device (hence it is a link to /dev/null), getmsg and putmsg are stubbed so don't do anything and opens on the /dev/spx simply replace the open inode with a socket connected to the X server's Unix domain socket. At some point in the future we will implement a simple minded /dev/X* driver that returns some form of id via the getmsg which can then be passed to /dev/spx with putmsg and which will allow /dev/spx to connect to the relevant X server. This will only happen if someone actually *needs* multiple local X servers... ------------------ So perhaps someone out there can try the above suggestions and report back ... Tnks, Amancio
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199503010230.SAA06929>