--- John Foust <jfoust_at_threedee.com> wrote:
> At 08:30 AM 6/13/01 -0400, Douglas Quebbeman wrote:
> >> Since most vintage machines can't run TCP/IP but CAN run uucp, would
> >> there be any interest in a dialup uucp node for retrieving email, files...
> You can still use the regular Internet as your transport
> and do away with the toll calls, can't you?
I did this for months when I moved away from my old ISP and I needed to
keep my old UUCP address live (toll calls from Antarctica to Ohio were
*not* an option). It was on an Amiga; I hacked UUCP to open telnet.device
instead of serial.device (not required on modern UUCP implementations) which
simulated a modem, but opened a TCP port. You "dialed" it with
"ATDTuucp.somewhere.com" instead of a phone number. It was a crufty hack, but
it meant that you didn't have to change apps, whether a terminal program or
something more sophisticated, like UUCP.
HDB UUCP does allow you to fully describe the transport mechanism without
resorting to OS-specific tricks. If the goal is to attach old machines
to each other over the net, it might be handy for each participant to have
an intermediate machine that _could_ reach out over the 'net and aggregate
the local traffic over serial ports.
A 386/486 box, for example, running not much more than UNIX and UUCP, could
be the RS-232<->Ethernet UUCP home gateway, as could an Amiga, should you
happen to have one with a network card lying around doing nothing (given
which is more abundant...) It would only add one bang on each end of the
path.
At least script kiddies aren't running around with wads of exploits for
UUCP daemons hanging on port 540. Security through antiquity?
-ethan
=====
Visit "The Seventh Continent"
http://penguincentral.com/penguincentral.html
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35
a year!
http://personal.mail.yahoo.com/
Received on Wed Jun 13 2001 - 17:45:24 BST