OSF DCE Administration Guide--Introduction

OSF DCE Administration Guide—Introduction
• The common directory
This directory contains programs and files needed by users working on machines of
all system types, such as text editors or online documentation files. The common/etc
directory is a logical place to keep the central update sources for files used on all
DFS client machines.
• The public directory
This directory contains files that users want to make available to everyone, including
foreign and unauthenticated users.
• The sys_type directory
This directory contains binaries for each system type you use as a file server or client
machine. If you plan to use the @sys variable in pathnames, you need to use
standard names to represent system types.
• The usr directory
This directory contains the home directory of each DFS user in a cell and any foreign
users that are granted a local account. Users and system administrators can protect
this directory so that only locally authorized users can access it. If your cell is quite
large, you can divide user home directories in multiple directory listings to facilitate
quicker directory lookups.
• The src directory
This directory contains source filesets, such as those for DFS source files.
2.4.5 Setting Up Filesets
Consider the following recommendations and restrictions when you set up filesets:
• Fileset names must be limited to 102 characters or less.
• Every cell must include root.dfs. The root fileset can be a LFS fileset or it can be a
non-LFS fileset (a non-DCE LFS file system). If root.dfs is a LFS fileset and you
plan to use replication, you need to follow the steps described in the , which
describes how to create root.dfs as a DFS LFS fileset and create a read/write mount
point for the fileset below the top level of the cell’s filespace.
• You should use a common prefix when naming related filesets. This aids in
manipulating and grouping related filesets. It also relates the fileset’s name to its
mount point.
• You can group filesets on the same partition of a File Server machine. This can
localize the effects of an outage, but you also need to consider factors such as the
number of File Server machines and load balancing before grouping filesets.
• You can replicate filesets for load balancing and to make fileset contents more
available. Replication is appropriate for filesets that are read much more often than
they are written, such as filesets containing installed executable files. Replication is
not supported for non-LFS filesets.
2− 14 Tandem Computers Incorporated 124244