Groups | Search | Server Info | Login | Register

Groups > comp.mail.uucp > #299

Re: how to connect UUCP nodes in the 21st century?

Show all headers | View raw

In article <3urs7l-88i.ln1@intheattic.eternal-september.org>,
Juancho  <eternal@notreally.com> wrote:
>On 2025-02-11, Dan Cross <cross@spitfire.i.gajendra.net> wrote:
>> Juancho  <eternal@notreally.com> wrote:
>>>
>>>I was thinking about the "ct" and "cu" commands of the uucp suite.
>>
>> `cu` is just a serial communications program; it lets you use a
>> serial port and whatever that serial port is connected to;
>> historically it also had some syntactic sugar to connect to
>> systems that the administrator had put in the local UUCP
>> configuration.  Fundamentally it only lets you execute remote
>> commands in so far as the thing on the other end of the serial
>> port you use it with lets you do that, and `cu` itself is just
>> the communications agent.  I still occasionally use `cu` to talk
>> to little embedded devices and things like that.  Critically,
>> I doubt you could do `cu thathost!thishost` and expect it to
>> work (what if all outgoing lines from `thishost` were busy at
>> the time?).
>>
>> Similarly, `ct` does more or less the same thing, but assumes
>> that a line is connected to a modem, and knows how to dial a
>> phone number (back in the bad old days this was a lot more
>> complex than having a Hayes compatible modem that understood the
>> "AT" command set); in that sense, it's a little less flexible
>> than `cu`.  But again, it's just a communications agent, not a
>> remote execution/login program itself.
>>
>> `uux`, on the other hand, was actually designed to run commands
>> on some remote system: `uux seismo!me /bin/ls` or something
>> more involved like, `uux ucbvax!seismo!me /bin/ls` or whatever.
>> Still, this isn't exactly "remote login."
>
>In other words, it was common practice, before the Internet was 
>mainstream, to use cu/ct to login into other UNIX systems through serial
>lines and modems. Or my Xenix memories may be failing me.

I don't think that's what I said, but it's probably a true
statement.  This was not, however, using UUCP for remote login
in any recognizable sense.

        - Dan C.

Back to comp.mail.uucp | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

how to connect UUCP nodes in the 21st century? lkh <lkh@dwalin.uucp> - 2025-01-24 17:50 +0100
  Re: how to connect UUCP nodes in the 21st century? Marco Moock <mm+usenet-es@dorfdsl.de> - 2025-01-24 23:01 +0100
  Re: how to connect UUCP nodes in the 21st century? jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-01-24 18:01 -0500
  Re: how to connect UUCP nodes in the 21st century? Grant Taylor <gtaylor@tnetconsulting.net> - 2025-01-25 18:45 -0600
    Re: how to connect UUCP nodes in the 21st century? eternal@notreally.com (Juancho) - 2025-02-09 06:49 +0100
      Re: how to connect UUCP nodes in the 21st century? Grant Taylor <gtaylor@tnetconsulting.net> - 2025-02-09 17:03 -0600
        Re: how to connect UUCP nodes in the 21st century? Borax Man <rotflol2@hotmail.com> - 2025-04-25 14:28 +0000
    Re: how to connect UUCP nodes in the 21st century? Andy Valencia <vandys@vsta.org> - 2025-02-10 10:44 -0800
      Re: how to connect UUCP nodes in the 21st century? cross@spitfire.i.gajendra.net (Dan Cross) - 2025-02-11 12:27 +0000
        Re: how to connect UUCP nodes in the 21st century? Juancho <eternal@notreally.com> - 2025-02-11 18:45 +0100
          Re: how to connect UUCP nodes in the 21st century? cross@spitfire.i.gajendra.net (Dan Cross) - 2025-02-11 20:08 +0000
            Re: how to connect UUCP nodes in the 21st century? Juancho <eternal@notreally.com> - 2025-02-11 22:26 +0100
              Re: how to connect UUCP nodes in the 21st century? cross@spitfire.i.gajendra.net (Dan Cross) - 2025-02-11 23:00 +0000
          Re: how to connect UUCP nodes in the 21st century? Grant Taylor <gtaylor@tnetconsulting.net> - 2025-02-11 18:32 -0600
            Re: how to connect UUCP nodes in the 21st century? John Levine <johnl@taugh.com> - 2025-02-12 01:36 +0000

csiph-web