Technical data

Table 2–11: Comparison of File Protection (cont.)
Protection levels READ (R)
WRITE (W)
EXECUTE (E) – Controls file
execution and directory search
access
DELETE (D)
read (r)
— The user has a
matching UIC
write (w)
— Controls
unlinking files to the directory.
execute (x)
— Controls file
execution and directory search
access
A file is deleted if it is unlinked
from the directory and had
no links in other directories.
Writeaccesstothedirectoryis
refused.
Syntax
s:rwed, o:rwed, g:rwed,
w:rwed
rwxrwxrwx
The protection levels are divided
into groups of three characters:
• First three characters:
protection levels for the
owner.
• Second three characters:
protection levels for the
group.
• Last three characters:
protection levels for all other
users.
2.3 Portability
The TCP/IP Services allows you to create a logical UNIX style file system on an
OpenVMS host. Remote UNIX hosts that have NFS software can then access
this file system. When a remote UNIX system accesses files, these files conform
to UNIX file system rules, not to the OpenVMS rules. This ensures that existing
UNIX applications work without change. The logical UNIX file system resides
on a Files-11 formatted disk and is represented as a set of Files-11 files called a
container file system. For information about creating a UNIX file system on an
OpenVMS host, refer to the Compaq TCP/IP Services for OpenVMS Management
guide.
The UNIX file names and attributes are catalogued in the container file, one of the
files in the container file system. The container file also has a representation of
the UNIX directory hierarchy and a pointer to the data file for each file name.
In addition to its UNIX name, each file in the container file system has a valid
Files-11 file name assigned by the system. An OpenVMS directory exists for each
UNIX directory stored in the container file. All files catalogued in a UNIX directory
are also catalogued in the corresponding OpenVMS directory. However, the UNIX
directory hierarchy is not duplicated in the OpenVMS directory hierarchy. Each
UNIX file is represented as an OpenVMS data file. Therefore, OpenVMS utilities,
such as BACKUP, can use standard methods to access these files.
2–10 Understanding OpenVMS and UNIX Implementations