Unix file types
|This article does not cite any references or sources. (December 2009)|
The structure and interpretation thereof is entirely dependent on how the file is interpreted by software.
Unix does however have some special files. These special files can be identified by the
ls -l command which displays the type of the file in the first alphabetic letter of the file system permissions field. A normal file is indicated by a dash ('
Being the well known entity files are, files are also called "regular files" to distinguish them from "special files". They show up in
ls -l without a specific character in the mode field:
$ ls -dl /etc/passwd -rw-r-—r-- ... /etc/passwd
The most common special file is the directory. The layout of a directory file is defined by the filesystem used. As several filesystems, both native and non-native, are available under Unix, there is not one directory file layout.
A directory is marked with a
d as the first letter in the mode field in the output of `
ls -dl` or `
$ 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) ...
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
l (lower case
L) as the first letter of the mode string, e.g.
lrwxrwxrwx ... termcap -> /usr/share/misc/termcap lrwxrwxrwx ... S03xinetd -> ../init.d/xinetd
One of the strengths of Unix has always been inter-process communication. Amongst the facilities provided by the OS are pipes. These pipes connect the output of one process to the input of another. This is fine if both processes are living in the same parent process space, started by the same user. There are however circumstances where the communicating processes must use named pipes. One such circumstance is that the processes have to be executed under different user names and permissions.
These named pipes are special files that can exist anywhere in the file system. These named pipe special files are made with the command
mkfifo as in
A named pipe is marked with a
p as the first letter of the mode string, e.g.
prw-rw---- ... mypipe
A socket is a special file used for inter-process communication. These allow communication between two processes. In addition to sending data, processes can send file descriptors across a Unix domain socket connection using the
recvmsg() system calls.
Unlike named pipes sockets are fully duplex-capable.
A socket is marked with an
s as the first letter of the mode string, e.g.
srwxrwxrwx ... /tmp/.X11-unix/X0
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 for devices and the files that represent them are network devices that do not turn up in the file system but are handled separately.
Device files are used to apply access rights 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 output;
- block devices are randomly accessible;
although, for example, disk partitions may have both character devices that provide unbuffered 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
c as the first letter of the mode string. Likewise, a block device is marked with a
A door is marked with a
D (upper case) as the first letter of the mode string, e.g.
Dr--r--r-- ... name_service_door