Here are the answers:
1) In theory, up to 6 NuBus slots can be connected as 802.3 Ethernet
ports.
2) The current version of A/UX 3.0 is based on AT&T System V2.2 UNIX with
BSD 4.[23] extensions which include software signals and Internetwork
facilities. It conforms to SVID (System V Interface Definition) and SVVS
(System V Verification Suite). Also the System V3 Streams is supported
in A/UX.
3) The A/UX C compiler is driven from the standard AT&T System V.2 C
compiler. However, it is not ANSI C compatible.
4) The current version of A/UX does not support menu driven System
Administration type of function.
5) The remote system administration utilities like "rdump" and
"rrestore" are supported in A/UX.
6) Currently, A/UX 3.0 does not support Xerox's Ethernet (XNS), but a
third-party might have solution on it, for instance the BSD 4.3 UNIX
supports XNS protocol. Porting to any UNIX box should be easy.
7) RFC 1117 is pretty standard in Internet. It replaced the obsolete RFC
943. Basically, DDN Network Information Center (NIC) maintains the
assigned network number for the Internet community, Class A network is
assigned with numbers between 1 and 127, Class B network is assigned
with numbers between 128 and 191, and Class C is assigned with numbers
between 192 and 255. This is supported by A/UX.
8) RFC 951 (Bootstrap Protocol) describes an IP/UDP bootstrap protocol
(BOOTP) that lets a diskless client machine discover its own IP address,
the address of a server host, and the name of a file to be loaded into
memory and executed. The current version of A/UX 3.0 does not support
bootp.
9) The number of physical layer supported connections can be up to the
number of available NuBus slots. (That's 6 in Macintosh IIx.)
10) The number of sockets per session can be configured via "kconfig" to as
many as the user wishes. However, for the sake of performance, more
physical memory is needed if the number of sessions is increased. The
default is 16.
Article Change History:
19 Sep 1994 - Reviewed.
Support Information Services