rubin@mtuxn.UUCP (M.RUBIN) (07/13/85)
We found that uucp between two 3B2's (running SYSV.2 and HoneyDanBer uucp) over a direct line was taking a long time (30-60 sec.) to start talking. Turns out the entry in the Systems file, which we had written according to the dimwits' documentation that comes with the 3B2 (and would have been written for us by the Simple Administration program that comes with the 3B2), went: othersys Any othersys 9600 - in:--in: n\pu\pu\pc\pp Unfortunately, the uugetty at the other end requires a return before it will say "login:", and since our machine was waiting for the "login:" nothing happened until uugetty hit a 60-second timeout. The above entry could only work with getty at the other end, not uugetty, i.e. a one-way line. At any rate, the CORRECT entry in Systems is: othersys Any othersys 19200 - "" \r in:--in: n\pu\pu\pc\pp Note the pauses in between "nuucp"; login can't handle 19200 baud input! (We also found no problems using 19200 baud instead of the recommended 9600. Then again we're using a very short cable.) --Mike Rubin, AT&T Information Systems, Freehold NJ {ihnp4, rest of AT&T}!mtuxn!newtech!rubin
honey@down.FUN (Peter Honeyman) (07/13/85)
hey let's take it easy on the boys, huh? honey, dan, and ber paid attention to the big things; little things like a "" "" in the Devices file just weren't big enough game. obtw you might try using echo checking (\Enuucp\e) instead of pauses. peter ps: i know your criticism was of the documenters and script writers (none of which were the principal authors, surprise!), but i take this shit personally, see? if you want to criticize honey danber, you have to praise it first.