🚀 go-pugleaf

[]

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.