Everything in Solaris is a file—for example, a regular file, a directory, a link, a command, and a device. Information about a file is contained inside a data structure called an inode. The maximum number of modes you can create on a file system determines the maximum number of files that can be created and depends on the file system
Files can be stored on a permanent storage medium (the disk) or in a volatile storage medium (the memory); the corresponding file systems are called disk-based file systems and
Solaris offers commands to monitor disk space usage at different levels of detail:
df
at the file system level,
du
at the file level, and
quot
at the
Most of the file systems that you will manage as a system administrator reside on a disk, and the disk must be managed as well. Therefore, in the
Only the connected devices have entries in the /devices directory, and the /dev directory contains symbolic links to these entries (files).
Unmount a file system before running the fsck command on it, in order to avoid generating inconsistencies during the repair.
A hard link cannot point to a file across the file systems because the file and the link must have the same inode.
The fsck is used not only to check the file system inconsistencies but to repair them.
Deleting a file in the /proc directory does not kill the corresponding process.
Files in the /tmp and /var/run directories are deleted when the system is rebooted.
The command ln creates a hard link by default if you do not give the option - s for creating the symbolic link.
Logging is enabled by default in Solaris 10 UFS.
You can create a multiterabyte UFS in Solaris 10 with a size of up to 16 terabytes and a maximum file size of up to about 1 terabyte.
A hard link can only point to a file, whereas a symbolic link can point to either a file or a directory.
The
/tmp
directory contains temporary
|
q |
Everything in Solaris is a file: regular files, directories, commands, links, devices, etc. |
|
q |
Information about a file is contained inside a data structure called inode. |
|
q |
The maximum number of files that you can create on a system depends on the maximum number of inodes that you can create, which in
|
|
q |
The general associations of disk-based file systems to the storage media are as
|
|
q |
Solaris 10 supports network file system (NFS) version 4. |
|
q |
Solaris supports the following
|
|
q |
The /proc directory contains information about the active processes on the system. |
|
q |
The devices on Solaris 10 are managed by device file system (
|
|
q |
UNIX file system (UFS) is the default file system for Solaris. |
|
q |
File system inconsistencies arise when the system is shut down improperly or from hardware errors, such as disk errors. |
|
q |
The inconsistencies can be checked and repaired by using the fsck command. |
|
q |
The
fsck
runs automatically during the system
|
|
q |
You must
|
|
q |
The df command is used to get a report on disk usage by the file systems. |
|
q |
The du command is used to get a report on disk usage by directories and files. |
|
q |
The quot command is used to get a report on disk usage by users. |
|
q |
The links are created with the following command:
ln [-fs] <source> [<target>] |
|
q |
The hard link is created by default, whereas the symbolic link is created with the -s option. |
|
q |
The links are removed with the following command:
rm [<linkName>] |
|
q |
A file can be removed without removing its symbolic link, but all of its hard links must be removed. Unless the last hard link is removed, the file content will still exist. |