burrough@bronze.ucs.indiana.edu (michael burroughs) (10/09/90)
If the SCO machine that you are using is going to be the backbone of the
LAN, I would suggest using a Lan Manager based local area network. SCO
seems to have a seemless interface to Lan Manager and OS/2 LAN
environments. I have to admit that my knowledge of this arangement is
textbook only. I have an SCO system running on a network with Novell
LAN's. Transferring files between the Novell LAN and the SCO system is
kludged together at best, requiring a second ethernet card and the DOS
emulation capabilities of SCO. This solution is also fairly slow. In
any case I would stay with a LAN solution that allowed you to stay with
ethernet connectivity. If I were desgning the system I would use an
OS/2-DOS-SCO Unix solution. Of course, these are my opionions and don't
reflect the opionions of my employer.
**************************************************************
* Michael Burroughs (812)855-8478 *
* *
* LAN Support & Development Group / UCS Networks Division *jbreeden@netcom.UUCP (John Breeden) (10/09/90)
In article <63319@iuvax.cs.indiana.edu> burrough@bronze.ucs.indiana.edu (michael burroughs) writes: >If the SCO machine that you are using is going to be the backbone of the >LAN, I would suggest using a Lan Manager based local area network. SCO Lan Manager is a possibility but I don't recall SCO supporting LMX (Lan Manager/Unix). Both AT&T and HP do support it. AT&T runs LMX over both ISO and Netbui, HP is running over IEEE TCP-IP. Either one of these would call for replacing SCO Unix with either SysV or HP/UX. When both SCO and AT&T start shipping their Intel binary compatable versions of Unix (R4?), then AT&T's LM/X is supposed to run on SCO. Of course AT&T has a "SystemPro" solution too - StarServer E - 106mip multiproccesor PC. -- John Robert Breeden, netcom!jbreeden@apple.com, apple!netcom!jbreeden, ATTMAIL:!jbreeden ------------------------------------------------------------------- "The nice thing about standards is that you have so many to choose from. If you don't like any of them, you just wait for next year's model."
j_rodin@hpfcso.HP.COM (Jon Rodin) (10/10/90)
> >Both AT&T and HP do support it. AT&T runs LMX over both ISO and Netbui, HP >is running over IEEE TCP-IP. Either one of these would call for replacing >SCO Unix with either SysV or HP/UX. > HP's LM/X product will run over SCO Unix.
jabusch@osiris.cso.uiuc.edu (John Jabusch) (10/11/90)
ma176f1@sdcc14.ucsd.edu (Sean Kelly) writes: >IBM PC/XTs and upgrading to a Compaq SystemPro using SCO Unix. >The problem is that with all this extra power, they want to take >full advantage of it with a LAN. The question is: Which one? >What needs to be connected: > Compaq SystemPro (as backbone if you will) > using SCO Unix > VT100 or other terminals (Suggestions?) > C.Itoh & Epson Printers > HP LaserJet Series III > IBM PC/XTs as workstations. > Compaq 286s as workstations. >Dealers have suggested everything from EtherNet to Novell. Since One thing that hasn't been mentioned yet is NFS. If SCO Xenix supports NFS, you can get Sun's PC-NFS for the PC/XTs and Compaq 286s, and run them as client workstations with it. Sun's PC-NFS package provides most of the same functionality of your typical Novell/3Com/Banyan networks, plus is more smoothly integrated into the Unix environment you obviously prefer. It might be your best choice. (Over Ethernet cabling, of course!) John W. Jabusch INTERNET: jabusch@cerl.cecer.army.mil MILNET: jabusch@osiris.arpa US Mail: USA CERL, PO Box 4005 Newmark Drive, Champaign, Il 61824-4005 Voice/Phone: Commercial (217) 352-6511 -- John W. Jabusch INTERNET: jabusch@cerl.cecer.army.mil MILNET: jabusch@osiris.arpa US Mail: USA CERL, PO Box 4005 Newmark Drive, Champaign, Il 61824-4005 Voice/Phone: Commercial (217) 352-6511
pat@hprnd.rose.hp.com (Pat Thaler) (10/16/90)
> > Dealers have suggested everything from EtherNet to Novell. > ---------- I wanted to point out that Ethernet and Novell cover different parts of your LAN implementation and don't conflict. ISO defines an LAN (or any network) architecture as partitioned into seven layers. Ethernet/802.3 covers the bottom two layers, the part generally implemented in hardware. Other possibilities for these layers exist including 802.5 and FDDI. Within Ethernet/802.3 several kinds of media supported (by changing part of the bottom layer) including coax, twisted pair, and fiber. To communicate over your LAN, you need to put some upper layers over the bottom two layers. These are usually implemented in software (or firmware). Possibilities here include Novell, TCP/IP, OSI, and a host of others. Pat Thaler