The file ls-lr is a directory listing of the files available for anonymous uucp
from uunet. The directory listing shows file permissions, ownership, size in 
bytes, creation date, and name.  If the first character of the permissions 
field is a "d", the file is a directory file, and its name and the files 
within will be found later in the listing.  If the first character is a hyphen
("-"), it is an ordinary file.  

DIRECTORY AND FILE NAMES ON UUNET

When fetching files from uunet, if the file is in uunet's "uucp root" directory
(the first group of files shown in ls-lr.), the source file spec should be
"uunet!~/filename".  For example, to get the current ls-lr file, use 

	$ uucp "uunet!~/ls-lR.Z" ls-lr.z

or, to retrieve the current uucp map files in compressed tar format, use

	$ uucp "uunet!~/uumap.tar.Z" uumap.tar-z

Note that CASE IS SIGNIFICANT in the remote (source) file name.  

for files in other than the top-level directory, include the directory 
specification after the "~/".  For example, here is part of the
uunet-info directory (at the very end of the ls-lr list): 

/usr/spool/ftp/uunet-info: <--- this is the directory name (w/o the :)
total 862
-rw-rw-r--  1 rick         1773 Apr 30 09:09 900
-rw-r--r--  1 asp         18629 Jun 25 11:58 AlterNet.backbone.ps
-rw-rw-r--  1 revell        785 Apr 19 18:04 access
	[...]

To retrieve the second file listed, use the following uucp command:

 $ uucp "uunet!~/usr/spool/ftp/uunet-info/AlterNet.backbone.ps" -
	"alternet.backbone-ps"

LOCAL (DESTINATION) FILE NAMES

The local (destination) file name (alternet.backbone-ps in the last example)
can be any valid VMS file name.  Like any other VMS file name, case is not
significant.  If the Unix file name contains more than one dot (.) or some
other construction that isn't acceptable to VMS, you'll have to come up with a
substitute, as we've done here.  Note that the destination name need not be
even slightly related to the file's original name; so the following would work
as well: 

 $ uucp -m "uunet!~/usr/spool/ftp/uunet-info/AlterNet.backbone.ps" foo.bar

but probably we want the file name to be a bit more meaningful than that.  

LOCAL (DESTINATION) DIRECTORIES

Under present implementations of DECUS uucp, the file will always arrive in the
UUCP_SPOOL directory.  The uucp command will not reject vms-style device and 
directory specs on the "local file name" parameter, but it will silently 
ignore them.  

HANDLING COMPRESSED FILES

All uunet files ending in ".Z" are compressed.  You can decompress them with
the compress utility supplied with DECUS uucp.  compress expects the names of 
compressed files to end with "-Z", unless overridden with the -z option.  To
decompress the ls-lr file, as retrieved from uunet via the command shown
above, you can either use

	$ decompress -z  ls-lr.z

which will leave the decompressed file in ls-lr.z, or you can

	$ rename ls-lr.z ls-lr.-z
	$ decompress ls-lr.

which will assume that the input is called ls-lr.-z, and name the output ls-lr.
You could also have asked uucp to retrieve the file with the ".-z" suffix in 
the first place, eg

	$ uucp "uunet!~/ls-lR.Z" ls-lr.-z