Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!sundc!citcom!peter From: peter@citcom.UUCP (Peter Klosky) Newsgroups: comp.unix.xenix Subject: Re: Does XENIX have sockets? Also, SCO 2.2 Upgrade A query. Message-ID: <36@citcom.UUCP> Date: Thu, 23-Jul-87 14:27:10 EDT Article-I.D.: citcom.36 Posted: Thu Jul 23 14:27:10 1987 Date-Received: Sat, 25-Jul-87 07:49:22 EDT References: <114@dalcsug.UUCP> Organization: Citcom Systems, Inc., Herndon, VA Lines: 27 In article <114@dalcsug.UUCP>, dalegass@dalcsug.UUCP (Dale Gass) writes: > Does XENIX support interprocess communication(IPC) through sockets? > What does XENIX use for interprocess stuff such as piping, etc? We are running SCO xenix; like you, we have a need for IPC. In our case we use the message passing operations msg_send, msg_receive, etc. As far as pipes go, they look just like they always have. In our case, we also have the "socket library" that comes with the TCP/IP protocol software we use for our ethernet. This came with the Micom/Interlan ethernet kit. It includes such system calls as bind, which mentions sockets in the man page. Here is my query: What has changed from 2.1.3 to 2.2.1 in the SCO product? We have just gotten the eight diskettes for the OS upgrade, but we harbor fears concerning the health of the Micom protocol software under the new OS version. Has anyone tried the OS upgrade yet? Does anyone know what they changed? In specific, did the file format change enough so that programs compiled with an old inode layout or readdir call will not work? Was I the only person to buy Micom instead of Excelan? Should I proceed to "Go for it, dude. No Maj." (Trying to get the silicon valley guy accent going, there.) -- Peter Klosky, Citcom Systems (materiel de telecommunications) seismo!vrdxhq!baskin!citcom!peter (703) 689-2800 x 235