From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HTML_MESSAGE,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 11053 invoked from network); 4 Jul 2020 00:29:53 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 4 Jul 2020 00:29:53 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 0381D9C711; Sat, 4 Jul 2020 10:29:51 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 252549C5E1; Sat, 4 Jul 2020 10:29:05 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (1024-bit key; unprotected) header.d=ccc.com header.i=@ccc.com header.b="RWhwQ0O+"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 0BE989C5E1; Sat, 4 Jul 2020 10:29:03 +1000 (AEST) Received: from mail-qv1-f51.google.com (mail-qv1-f51.google.com [209.85.219.51]) by minnie.tuhs.org (Postfix) with ESMTPS id B767794585 for ; Sat, 4 Jul 2020 10:29:01 +1000 (AEST) Received: by mail-qv1-f51.google.com with SMTP id t7so14934590qvl.8 for ; Fri, 03 Jul 2020 17:29:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ccc.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=hL8aky339Wu/J6SDdBZtt08JiSbuqqmLCVjlvI9Zd+w=; b=RWhwQ0O+FogS/cinufx8ieRIYcZSv+3fM+K/D+eOjAAp16gu7aEKrKEl+P0aR/eg3x MpXXH7bHYAFmgYLPXEcI+ai/28qj+Mu29BwdkKRLAOq4QI4cK3ykWge7DOLMu8PZy8K9 0fdkRdiPZKCuRn83vs+UoOz7WDUIUW889z49I= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=hL8aky339Wu/J6SDdBZtt08JiSbuqqmLCVjlvI9Zd+w=; b=eHOy63CyGv1OlSzbFCISnOZxoCmoOIRD+x35EB2Npjb80r7Y0VmhddUACMWSasmT2c GddJ/XMpz2bjUvxR5AwvpCZzi8ije3MBJD1g/O+JeHsB/RJLXC0DBLduVptMWvUQDJEU JeCn7MoQCxTTugEhxM/n1l7sjU8DjpRTV0D7OxQOwrjbSYf2GNkvc6t8FF5FWnWtPQPD rG5Q/XAYJ2N9rA2uWorK6d/kRvdTxQq463OWiyEkjKjldxyuASlQv+6dLTfvKCnPaTOa dMEH2p+L3OLYGJShxcjLeG6rg7o3po3Pob91IvnS7GuTZkxvTr9C1CqzCMtdApFkTPUB p1+g== X-Gm-Message-State: AOAM533T8iwXeFGYZ6u5hvaAOz6aOV0tTablPD36hZGKNSgH0uptulLE dv89g5Ks38neIoX6Oq0o0je91XlT7HUs7kWTGI3i6nK/FwY= X-Google-Smtp-Source: ABdhPJxHwd3FH/3rurNu7IfZwFFVqfI8Wu1R7i+qVW2wUPx9+0OBxxTidB6IwjmtU5CZYYetph5JnWlegwBCobgHMWQ= X-Received: by 2002:a0c:facb:: with SMTP id p11mr35996409qvo.243.1593822540427; Fri, 03 Jul 2020 17:29:00 -0700 (PDT) MIME-Version: 1.0 References: <01f8f896-9921-6c55-8dc2-6b9859f2f230@tnetconsulting.net> In-Reply-To: <01f8f896-9921-6c55-8dc2-6b9859f2f230@tnetconsulting.net> From: Clem Cole Date: Fri, 3 Jul 2020 20:28:49 -0400 Message-ID: To: Grant Taylor Content-Type: multipart/alternative; boundary="0000000000005b894f05a992ba66" Subject: Re: [TUHS] v7 uucp debugging help requested X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: tuhs@minnie.tuhs.org Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --0000000000005b894f05a992ba66 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Grant - The g (greg=E2=80=99s protocol) is correct. IIRC that=E2=80=99s the= only line protocol Dan distributed in the V7 original code base. On Fri, Jul 3, 2020 at 6:46 PM Grant Taylor via TUHS wrote: > On 7/3/20 2:52 PM, Adam Thornton wrote: > > I've built UUCP, set a node name, and set it up on the pi. > > > > I can execute uucico to send files, and it, frustratingly, almost works= . > > Which system are you referring to here? The Pi or V7? > > > From the Pi side, I see (with uulog): > > > > uucico v7 - (2020-07-03 08:11:34.97 23106) Calling system v7 (port TCP) > > uucico v7 - (2020-07-03 08:11:42.25 23106) Login successful > > uucico v7 - (2020-07-03 08:11:44.44 23106) Handshake successful > > (protocol 'g' sending packet/window 64/3 receiving 64/7) > > uucico v7 adam (2020-07-03 08:11:51.61 23106) Sending > > /home/adam/git/simh/sim_scsi.h (6780 bytes) > > uucico v7 adam (2020-07-03 08:16:21.79 23106) ERROR: Timed out waiting > > for packet > > uucico v7 - (2020-07-03 08:16:21.80 23106) Protocol 'g' packets: sent > > 86, resent 6, received 1 > > I'm a little surprised that you're trying to use the 'g' protocol to > talk to v7. I thought the 'g' protocol came out later for TCP over > Ethernet connections. As such I wonder if UUCP on v7 supports the 'g' > protocol. > > I think that Clem knows a LOT more about this than I do. > > I'm ignorantly asking questions. > > > uucico v7 - (2020-07-03 08:16:21.80 23106) Errors: header 2, checksum 0= , > > order 0, remote rejects 0 > > uucico v7 - (2020-07-03 08:16:22.51 23106) Call complete (283 seconds > > 5440 bytes 19 bps) > > > > So it's clearly logging in, and if I telnet in directly, the v7 end is > > starting uucico as expected: > > > > login: pi-uucp > > Password: > > Shere > > Shouldn't that be something more like the following? > > Shere=3Dv7 > > What does 'uuname -l' (or '--local') show? (I'm much more familiar with > Taylor UUCP than I am the UUCP in v7. > > > uulog -x on the v7 side has no output, and nothing ever appears in the > > spool directory, which I suspect is a direct result of the timeout > > waiting for packet. > > > > So my question is, what else do I do to debug this? Clearly the pi > > (Taylor UUCP) side is expecting something else--maybe an > > acknowledgement?--from the v7 side to let it know the transmission was > > successful. > > > > Any help would be appreciated. > > I've not messed with this particular problem in probably 2 years and > I've forgotten more than comments above. > > > > -- > Grant. . . . > unix || die > > -- Sent from a handheld expect more typos than usual --0000000000005b894f05a992ba66 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Grant - The g (greg=E2=80=99s protocol) is correct. = IIRC that=E2=80=99s the only line protocol Dan distributed in the V7 origin= al code base.

On Fri, Jul 3, 2020 at 6:46 PM Grant Taylor via TUH= S <tuhs@minnie.tuhs.org> = wrote:
On 7/3/20 2:52 PM, Adam Thor= nton wrote:
> I've built UUCP, set a node name, and set it up on the pi.
>
> I can execute uucico to send files, and it, frustratingly, almost work= s.

Which system are you referring to here?=C2=A0 The Pi or V7?

>=C2=A0 From the Pi side, I see (with uulog):
>
> uucico v7 - (2020-07-03 08:11:34.97 23106) Calling system v7 (port TCP= )
> uucico v7 - (2020-07-03 08:11:42.25 23106) Login successful
> uucico v7 - (2020-07-03 08:11:44.44 23106) Handshake successful
> (protocol 'g' sending packet/window 64/3 receiving 64/7)
> uucico v7 adam (2020-07-03 08:11:51.61 23106) Sending
> /home/adam/git/simh/sim_scsi.h (6780 bytes)
> uucico v7 adam (2020-07-03 08:16:21.79 23106) ERROR: Timed out waiting=
> for packet
> uucico v7 - (2020-07-03 08:16:21.80 23106) Protocol 'g' packet= s: sent
> 86, resent 6, received 1

I'm a little surprised that you're trying to use the 'g' pr= otocol to
talk to v7.=C2=A0 I thought the 'g' protocol came out later for TCP= over
Ethernet connections.=C2=A0 As such I wonder if UUCP on v7 supports the = 9;g'
protocol.

I think that Clem knows a LOT more about this than I do.

I'm ignorantly asking questions.

> uucico v7 - (2020-07-03 08:16:21.80 23106) Errors: header 2, checksum = 0,
> order 0, remote rejects 0
> uucico v7 - (2020-07-03 08:16:22.51 23106) Call complete (283 seconds =
> 5440 bytes 19 bps)
>
> So it's clearly logging in, and if I telnet in directly, the v7 en= d is
> starting uucico as expected:
>
> login: pi-uucp
> Password:
> Shere

Shouldn't that be something more like the following?

Shere=3Dv7

What does 'uuname -l' (or '--local') show?=C2=A0 (I'm m= uch more familiar with
Taylor UUCP than I am the UUCP in v7.

> uulog -x on the v7 side has no output, and nothing ever appears in the=
> spool directory, which I suspect is a direct result of the timeout > waiting for packet.
>
> So my question is, what else do I do to debug this?=C2=A0 Clearly the = pi
> (Taylor UUCP) side is expecting something else--maybe an
> acknowledgement?--from the v7 side to let it know the transmission was=
> successful.
>
> Any help would be appreciated.

I've not messed with this particular problem in probably 2 years and I've forgotten more than comments above.



--
Grant. . . .
unix || die

--
Sent from a handheld expect more typos t= han usual
--0000000000005b894f05a992ba66--