Very Computer

I have to run a null-modem line between my SPARC 1+ (named "helios", running
OS 4.1.3) and my new DEC Alpha (named "rover", running OS 1.3).  The line
is working fine; I can use "cu" to login from rover to helios, and (if
I turn helios' /etc/ttytab entry "off") from helios to rover.  I can
transfer ASCII files this way, but I'd like to use uucp (I know, I could
uuencode 'em, but uucp would be much simpler).  When I try, from helios:
  /usr/lib/uucp/Uutry rover    (while su'd to uucp)
it will eventually get the login prompt, but doesn't seem to ever get
the password prompt.  Here, see for yourself:
  $ /usr/lib/uucp/Uutry rover
  /usr/lib/uucp/uucico -r1 -srover  -x5 >/tmp/rover 2>&1&
  tmp=/tmp/rover
  mchFind called (rover)
  conn(rover)
  Device Type rover wanted
  mlock cua0 succeeded
  processdev: calling setdevcfg(uucico, rover)
  gdial(direct) called
  getto ret 6
  expect: (in:)
  sendthem (^M)
  expect: (in:)
  ^M^M^Jlogin:got it
  sendthem (Uhelios^M)
  expect: (word:)
   Uhelios^Mlost line errno - 0
  Call Failed: LOGIN FAILED
  exit code 101
  Conversation Complete: Status FAILED

Here's what it looked like trying from rover
  $ uutry helios
  maxstart = 300
  maxmsg = 33
  mchFind called (helios)
  list (rmail) num = 1
  _Request (TRUE), _Switch (TRUE), _CallBack (FALSE), _MyName (), _Commands rmail
  chdir(/usr/spool/uucp/helios)
  conn(helios)
  Device Type helios wanted
  Internal caller type direct
  errno: 17 link(/var/spool/locks//LTMP.391, /var/spool/locks/LCK..ttyd0)
  ttylock file /var/spool/locks/LCK..ttyd0
  kill pid (388), returned -1--ok to remove lock file (/var/spool/locks/LCK..ttyd0)
  ttylock ttyd0 succeeded
  Attempting to open /dev/ttyd0
  fixline(5, 9600)
  Changing tty c_cflags from 0145415
  Changing tty c_cflags to   0145415
  getto ret 5
  expect: (in:)
  ^M^Jhelios login:got it
  sendthem (^M)
  expect: (word:)
  Urover^M^JPassword:got it
  sendthem (^M)
  expect: (login:)

At this point, it looks like it's been successful, and maybe it has, but
after thirty seconds or so it continues with:
  timed out
  sendthem (^M)
  expect: (login:)
  lost line errno - 0
  close caller (5)
  ttyunlock(ttyd0)
  Call Failed: LOGIN FAILED
  exit code 101
  Conversation Complete: Status FAILED
  TM_cnt: 0

I tried uucp'ing a file from rover to helios, but it looks like it's going
to sit in the queue forever.  "uustat -q" tells me:
  ... LOGIN FAILED Retry: 0:03 Count: 3

So, any clues as to what I have misconfigured?  Are there any tips about
connecting BSD-based systems to not-so-BSD?  Is there a mismatch between
using getty on the Sun and uugetty on the Alpha?

--
Kevin Weinrich       Atlantic Research Corp. (but I don't speak for them)

        [ uucp diags deleted ]

Quote:>   sendthem (Uhelios^M)
>   expect: (word:)
>    Uhelios^Mlost line errno - 0

Kevin,

I would guess that your DEC communications are following POSIX specs
which says in effect, if CD is non-existent or in a low state then
assume there is no device connected to the line and do not respond to
any traffic and/or kill any processes associated with the line.

Put a breakout box in the line and look very closely at CD.  If it
transitions followed by your lost line error message then you will have
to find a high signal to feed CD on the DEC.

Best of luck to you.

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                        S. Lane Pierce

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Quote:>> it will eventually get the login prompt, but doesn't seem to ever get
>> the password prompt.  Here, see for yourself:
>>   $ /usr/lib/uucp/Uutry rover
>>   /usr/lib/uucp/uucico -r1 -srover  -x5 >/tmp/rover 2>&1&

        It looks like the old parity problem. Put in your chat script
in the Systems entry before the ogin:--ogin: (or equivalent) a
"" P_ZERO

This waits for nothing and sets the line to eight bit no parity.

Geoff Coleman

p.s. I'm posting this because it is a fairly common question