Unix file types

The seven standard Unix file types are regular, directory, symbolic link, FIFO special, block special, character special, and socket as defined by POSIX. Different OS-specific implementations allow more types than what POSIX requires (e.g. Solaris doors). A file's type can be identified by the  command, which displays the type in the first character of the file-system permissions field.

For regular files, Unix does not impose or provide any internal file structure; therefore, their structure and interpretation is entirely dependent on the software using them. However, the  command can usually be used to determine what type of data they contain.

Numeric
In the stat structure, file type and permissions (the mode) are stored together in a st_mode bit field, which has a size of at least 12 bits (3 bits to specify the type among the seven possible types of files; 9 bits for permissions). The layout for permissions is defined by POSIX to be at the least-significant 9 bits, but the rest is undefined.

By convention, the mode is a 16-bit value written out as a six-digit octal number without a leading zero. The format part occupies the lead 4-bits (2 octal digits), and "010" (1000 in binary) usually stands for a regular file. The next 3 bits (1 digit) are usually used for setuid, setgid, and sticky. The last part is already defined by POSIX to contain the permission. An example is "100644" for a typical file. This format can be seen in git, tar, and ar, among other places.

The type of a file can be tested using macros like. Such a check is usually performed by masking the mode with  (often the octal number "170000" for the lead 4 bits convention) and checking whether the result matches. is not a core POSIX concept, but a X/Open System Interfaces (XSI) extension; systems conforming to only POSIX may use some other methods.

Mode string
Take for example one line in the  output: drwxr-xr-x 2 root root    0 Jan  1  1970 home

POSIX specifies the format of the output for the long format ( option). In particular, the first field (before the first space) is dubbed the "file mode string", here. Its first character describes the file type, here  (directory). The rest of this string indicates the file permissions.

Examples of implementations
The GNU coreutils version of  uses a call to , a glibc function (exposed in the gnulib library ) to get the mode string.

FreeBSD uses a simpler approach but allows a smaller number of file types.

Directory
The most common special file is the directory. The layout of a directory file is defined by the filesystem used. As several filesystems are available under Unix, both native and non-native, there is no one directory file layout.

A directory is marked with a  as the first letter in the mode field in the output of  or , e.g.

$ ls -dl / drwxr-xr-x 26 root root 4096 Sep 22 09:29 / $ stat / File: "/" Size: 4096           Blocks: 8          IO Block: 4096   directory Device: 802h/2050d     Inode: 128         Links: 26 Access: (0755/drwxr-xr-x) Uid: (    0/    root)   Gid: (    0/    root) ...

Symbolic link
A symbolic link is a reference to another file. This special file is stored as a textual representation of the referenced file's path (which means the destination may be a relative path, or may not exist at all).

A symbolic link is marked with an  (lower case  ) as the first letter of the mode string, e.g. in this abbreviated   output:

lrwxrwxrwx ... termcap -> /usr/share/misc/termcap lrwxrwxrwx ... S03xinetd -> ../init.d/xinetd

FIFO (named pipe)
One of the strengths of Unix has always been inter-process communication. Among the facilities provided by the OS are pipes, which connect the output of one process to the input of another. This is fine if both processes exist in the same parent process space, started by the same user, but there are circumstances where the communicating processes must use FIFOs, here referred to as named pipes. One such circumstance occurs when the processes must be executed under different user names and permissions.

Named pipes are special files that can exist anywhere in the file system. They can be created with the command  as in.

A named pipe is marked with a  as the first letter of the mode string, e.g. in this abbreviated   output:

prw-rw ... mypipe

Socket
A socket is a special file used for inter-process communication, which enables communication between two processes. In addition to sending data, processes can send file descriptors across a Unix domain socket connection using the  and   system calls.

Unlike named pipes which allow only unidirectional data flow, sockets are fully duplex-capable.

A socket is marked with an  as the first letter of the mode string, e.g.

srwxrwxrwx /tmp/.X11-unix/X0

Device file (block, character)
In Unix, almost all things are handled as files and have a location in the file system, even hardware devices like hard drives. The great exception is network devices, which do not turn up in the file system but are handled separately.

Device files are used to apply access rights to the devices and to direct operations on the files to the appropriate device drivers.

Unix makes a distinction between character devices and block devices. The distinction is roughly as follows:


 * Character devices provide only a serial stream of input or accept a serial stream of output
 * Block devices are randomly accessible

Although, for example, disk partitions may have both character devices that provide un-buffered random access to blocks on the partition and block devices that provide buffered random access to blocks on the partition.

A character device is marked with a  as the first letter of the mode string and a block device is marked with a , e.g. in this abbreviated   output:

crw-rw-rw- ... /dev/null brw-rw ... /dev/sda