predict@charon.unm.edu (Andrew R. Large) (09/04/88)
I am in the processing of designing a ThinWire Ethernet for our building. We currently have two Vax 11/730s, an IBM PC/RT, a Tandy 3000 (I think), and several flavors of PC clone, PC to PC/AT. We are likely to add a Sun and an Apollo in the near future. One of the 730's is running mt Xinu 4.3 BSD. The other is running VMS 4.7. The RT is running AIX. The Tandy is running SCO Xenix 286. For the VMS machine, I'm looking into the CMU VMS TCP/IP package. I'm not sure about the RT yet -- I'm guessing that software is there and I just need to figure out how to use it. My big question is ``What do I need in order to get the Tandy on an Ethernet?'' I would assume the 3COM card. What about software? Does anyone sell a reasonably priced TCP/IP package for Xenix 286, with rlogin or telnet and ftp (like maybe CMU, since I forgot to ask them)? Advice greatly appreciated ...
predict@charon.unm.edu (Andrew R. Large) (09/04/88)
Nuts, didn't get my signature on the last article ... here it is.
-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-
* Andrew R. Large *
** (work) 505/255-8611 ------| Univ of New Mexico EECE Department **
*** (home) 505/888-4010 |---> Management Sciences, Inc. [MSI] ***
**** _Babooshka!_ ****
*** Usenet: {convex,gatech,ucbvax,csu-cs,anl-mcs}!unmvax!charon!predict ***
** Internet: predict@charon.UNM.EDU **
* If I am quoted, my employers will deny my existence. *
-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-davidsen@steinmetz.ge.com (William E. Davidsen Jr) (09/09/88)
I have been running Excelan for several years now. Has telnet, rlogin,
ftp. Supports getty on Enet lines, and uucp over Enet with no support
needed on the other end. I knocked out a quick and dirty SMTP server in
an afternoon, but I believe that the current software supports it out of
the box.
This stuff has been dead reliable for me.
--
bill davidsen (wedu@ge-crd.arpa)
{uunet | philabs}!steinmetz!crdos1!davidsen
"Stupidity, like virtue, is its own reward" -mejbayer@ispi.UUCP (id for use with uunet/usenet) (09/09/88)
In article <3606@charon.unm.edu>, predict@charon.unm.edu (Andrew R. Large) writes: > I am in the processing of designing a ThinWire Ethernet for our building. > The RT is running AIX. The Tandy is running SCO Xenix 286. > > My big question is ``What do I need in order to get the Tandy on an Ethernet?'' Exelan has a good line of products which put Ethernet and TCP/IP on Xenix. I have sold their stuff to several companies who are all pleased with it. Jonathan Bayer Intelligent Software Products, Inc.
sandy@turnkey.TCC.COM (Sanford 'Sandy' Zelkovitz) (09/11/88)
> Exelan has a good line of products which put Ethernet and TCP/IP on Xenix. I > have sold their stuff to several companies who are all pleased with it. > > Jonathan Bayer > Intelligent Software Products, Inc. I truely agree with you about The Excelan Hardware and software; however, you would think that after MANY requests from customers about supporting "compatible" NFS, they would. Like many other companies, we have Sun workstations and VAXs running under NFS; however, our 286 and 386 systems cannot share that luxury. Sanford ( Sandy ) Zelkovitz
dyer@spdcc.COM (Steve Dyer) (09/11/88)
In article <1860@turnkey.TCC.COM> sandy@turnkey.TCC.COM (Sanford 'Sandy' Zelkovitz) writes: >I truely agree with you about The Excelan Hardware and software; however, >you would think that after MANY requests from customers about supporting >"compatible" NFS, they would. Like many other companies, we have Sun >workstations and VAXs running under NFS; however, our 286 and 386 systems >cannot share that luxury. If you understood what it meant to provide a "compatible" NFS client, you would understand that Excelan, which provides only a TCP/IP card with a set of private utilities, has no access to the higher NFS/RPC layer which must necessarily be integrated tightly into the kernel. A device driver is too low an interface, and without UNIX sources, that's all they have to work with. It would be much less work to provide an NFS server so that your XENIX disks could be made accessible to your Suns and VAXes; however, that's probably not what you're looking for. I know that SCO is working on a port of NFS to their version of XENIX/UNIX (probably the Lachman Sys V stuff, although I could be wrong), and at that point you could start asking the question you ask here, since Excelan's job would be to splice their IP processing beneath the kernel's RPC layer. -- Steve Dyer dyer@harvard.harvard.edu dyer@spdcc.COM aka {harvard,husc6,linus,ima,bbn,m2c,mipseast}!spdcc!dyer
sandy@turnkey.TCC.COM (Sanford 'Sandy' Zelkovitz) (09/12/88)
> If you understood what it meant to provide a "compatible" NFS client, > you would understand that Excelan, which provides only a TCP/IP card with > a set of private utilities, has no access to the higher NFS/RPC layer which > must necessarily be integrated tightly into the kernel. Steve, I SURE do know what is involved in adding NFS server/client capabilities into Xenix since I was involved in adding it to other compatible *nixes. It just seems strange to me that SCO and Excelan haven't joined forces to provide this product. Like yourself, I too know that SCO is working on the project; however, the way things are going, other '386 Unixes will have it before SCO. Sanford ( sandy ) Zelkovitz
stu@gtisqr.UUCP (Stu Donaldson) (09/16/88)
In article <1860@turnkey.TCC.COM> sandy@turnkey.TCC.COM (Sanford 'Sandy' Zelkovitz) writes: >I truely agree with you about The Excelan Hardware and software; however, >you would think that after MANY requests from customers about supporting >"compatible" NFS, they would. Like many other companies, we have Sun >workstations and VAXs running under NFS; however, our 286 and 386 systems >cannot share that luxury. Heck, I'd be happy if they would simply provide STREAMS support for the 386 Unix implimentation. -- Stu Donaldson UUCP: uw-beaver!uw-nsr!uw-warp!gtisqr!stu Global Tech Int'l Inc. ARPA: uw-nsr!uw-warp!gtisqr!stu@beaver.cs.washington.edu Mukilteo WA, 98275 Bell: (206) 742-9111 PS, use one of the above return addresses, the From field is probably hosed.