Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

link(1m) [opensolaris man page]

link(1M)						  System Administration Commands						  link(1M)

NAME

       link, unlink - link and unlink files and directories

SYNOPSIS

       /usr/sbin/link  existing-file new-file

       /usr/xpg4/bin/link  existing-file new-file

       /usr/sbin/unlink file

DESCRIPTION

       The link and unlink commands link and unlink files and directories. Only super-users can use these commands on directories.

       Use  link  to  create  a new file that points to an existing file. The  existing-file and  new-file operands  specify the existing file and
       newly-created files.  See OPERANDS.

       link and  unlink directly invoke the link(2) and unlink(2) system calls, performing exactly what they are told to  do  and  abandoning  all
       error checking. This differs from the  ln(1) command. See  ln(1).

       While linked files and directories can be removed using unlink, it is safer to use rm(1) and rmdir(1) instead. See  rm(1) and  rmdir(1).

   /usr/xpg4/bin/link
       If  the	existing  file being hard linked is itself a symbolic link, then the newly created file (new-file) will be a hard link to the file
       referenced by the symbolic link, not to the symbolic link object itself (existing-file).

OPERANDS

       The following operands are supported:

       existing-file	Specifies the name of the existing file to be linked.

       file		Specifies the name of the file to be unlinked.

       new-file 	Specifies the name of newly created (linked) file.

ENVIRONMENT VARIABLES

       See  environ(5) for descriptions of the following environment variables that affect the execution of  link: LANG, LC_ALL, LC_CTYPE, LC_MES-
       SAGES, and NLSPATH.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWcsu			   |
       +-----------------------------+-----------------------------+

   /usr/xpg4/bin/link
       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWxcu4			   |
       +-----------------------------+-----------------------------+
       |Interface Stability	     |Standard			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       ln(1), rm(1), link(2), unlink(2), attributes(5), environ(5), standards(5)

SunOS 5.11							    9 Oct 2002								  link(1M)

Check Out this Related Man Page

symlink(4)						     Kernel Interfaces Manual							symlink(4)

NAME

       symlink - symbolic link

DESCRIPTION

       A symbolic (or soft ) link is a file whose name indirectly refers (points) to a relative or absolute path name.

       During  path  name  interpretation,  a symbolic link to a relative path name is expanded to the path name being interpreted, and a symbolic
       link to an absolute path name is replaced with the path name being interpreted.

       Thus, given the path name

	      If is a symbolic link to a relative path name such as the path name is interpreted as

	      If is a symbolic link to an absolute path name such as the path name is interpreted as

       All symbolic links are interpreted in this manner, with one exception: when the symbolic link is the last component of a path name,  it	is
       passed  as  a  parameter  to  one of the system calls: or (see readlink(2), rename(2), symlink(2), unlink(2), chown(2) and lstat(2)).  With
       these calls, the symbolic link, itself, is accessed or affected.

       Unlike normal (hard) links, a symbolic link can refer to any arbitrary path name and can span different logical devices (volumes).

       The path name can be that of any type of file (including a directory or another symbolic link), and may be invalid if no such  path  exists
       in  the	system.   (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, which means that affects the actual file, but not the  file	containing
       the symbolic link (see chmod(1)).

       Symbolic links can be created using or (see ln(1) and symlink(2)).

AUTHOR

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

SEE ALSO

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

																	symlink(4)
Man Page