tr@samadams.princeton.edu (Tom Reingold) (10/18/90)
Someone wrote some programs that implement or emulate or hearken from
TCP/IP programs such as rlogin, rsh (or call it remsh if you prefer),
and they ran on the 3B1 or something on a LAN running StarGROUP. Where
was it posted or archived? I would like to try compiling them on 3B2's
and 386's.
--
Tom Reingold
tr@samadams.princeton.edu OR ...!princeton!samadams!tr
"Brew strength depends upon the
amount of coffee used." -Black&Deckermvadh@cbnews.att.com (andrew.d.hay) (10/18/90)
In article <3750@rossignol.Princeton.EDU>, tr@samadams.princeton.edu (Tom Reingold) writes: > Someone wrote some programs that implement or emulate or hearken from > TCP/IP programs such as rlogin, rsh (or call it remsh if you prefer), > and they ran on the 3B1 or something on a LAN running StarGROUP. Where > was it posted or archived? I would like to try compiling them on 3B2's > and 386's. > -- it was a port of BSD rlogin et. al. to *STARLAN-1* for the 3b1. you'll probably find it on osu-cis. while you might make it work on a 3b2/starlan-1, i don't believe such was ever offered for the 386. on the other hand, you don't need it for starlan-10 -- isn't it just ethernet over twisted pair? can't you just run the BSD stuff as is? -- Andrew Hay +------------------------------------------------------+ Ragged Individualist | You just have _N_O idea! It's the difference | AT&T-BL Ward Hill MA | between _S_H_O_O_T_I_N_G a bullet and _T_H_R_O_W_I_N_G it! | a.d.hay@att.com +------------------------------------------------------+
woods@eci386.uucp (Greg A. Woods) (10/24/90)
In article <1990Oct18.113228.7342@cbnews.att.com> mvadh@cbnews.att.com (andrew.d.hay) writes: > it was a port of BSD rlogin et. al. to *STARLAN-1* for the 3b1. > you'll probably find it on osu-cis. > > while you might make it work on a 3b2/starlan-1, i don't believe such > was ever offered for the 386. on the other hand, you don't need it > for starlan-10 -- isn't it just ethernet over twisted pair? can't you > just run the BSD stuff as is? After a cursory glance at these tools, it appears a small amount of clean-up will make the port work on any TLI implementation. I.e. the port has changed the r-utils to use the t_* networking routines from SysVr3.x, i.e. libnsl_s.a, as described in the SysV Network Programmers Guide. I.e. as long as you have a homogenous network using these tools, it doesn't matter what the transport layer, or the physical layer for that matter, is. [The clean-up probably means better integration with the listener, i.e. the way HDB-UUCP is.] As for "just running the BSD stuff as-is", you can't, unless you have a full BSD socket library or emulation library. This is possible on many TCP/IP implementations for SysVr3.x, though such implementations usually come with ports of the r-utils. There's a big difference between TCP/IP and Ethernet. -- Greg A. Woods woods@{eci386,gate,robohack,ontmoh,tmsoft}.UUCP +1-416-443-1734 [h] +1-416-595-5425 [w] VE3-TCP Toronto, Ontario CANADA