eps@toaster.SFSU.EDU (Eric P. Scott) (09/12/90)
This is the latest and greatest version of telnet/telnetd from Berkeley--well, actually from Dave Borman at Cray Research. I've made the appropriate tweaks to get it to compile on NeXT 1.0/1.0a systems in addition to the other supported platforms. There's very little peculiar about the NeXT; most of the effort went into making GCC happy, hence most fixes are under __GNUC__ conditionals. I've included the original source files along with my revisions, so you can diff them to see what I've actually done. As usual, I've heavily resisted the temptation to fix every little blatant coding stupidity. [enough editorializing] The following files are available for anonymous FTP from sutro.sfsu.edu [130.212.15.230] in the pub directory: telnet-src.tar.Z complete source distribution telnet-exe.tar.Z telnet executable and man page Previous versions of telnet-src.tar.Z, telnet.Z, and telnet.1c.Z from SFSU are OBSOLETE and should be deleted. I feel comfortable renaming NeXT's telnet to telnet.orig and dropping this one in /usr/ucb. telnetd is another story entirely; while it fixes many problems with the telnetd NeXT ships, it turns out not to work with the widely-used (freebie) Clarkson telnet software for IBM PCs. This is a problem specific to the Clarkson/NCSA and CUTCP/CUTE software (e.g. NCSA 2.3b10 does NOT have the problem). I'm told it will be fixed in the forthcoming "-C" release (whenever THAT is). Anyway, if you want to play with telnetd, grab the source tarchive. Also, I'm including an example of how one might implement "local policy restrictions" on incoming telnet connections in the form of a context diff (which you can apply using Larry Wall's "patch" utility). Happy hacking! -=EPS=-
joeh@eleazar.dartmouth.edu (Joseph L. Hill) (09/28/90)
Can anyone tell me if macintosh memory chips can be used in a neXt? A friend of mine wants to buy some mac chips and put them in his next. (4 meg chips), please reply via mail to glennm@melchior.dartmouth.edu. Thanks!