This chapter describes commands which create special types of files (and
rmdir, which removes directories, one special file type).
Although Unix-like operating systems have markedly fewer special file types than others, not everything can be treated only as the undifferentiated byte stream of normal files. For example, when a file is created or removed, the system must record this information, which it does in a directory---a special type of file. Although you can read directories as normal files, if you're curious, in order for the system to do its job it must impose a structure, a certain order, on the bytes of the file. Thus it is a "special" type of file.
Besides directories, other special file types include named pipes (FIFOs), symbolic links, sockets, and so-called special files.
ln: Make links between files
ln makes links between files. By default, it makes hard links;
with the `-s' option, it makes symbolic (or soft) links.
Synopses:
ln [option]... source [dest] ln [option]... source... directory
If the last argument names an existing directory, ln links each
source file into a file with the same name in that directory.
(But see the description of the `--no-dereference' option below.)
If only one file is given, it links that file into the current directory.
Otherwise, if only two files are given, it links the first onto the
second. It is an error if the last argument is not a directory and more
than two files are given. By default, it does not remove existing
files.
A hard link is another name for an existing file; the link and the original are indistinguishable. (Technically speaking, they share the same inode, and the inode contains all the information about a file--indeed, it is not incorrect to say that the inode is the file.) On all existing implementations, you cannot make a hard links to directories, and hard links cannot cross filesystem boundaries. (These restrictions are not mandated by POSIX, however.)
Symbolic links (symlinks for short), on the other hand, are a special file type (which not all kernels support; in particular, system V release 3 (and older) systems lack symlinks) in which the link file actually refers to a different file, by name. When most operations (opening, reading, writing, and so on) are passed the symbolic link file, the kernel automatically dereferences the link and operates on the target of the link. But some operations (e.g., removing) work on the link file itself, rather than on its target. See section `Symbolic Links' in GNU C library.
The program accepts the following options. Also see section Common options.
ln can
treat the destination just as it would a normal directory and create
the link in it. On the other hand, the destination can be viewed as a
non-directory--as the symlink itself. In that case, ln
must delete or backup that symlink before creating the new link.
The default is to treat a destination that is a symlink to a directory
just like a directory.
mkdir: Make directories
mkdir creates directories with the specified names. Synopsis:
mkdir [option]... name...
It is not an error if a name is already a directory; mkdir
simply proceeds. But if a name is an existing file and is
anything but a directory, mkdir complains.
The program accepts the following options. Also see section Common options.
chmod and uses 0777 (read, write and execute allowed for
everyone) minus the bits set in the umask for the point of the
departure. See section File permissions.
mkfifo: Make FIFOs (named pipes)
mkfifo creates FIFOs (also called named pipes) with the
specified names. Synopsis:
mkfifo [option] name...
A FIFO is a special file type that permits independent processes to communicate. One process opens the FIFO file for writing, and another for reading, after which data can flow as with the usual anonymous pipe in shells or elsewhere.
The program accepts the following option. Also see section Common options.
chmod and uses 0666 (read and write allowed for everyone) minus
the bits set in the umask for the point of departure. See section File permissions.
mknod: Make block or character special files
mknod creates a FIFO, character special file, or block special
file with the specified name. Synopsis:
mknod [option]... name type [major minor]
Unlike the phrase "special file type" above, the term special
file has a technical meaning on Unix: something that can generate or
receive data. Usually this corresponds to a physical piece of hardware,
e.g., a printer or a disk. (These files are typically created at
system-configuration time.) The mknod command is what creates
files of this type. Such devices can be read either a character at a
time or a "block" (many characters) at a time, hence we say there are
block special files and character special files.
The arguments after name specify the type of file to make:
When making a block or character special file, the major and minor device numbers must be given after the file type.
The program accepts the following option. Also see section Common options.
chmod and uses 0666 minus the bits set in the umask as the point
of departure. See section File permissions.
rmdir: Remove empty directories
rmdir removes empty directories. Synopsis:
rmdir [option]... directory...
If any directory argument does not refer to an existing empty directory, it is an error.
The program accepts the following option. Also see section Common options.
See section rm: Remove files or directories, for how to remove non-empty directories (recursively).
Go to the first, previous, next, last section, table of contents.