Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site nrcvax.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!vax135!cornell!uw-beaver!tektronix!hplabs!sdcrdcf!psivax!nrcvax!blc From: blc@nrcvax.UUCP (Bruce Carneal x313) Newsgroups: net.lan Subject: Re: socket library under System V? Message-ID: <229@nrcvax.UUCP> Date: Thu, 22-Aug-85 06:03:40 EDT Article-I.D.: nrcvax.229 Posted: Thu Aug 22 06:03:40 1985 Date-Received: Sun, 25-Aug-85 13:45:48 EDT References: <284@SCIRTP.UUCP> <3070002@csd2.UUCP> <413@cheviot.uucp> Reply-To: blc@nrcvax.UUCP (Bruce Carneal x313) Organization: Network Research Research Corp. Oxnard,CA Lines: 30 Keywords: socket NRC FUSION Summary: [] NRC FUSION implements a superset of the BSD4.2 socket abstraction mapping bind(), connect(), accept(), and friends into ioctl() calls. Socket() requires use of an open() call as well as an ioctl() and returns a character device file descriptor clothed with the indicated protocol. The other library routines do little more than marshall parameters and call ioctl(). This approach is adequate for all current FUSION UNIX ports including v7, SysIII, SysV, BSD4.X, Xenix, Venix, Ultrix, and UTS. ("From now on, consider it standard". :-)) FUSION uses a similar approach under VMS and MS/DOS. Only the OS escapes/entrypoints change. I suspect that anyone not having access to or inclination to change kernel sources will have followed a similar ioctl() approach. If you need or want further information get in touch. Trademark credits: Ultrix, Xenix?, Venix, UTS?, FUSION and UNIX to Digital Equipment, Microsoft, Venturecom, Amdahl, Network Research and ATTIS? respectively. UUCP: {sdcsvax,hplabs}!sdcrdcf!psivax!nrcvax!blc ucbvax!calma!nrcvax!blc I speak for myself alone.