Path: utzoo!attcan!uunet!husc6!cmcl2!phri!dasys1!jpr
From: jpr@dasys1.UUCP (Jean-Pierre Radley)
Newsgroups: comp.sys.tandy
Subject: Re: Tandy 6000: brain-damaged uucp
Message-ID: <7810@dasys1.UUCP>
Date: 20 Nov 88 04:17:57 GMT
References: <7615@dasys1.UUCP> <4351@sneaky.TANDY.COM>
Reply-To: jpr@dasys1.UUCP (Jean-Pierre Radley)
Distribution: na
Organization: TANGENT
Lines: 32

In article <4351@sneaky.TANDY.COM> gordon@sneaky.UUCP (Gordon Burditt) writes:
>I tried mailing this, but it bounced.

Do you remember what routing you used?

>The uucp that comes with the Tandy 6000 is a UNIX Version 7-derived version.  
>Host names are supposed to be limited to 7 characters.
>Login names are limited to 8 characters.  Uucico doesn't know or care
>about this, though.

That does seem to be true on the 6000. On other systems, I note host names
and login names of nine characters, or more.

>>fail, because my uucico will send that as 'ujpradley', translating
>>upper-case to lower-case.
>uucico does not do this.  The getty on the other end (which I presume
>is another 6000) is doing it.

At site 'jpradley' (Tandy 6000): I cannot employ Ujpradley as a login name
from site 'trigere' (also a Tandy 6000). I must avoid that capital 'U'.

But at the same 'jpradley' site, the login name 'Uhombre' is quite nicely
used by a (non-Tandy) machine for a uucp login.

But from what you said, if it's the getty on the called machine that does
a "_tolower()", how can it do it selectively when getty has no idea about
the nature of the calling device? Same getty is answering all calls, but
different uucico's are calling...
-- 
Jean-Pierre Radley		Honi soit		jpr@dasys1.UUCP
New York, New York		qui mal			...!hombre!jpradley!jpr
CIS: 76120,1341			y pense			...!hombre!trigere!jpr