svcadm(8)을 검색하려면 섹션에서 8 을 선택하고, 맨 페이지 이름에 svcadm을 입력하고 검색을 누른다.
filesystem(7)
fi...m(7)Standards, Environments, Macros, Character Sets, and miscellanfyi...m(7)
NAME
filesystem, hier - file system organization
SYNOPSIS
/
DESCRIPTION
The file system is a hierarchical structure of descendent file systems
and directories that are used to organize system-related components and
binaries as well as non-system-related components and home directories
in the Oracle Solaris OS. By default, the root file system is installed
within a ZFS root pool and specifically, is a ZFS file system with sep‐
arate directories of system-related components, such as etc, usr, and
var, that must be available for the system to function correctly. After
a system is installed, the root of the Solaris file system is mounted
to make the files and directories within accessible. See the
datasets(7) manual page for more information on the ZFS datasets cre‐
ated when a Solaris system is installed.
All subdirectories of the root file system that are part of the Oracle
Solaris OS, with the exception of /var, must be contained in the same
file system as the root file system. In addition, all packaged software
must reside in the root pool, with the exception of the swap and dump
devices. A default swap device and dump device are created automati‐
cally as ZFS volumes in the root pool when a system is installed.
The following file system content descriptions make use of platform,
platform-dependent, platform-independent, and platform-specific terms.
Platform refers to a system's Instruction Set Architecture or processor
type as returned by the uname -i command. Platform-dependent refers to
a file that is installed on all platforms and whose contents vary de‐
pending on the platform. Like a platform-dependent file, a platform-in‐
dependent file is installed on all platforms. However, the contents of
the latter type remains the same on all platforms. An example of a
platform-dependent file is compiled, executable program. An example of
a platform-independent file is a standard configuration file, such as
/etc/hosts. Unlike a platform-dependent or a platform-independent file,
the platform-specific file is installed only on a subset of supported
platforms. Most platform-specific files are gathered under /platform
and /usr/platform.
Root File System
The root file system contains files and directories that are critical
for system operation, such as the kernel, the device drivers, and the
programs used to boot the system. These components are described below.
The root (/) directory also contains mount point directories where lo‐
cal and remote file systems can be attached to the file system hierar‐
chy.
/
Root directory of the entire file system name space. This is a spe‐
cial file system that is mounted by the kernel at system boot time.
/boot
Directory that contains files and executables that are needed for
booting the system.
/bin
Symbolic link to the /usr/bin directory that contains system exe‐
cutables and scripts.
/dev
Directory that contains special device files. Typically, device
files are built to match the kernel and hardware configuration of
the system.
/devices
Mount point directory for the devfs file system that manages the
device name space.
/etc
Directory that contains platform-dependent administrative and con‐
figuration files and databases that are not shared among systems.
This directory defines the system's identity. An approved installa‐
tion location for bundled Solaris software.
/etc/dfs/sharetab
The file is a mounted sharefs(4FS) file system that provides read-
only access to the state of all shares currently loaded by the ker‐
nel.
/etc/mnttab
The file is a mounted file system that provides read-only access to
the table of mounted file systems for the current host. Its format
is documented in mnttab(5).
/export/home or /home
Directory or file system mount point for user home directories,
which store user files. By default, the /home directory is an auto‐
mounted file system.
/kernel
Directory of platform-dependent 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 ker‐
nel(8). An approved installation location for bundled Oracle So‐
laris software and for add-on system software.
/lib
Directory that contains core system libraries. Historically, this
directory contained essential library components for system
startup.
/media
Directory for accessing removable media that is automatically
mounted.
/mnt
Default temporary mount point directory for file systems. This
empty directory is used to temporarily mount a file system.
/net
Temporary mount point directory for file systems that are mounted
by the automounter.
/opt
Directory for unbundled application packages.
/platform
Directory of platform-specific objects that need to reside in the
root file system. It contains a series of directories, one per sup‐
ported platform. The semantics of the series of directories is
equivalent to / (root).
/proc
Mount point directory for the process file system.
/root
Home directory for the root user.
/rpool
Mount point directory for the ZFS boot-related components. By de‐
fault, the root pool is named rpool during installation.
/sbin
Symbolic link to the /usr/sbin directory.
/system/contract
Mount point directory for the contract file system. See ctfs(4FS).
/system/object
Mount point directory for the kernel object file system. See ob‐
jfs(4FS).
/system/volatile
Mount point for a writable tmpfs(4FS) file system available immedi‐
ately after boot. Primarily for system specific use but also avail‐
able for use by 3rd party.
/system/zones
Directory that is shared across several boot environments, and is
resident on a separate dataset beneath the zpool containing boot
environments. This is the default parent of zonepaths.
/tmp
Directory that contains temporary files that are removed during a
boot operation.
/usr
Directory that contains platform-dependent and platform-independent
binaries and files. The /usr/share subdirectory contains platform-
independent files. The rest of the /usr directory contains plat‐
form-dependent files.
/usr/bin
Directory that contains platform-dependent, user-invoked executa‐
bles. These are commands that users expect to be run as part of
their normal $PATH. An approved installation location for bundled
Oracle Solaris software. The analogous location for unbundled sys‐
tem software or for applications is /opt/packagename/bin.
/usr/lib
Directory that augments the contents of /lib with additional system
libraries, and other supporting files that are required by programs
at runtime.
/usr/gnu
Directory that contains GNU versions of commands that are not used
as the default Solaris implementation but which are provided for
familiarity with other platforms. The executables are located in
/usr/gnu/bin, which can be placed before /usr/bin in $PATH if the
GNU versions are preferred. In addition, all the commands in this
directory tree are accessible by default from /usr/bin through sym‐
links which are the command name prefixed by the 'g' character. For
example:
/usr/bin/ggrep -> ../gnu/bin/grep
If the GNU compatibility facet (compat.gnu-links) is set to False
by pkg(1), all of the g* symlinks will be removed from /usr/bin. If
this has been done, the links can be restored by running pkg
change-facet compat.gnu-links=True as a user with all privileges.
/usr/java
Directory that contains Java files and executables.
/usr/sbin
Contains essential executables used in the booting process and in
manual system recovery. Historically, this directory was needed to
recover the system before the /usr file system was mounted. In this
Oracle Solaris release, /usr is a directory, not a separate file
system and is available when the root file system is mounted.
/usr/sunos
Directory that contains versions of /usr/bin commands that have
been kept for compatibility with older releases of Solaris. The ex‐
ecutables are located in /usr/sunos/bin, which can be placed before
/usr/bin in $PATH if the older versions are preferred.
/var
Directory or file system that contains varying files that are
unique to a system but can grow to an arbitrary or variable size.
An example is a log file. An approved installation location for
bundled Oracle Solaris software.
/var/logadm
State information for the logadm service, particularly timestamps
for last rotation.
/var/share
Directory that is shared across several boot environments, and is
resident on a separate dataset beneath the zpool containing boot
environments. Packages should not deliver content here, since pack‐
age metadata in a given boot environment may not reflect the cur‐
rent content of /var/share.
Packages may deliver directories to /var/.migrate, which will be
created automatically beneath /var/share during boot. See pkg(7)
and Packaging and Delivering Software With the Image Packaging Sys‐
tem in Oracle Solaris 11.4 for a description of how to share data
across boot environments.
Symlinks are delivered to /var to point to each shared directory.
If existing datasets attempt to mount on one of those symlinks (for
example, users with an existing dataset that normally mounts on
/var/mail), then those datasets will be mounted beneath /var/share,
since filesystem mounts traverse symlinks. The dataset will still
be accessible through the original mountpoint.
/var/share/user
A persistent per host local file system directory for per user con‐
tent. Not to be confused with the users home directory which may or
may not be on a local filesystem.
Directories under here are named with the uid with a symlink named
using the username pointing to the uid.
All content in here is assumed to be private to the creating appli‐
cation and the user must not manually manipulate the files even
though they may be owned by the user themsevles.
The per user directories are created by useradd(8) and by the
pam_sm_setcred(3PAM) method of pam_unix_auth(7).
/tmp/volatile-user
Similar to /var/share/user but does not persist over reboot.
Unlike /var/share/user the /tmp/volatile-user only has uid directo‐
ries, there is no symlink or other use of the username.
/var/tmp
Directory that contains files that vary in size or presence during
normal system operations. The content of this directory is not re‐
moved during a boot operation. It is possible to change the default
behavior for /var/tmp to clear all of the files except editor tem‐
porary files by setting the clean_vartmp property value of the
rmtmpfiles service. This is done with the following commands:
# svccfg -s svc:/system/rmtmpfiles setprop \
options/clean_vartmp = "true"
# svcadm refresh svc:/system/rmtmpfiles:default
The solaris.smf.value.rmtmpfiles authorization is required to mod‐
ify this property.
Directory that is shared across several boot environments and a
separate file system.
SEE ALSO
isainfo(1), svcs(1), uname(1), mount(2), pam_sm_setcred(3PAM),
ctfs(4FS), devfs(4FS), objfs(4FS), Intro(5), proc(5), datasets(7),
pam_unix_auth(7), automount(8), automountd(8), boot(8), init(8), ker‐
nel(8), mount(8), svcadm(8), svccfg(8), useradd(8), zfs(8), zpool(8)
Packaging and Delivering Software With the Image Packaging System in
Oracle Solaris 11.4
HISTORY
The various members of the filesystem hierarchy first appeared in the
listed release of Solaris:
tab() box; cw(4.71i) |cw(0.79i) lw(4.71i) |lw(0.79i) PATHRELEASE _
/tmp/volatile-user, /var/share/user11.4.0 _ /system/zones11.2.0 _
/var/share11.1.0 _ T{ /media, /root, /system/volatile, /usr/gnu,
/usr/sunos T}11.0.0 _ /var/logadm10 1/13 (Update 11) _ /rpool10 8/08
(Update 6) _ /system/contract, /system/object10 3/05 _ /var/run8 _
/boot7 _ /platform2.5 _ T{ /devices, /etc/dfs/sharetab, /etc/mnttab,
/kernel, /opt, /proc, /usr/sbin T}2.0 _ T{ /, /bin, /dev, /etc,
/export/home, /home, /lib, /mnt, /net, /sbin, /tmp, /usr, /usr/bin,
/usr/lib, /var, /var/tmp T}1.0
Oracle Solaris 11.4 12 Sep 2023 fi...m(7)