0-1
|
|---|
| 10FSL | | Acronym for “10.0 File System Layout”
|
|---|
C
|
|---|
| Cluster | | A set of one or more nodes, connected by a network,
that are provided boot services by a cluster server.
|
|---|
| Configuration data | | information used to configure the system and includes:
IP address, hostname, timezone, etc.
|
|
|---|
E-F
|
|---|
| Execution script | | An execution script is a system start-up and shutdown
script located in/sbin/init.d.
|
|---|
G-H-I-J-K
|
|---|
| Install point | | A directory into which software can be directly
installed. All non-install points are potentially private directories,
and must be configured on a per-host basis by execution of SD configuration
scripts.
|
|---|
L-M-N-O
|
|---|
| Link Files | | A component of the start-up/shutdown model used
to link the execution scripts to a particular run-state. Link files
are contained in /sbin/rc*.d and point to execution
scripts in /sbin/init.d.
|
|---|
| NFS | | Network File System. An implementation of Remote
Procedure Calls (RPCs) and remote mounting and access of file systems
over a network.
|
|---|
| OSF | | Open Software Foundation.
|
|---|
P-Q-R-S
|
|---|
| PID file | | A file which contains the process ID of a running
application or subsystem component.
|
|---|
| Runtime File | | A working file created by an application or a subsystem.
these include lock files, PID files, temporary files, state files,
etc.
|
|---|
| SD | | Acronym for Software Distributor, a replacement
for the HP-UX DUI update utility.
|
|---|
| Server | | The node or nodes in a cluster providing services
to other nodes.
|
|---|
| Subsystem | | An operating system feature that is tightly coupled
with the rest of the operating system; enough so that it is not
considered an application. An example of a subsystem is NFS.
|
|---|
T-U-V-W
|
|---|
| V.4 | | AT&T System V, release 4. Sometimes used
in this paper to denote the 10.x Filesystem Layout.
|
|---|
| V4FSL | | Acronym for the AT&T System V, Release
4 FileSystem Layout
|
|---|
Printable version
