Series 300 Only

NAME

symlink − symbolic link

DESCRIPTION

A symbolic link is a type of file that indirectly refers to ("points to") a path name.  Also known as a soft link, a symbolic link contains a relative or absolute path name.  If a symbolic link to a relative path name is encountered during path name interpretation, the contents of the symbolic link replace the symbolic link component and is expanded into the path name being interpreted.  If a symbolic link to an absolute path name is encountered, the contents of the symbolic link replaces all components up to and including the symbolic link and is expanded into the remainder of the path name. 

Thus, given path name /a/b/c/d, where c is a symbolic link to ../x/y, the original path name would be interpreted as /a/b/../x/y/d.  If, instead, c were a symbolic link to an absolute path name such as /v/w, the same path name would be interpreted as /v/w/d.  All symbolic links are interpreted in this manner except when the symbolic link is the last component of a path name passed as a parameter to one of the following system calls: readlink(2), rename(2), symlink(2), unlink(2), and lstat(2). With these calls, the symbolic link itself is accessed or affected.

Unlike normal (hard) links, a symbolic link may refer to any arbitrary path name and may span different logical devices (volumes).  The path name may be that of any type of file (including a directory, or another symbolic link) or it may even be invalid if no such path exists in the system.  Thus it is possible to make symbolic links point to themselves or other symbolic links in such a way that they form a closed loop.  The system detects this situation by limiting the number of symbolic links it traverses while translating a path name.  The mode and ownership of a symbolic link is ignored by the system. 

Symbolic links can be created using ln (on cp(1)) or symlink(2).

NETWORKING FEATURES

RFA

When a symbolic link that refers to an absolute path name is located on a remote node (that is, using the Remote File Access (RFA) facility; see mknod(1M)), the path name is interpreted relative to the root of the remote node, not the node on which the process is executing.

AUTHOR

Symlink was developed by HP and the University of California, Berkeley. 

SEE ALSO

cp(1), symlink(2), readlink(2), link(2), stat(2), mknod(1M). 

Hewlett-Packard Company  —  Version B.1,  May 11, 2021