15 Facts About UUCP

Taylor UUCP addressed security holes which allowed some of the original network worms to remotely execute unexpected shell commands.

Taylor UUCP incorporated features of all previous versions of UUCP, allowing it to communicate with any other version and even use similar config file formats from other versions.

UUCP was implemented for non-UNIX operating systems, most-notably DOS systems.

FSUUCP was the only other implementation of Taylor's enhanced 'i' protocol, a significant improvement over the standard 'g' protocol used by most UUCP implementations.

UUCP used the computers' modems to dial out to other computers, establishing temporary, point-to-point links between them.

Related searches

Each system in a UUCP network has a list of neighbor systems, with phone numbers, login names and passwords, etc.

UUCP is normally started by having a user log into the target system and then running the UUCP program.

Taylor UUCP did not support G, but did support any valid requested window or packet size, so remote systems starting G would work fine with Taylor's g, while two Taylor systems could negotiate even faster connections.

UUCP implementations include other transfer protocols for use over certain links.

The UUCP network was constantly changing as new systems and dial-up links were added, others were removed, etc.

UUCP Mapping Project was a volunteer, largely successful effort to build a map of the connections between machines that were open mail relays and establish a managed namespace.

The UUCP Mapping Project was formally shut down in late 2000.

In July 2012, Dutch Internet provider XS4ALL closed down its UUCP service, claiming it was "probably one of the last providers in the world that still offered it"; it had only 13 users at that time.

One surviving feature of UUCP is the chat file format, largely inherited by the Expect software package.

Similar techniques as those used by UUCP can apply to other networks that experience delay or significant disruption.