.TH GETUNIX 1 HEP
.SH NAME
cp11, cpv, cpu; ls11, lsv, lsu \- read UNIX filesystems
.SH SYNOPSIS
.BR cp ?
[options] sourcefile [targetfile]
.br
.BR ls ?
[options] directory
.SH DESCRIPTION
.IR Cp ?
retrieves the named
.I sourcefile
from a UNIX file system.
If a
.I targetfile
is specified, the copy is placed there; otherwise
the contents of the file are written to standard output.
If the
.I targetfile
named is a directory,
the file is copied there
with the same basename
as the original.
.PP
.IR Ls ?
is similar to
.IR cp ?
(in fact, it is merely a link to it),
but lists the contents of the directory
.IR sourcefile ;
if the file is not a directory,
it is listed by itself.
Normally,
just filenames are listed;
if the
.B \-l
flag is given,
more information
(protection, modes)
is printed.
.PP
Other options
recognized by both
.I cp?
and
.IR ls? :
.PP
.TP 1i
.BR \-d " device"
Filesystem resides on the named
.I device
(or file),
rather than the default.
.B
.IP \-v
Filesystem is a VAX (32V) filesystem.
.B
.IP \-7
Filesystem is a version 7 filesystem.
.B
.IP \-6
Filesystem is a version 6 filesystem.
.B
.IP \-s
Silent mode; error messages are suppressed.
.SH FILES
/dev/v\(**	VAX filesystems
.br
/dev/v7\(**	V7 filesystems
.br
/dev/v6\(**	V6 filesystems
.br
/bin/sort
.SH SEE ALSO
ls(1)
.SH DIAGNOSTICS
Most are self-explanatory.
.PP
"File has hole(s)" means that the file contains an unallocated block.
This usually indicates something weird with the file,
but may be a normal condition.
Holes in the output file are created as allocated blocks filled with zeros.
.SH "HEP INFO"
Written at HEP by Rob Pike.
Modified by Mark Bartelt.
Further hacked by Norman Wilson.
Hacked still more by Mark Bartelt.
.PP
On the UNIX VAX, the program is named
.I cp11
and
.IR ls11 ,
and is used to fetch files from the PDP-11/45 RJE system.
Since the RJE system is now running a V7 system,
.B \-7
is the default.
.PP
On the 11/45, the program is named
.I cpv
and
.IR lsv ,
and is used to fetch files from the VAX.
The default is
.BR \-v .
.PP
Now also runs under VMS (ported via EUNICE),
where the disks containing UNIX filesystems
are mounted foreign
with names $UNIX0, $UNIX1, and so forth.
The following foreign commands are defined:
.in +.5i
.nf
cpu*nix :== $sys$sysdisk:[bin]getunix cpunix
lsu*nix :== $sys$sysdisk:[bin]getunix lsunix
cpv*ax :== $sys$sysdisk:[bin]getunix cpvax
lsv*ax :== $sys$sysdisk:[bin]getunix lsvax
cp11 :== $sys$sysdisk:[bin]getunix cp11
ls11 :== $sys$sysdisk:[bin]getunix ls11
.fi
.PP
On the VMS VAX,
.I cpu/lsu
(and
.IR cpv/lsv )
are used to fetch files from the UNIX VAX,
.I cp11/ls11
to fetch files from the 11/45.
Defaults are, obviously,
.B \-v
and
.BR \-7 ,
respectively.
.PP
File protection modes are checked
to ensure that the person running the program
actually has appropriate access permission.
When running under VMS,
the access test is modified somewhat:
Since there is no convenient way to map UNIX UIDs
and VMS UIC member numbers onto each other,
only group and world access are checked.
Furthermore, a group match is defined to exist
if the decimal representation of the UNIX GID
is the same as the octal representation of the VMS UIC group number.
This is done to make things easier for people who set up accounts:
If a group on the VMS machine is, say, 123 (octal),
that same group must be 123 (decimal) on the UNIX machines,
and vice-versa.
Fortunately, that's the way things are set up here.
Note that files which are readable only to owner
cannot be copied to the VMS system.
.PP
The UNIX version needs to read ``cooked'' devices
rather than ``raw'' ones,
since it does
.IR lseek s
that aren't whole-block multiples.
.PP
The VMS version of
.IR ls ?
does not produce sorted output.