The VMSnet Working Group (U.S. VAX Systems SIG) Submissions DECUS uucp, Version 2.0 This directory tree contains Version 2.0 of DECUS uucp (formerly "VMSnet software"), a package which allows VMS systems to exchange mail, files, and network news with other systems (including Unix systems, and VMS systems running this software) using the uucp "g" protocol. Geoff Huston's ANU News, Version 6.1 Alpha-4 is included, along with command procedures and programs for transferring news via uucp. Everything here has been compiled and linked under VMS V5.4-x or 5.5. All images are known to work under 5.4-x, and possibly earlier versions. Object files are present (in the "development" savesets) for aid in linking under earlier versions. For distribution via the VAX SIG Symposium tape, almost all of the files have been placed in compressed BACKUP savesets. (The exceptions are: the documentation; and the programs and files needed to decompress and restore the compressed savesets.) Full documentation is in [UUCP.DOC]USRGD20.MEM, and in other files described therein. Chapter 2, "Installing the Files", of USRGD20.MEM contains descriptions of the contents of each saveset (so you can decide which ones you need) plus instructions for restoring them. After decompression, the total space required for the [UUCP...] tree is about 57,000 blocks. However, at least half of this (source and object files) will not be needed by most sites; sites that don't need the uucp maps and aren't running news can run uucp in about 6,000 blocks (plus log files). Sites that are currently running older versions of DECUS uucp and/or NEWS will probably need only the RUN.BKP saveset and the "loose" files in this tree. After restoring them as described in "Installing the Files", see the appendix, "Upgrading from Previous Versions", in USRGD20.MEM. principal contributors: Jamie Hanrahan, Kernel Mode Consulting POB 16540, San Diego, CA 92176 +1 619 284 8492 jeh@cmkrnl.com Tom Allebrandi II Mark Pizzolato Inland Steel Research Labs 1558 Fernside Street East Chicago, IN Redwood City CA 94061 +1 219 399 6306 +1 415 369 9366 allebrandi@inland.com mark@infocomm.com .decwrl!simpact!inland!allebrandi ...!decwrl!infopiz!mark DECUS uucp version 2.0 Page 2 Release Notes 1 Restoring The Files -- [UUCP] Must Be A UFD The [UUCP] directory must be a UFD; that is, its parent directory must be [000000]. Placing UUCP.DIR under another directory on the disk will not work, even with a rooted logical. 2 Restoring The Files With An Existing [UUCP] Tree If you are already running a previous version of DECUS uucp, note that the restoration procedures described in "Installing the Files" in the document is intended to place the files from this distribution into your existing [UUCP...] directory tree, with the new files superseding the old (by use of the /NEW_VERSION qualifier on the BACKUP command). This is intentional! Do not attempt to defeat this mechanism (for example, do not try to place the 2.0 files in a tree of their own). The automatic upgrade mechanisms we have provided may not work properly unless the new files coexist in the [UUCP...] tree with the old ones. Again, read the Appendix, "Upgrading from Previous Versions", in USRGD20.MEM for details on upgrading. Your files in [UUCP.CFG] will not be superseded. The automatic upgrade procedures will preserve the definitions of all standard logical names defined in your existing UUCP_SYSTARTUP.COM and NEWS_SYSTARTUP.COM; these will be propagated to their new home in the CONTROL. file. Other changes which you have made to these procedure will of course not be propagated, but the previous file versions will not be purged, so you will be able to migrate your changes into the new files (if you desire). 3 Upgrade Instructions Due to a typo, the instructions for upgrading do not appear as a separate Appendix in the document. They appear at the end of the Appendix, "Security Issues".