NAME | SYNOPSIS | DESCRIPTION | SEE ALSO
/
/usr
/export
The file system tree is organized for administrative convenience. Distinct areas within the file system tree are provided for files that are private to one machine, files that can be shared by multiple machines of a common architecture, files that can be shared by all machines, and home directories. This organization allows sharable files to be stored on one machine but accessed by many machines using a remote file access mechanism such as NFS. Grouping together similar files makes the file system tree easier to upgrade and manage.
The file system tree consists of a root file system and a collection of mountable file systems. The mount(2) program attaches mountable file systems to the file system tree at mount points (directory entries) in the root file system or other previously mounted file systems. Two file systems, / (the root) and /usr, must be mounted in order to have a completely functional system. The root file system is mounted automatically by the kernel at boot time; the /usr file system is mounted by the system start-up script, which is run as part of the booting process.
The root file system contains files that are unique to each machine. It contains the following directories:
Primary location for special files. Typically, device files are built to match the kernel and hardware configuration of the machine.
Block disk devices.
Pseudo-terminal devices.
Raw disk devices.
Raw tape devices.
Entry points for the STREAMS Administrative driver.
Terminal devices.
Host-specific administrative configuration files and databases. /etc may be viewed as the directory that defines the machine's identity.
Accounting system configuration information.
Configuration information for cron(1M).
Defaults information for various programs.
Configuration information for exported file systems.
Binaries organized by file system types for operations required before /usr is mounted.
Configuration files for Internet services.
Shell scripts for transitioning between run levels.
Shared libraries needed during booting.
Configuration information for the printer subsystem.
Mail subsystem configuration.
Configuration information for transport independent network services.
Configuration information for optional packages.
Scripts for entering or leaving run level 0. See init(1M).
Scripts for entering or leaving run level 1. See init(1M).
Scripts for entering or leaving run level 2. See init(1M).
Scripts for entering or leaving run level 3. See init(1M).
Service Access Facility files.
Default profile scripts for new user accounts. See useradd(1M).
Status monitor information.
Backup status monitor information.
Trademark files; contents displayed at boot time.
UUCP configuration information. See uucp(1C).
Default root of the exported file system tree.
Default root of a subtree for user directories.
Subtree of Platform Independent loadable kernel modules required as part of the boot process. It includes the generic part of the core kernel that is platform-independent, /kernel/genunix. See kernel(1M).
32-bit device drivers.
64-bit SPARC device drivers.
Platform-independent kernel.
Default temporary mount point for file systems. This is an empty directory on which file systems may be temporarily mounted.
Root of a subtree for add-on application packages.
Subtree of Platform Specific objects which need to reside on the root filesystem. It contains a series of directories, one per supported platform. The semantics of the series of directories is equivalent to / (root).
Platform-dependent objects with semantics equivalent to /kernel. It includes the file unix, the core kernel that is platform-dependent. See kernel(1M).
64-bit platform-dependent kernel.
32-bit platform-dependent kernel.
Platform Dependent objects with semantics equivalent to /lib.
Platform Dependent objects with semantics equivalent to /sbin.
Root of a subtree for the process file system.
Essential executables used in the booting process and in manual system recovery. The full complement of utilities is available only after /usr is mounted.
Temporary files; cleared during the boot operation.
Root of a subtree for varying files. Varying files are files that are unique to a machine but that can grow to an arbitrary (that is, variable) size. An example is a log file.
System logging and accounting files.
Log files for cron(1M).
Directory where users' mail is kept.
Community service messages. This is not the same as USENET-style news.
NIS+ databases.
Root of a subtree for varying files associated with optional software packages.
Databases maintained by the software package management utilities.
Service access facility logging and accounting files.
Root directory for files used in printer spooling, mail delivery, cron(1M), at(1), and so forth.
Spooling lock files.
Line printer spool files. See lp(1).
Mail queued for delivery.
Spooled packages.
Queued uucp(1C) jobs.
Files deposited by uucp(1C).
Transitory files; this directory is not cleared during the boot operation.
uucp(1C) log and status files.
Databases needed for backwards compatibility with NIS and ypbind(1M); unnecessary after full transition to NIS+.
Because it is desirable to keep the root file system small and not volatile, on disk-based systems larger file systems are often mounted on /home, /opt, /usr, and /var.
The file system mounted on /usr contains architecture-dependent and architecture-independent sharable files. The subtree rooted at /usr/share contains architecture-independent sharable files; the rest of the /usr tree contains architecture-dependent files. By mounting a common remote file system, a group of machines with a common architecture may share a single /usr file system. A single /usr/share file system can be shared by machines of any architecture. A machine acting as a file server may export many different /usr file systems to support several different architectures and operating system releases. Clients usually mount /usr read-only so that they do not accidentally change any shared files.
The /usr file system contains the following subdirectories:
a.out libraries for the Binary Compatibility Package. See Binary Compatibility Guide
Primary location for standard system utilities.
C compilation system.
C compilation commands and system utilities.
Symbolic link to /usr/lib.
Demo programs and data.
root of a subtree for CDE Motif.
Primary location for CDE Motif system utilities.
Header files for CDE Motif.
Libraries for CDE Motif.
On-line reference manual pages for CDE Motif.
Game binaries and data.
Include headers (for C programs).
Solaris Java Virtual Machine.
Subtree of platform-independent loadable kernel modules, not needed in the root filesystem.
Program libraries, various architecture-dependent databases, and executables not invoked directly by the user (for example, system daemons).
Symbolic link to the most portable 64-bit Solaris interfaces.
Accounting scripts and binaries. See acct(1M).
Scheduling class-specific directories containing executables for priocntl(1) and dispadmin(1M).
Database files for spell(1).
troff(1) font description files.
File system type dependent modules; generally not intended to be invoked directly by the user.
Conversion tables for iconv(1).
Profiled libraries.
Localization databases.
Line printer subsystem databases and back-end executables.
Auxiliary programs for the mail(1) subsystem.
Internet network services.
Auxiliary NFS-related programs and daemons.
Position Independent Code (PIC) archives needed to rebuild the run-time linker.
Auxiliary programs for refer(1).
Scripts and commands for the system activity report package. See sar(1).
Auxiliary programs and daemons related to the service access facility.
64-bit SPARC libraries.
Auxiliary programs and databases for spell(1). This directory is only present when the Binary Compatibility Package is installed.
Auxiliary programs and daemons for uucp(1C).
Commands local to a site.
Entry points for foreign name service requests relayed using the network listener. See listen(1M).
Commands and files related to the optional Framed Access Command Environment (FACE) package. See face(1).
Programs that are being phased out.
Installation or mount point for the OpenWindows software.
Subtree of platform-specific objects which does not need to reside on the root filesystem. It contains a series of directories, one per supported platform. The semantics of the series of directories is equivalent to /platform, except for subdirectories which don't provide utility under one or the other (for example: /platform/include isn't needed).
Platform-dependent headers with semantics equivalent to /usr/include.
Platform-dependent objects with semantics equivalent to /usr/kernel.
Platform-dependent objects with semantics equivalent to /usr/lib.
Platform-dependent objects with semantics equivalent to /usr/sbin.
System administration files and directories.
Binaries for the Form and Menu Language Interpreter (FMLI) scripts. See fmli(1).
Executables and scripts for package management.
Executables for system administration.
Statically linked version of selected programs from /usr/bin and /usr/sbin. These are used to recover from broken dynamic linking and before all pieces necessary for dynamic linking are present.
Architecture-independent sharable files.
Architecture-independent databases.
Keyboard layout description tables.
Help files for mailx(1).
nroff(1) terminal tables.
Character set data files.
Auxiliary scripts and databases for spell(1).
Tab setting escape sequences.
Terminal description files for terminfo(4).
Macro packages and related files for text processing tools, for example, nroff(1) and troff(1).
Time zone information.
On-line reference manual pages (if present).
Source code for utilities and libraries.
SNAG files.
Berkeley compatibility package binaries. See Source Compatibility Guide
Berkeley compatibility package headers.
Berkeley compatibility package libraries.
Commands and files related to the optional FACE package. See face(1). Berkeley compatibility package libraries.
A machine with disks may export root file systems, swap files, and /usr file systems to diskless or partially-disked machines that mount them into the standard file system hierarchy. The standard directory tree for sharing these file systems from a server is:
The default root of the exported file system tree.
The exported /usr file system supporting architecture-name for the current release.
The exported /usr file system supporting architecture-name for release-name.
The exported common /usr/share directory tree.
The exported common /usr/share directory tree for release-name.
The exported root file system for hostname.
The exported swap file for hostname.
The exported /var directory tree for hostname.
at(1), ex(1), face(1), fmli(1), iconv(1), lp(1), isainfo(1), mail(1), mailx(1), nroff(1), priocntl(1), refer(1), sar(1), sh(1), spell(1), troff(1), uname(1), uucp(1C), vi(1), acct(1M), cron(1M), dispadmin(1M), fsck(1M), init(1M), kernel(1M), mknod(1M), mount(1M), useradd(1M), ypbind(1M), mount(2), intro(4), terminfo(4)
NAME | SYNOPSIS | DESCRIPTION | SEE ALSO