180 lines
5.1 KiB
Groff
180 lines
5.1 KiB
Groff
.\" Copyright (c) 1980, 1990, 1993
|
|
.\" The Regents of the University of California. All rights reserved.
|
|
.\"
|
|
.\" This code is derived from software contributed to Berkeley by
|
|
.\" the Institute of Electrical and Electronics Engineers, Inc.
|
|
.\"
|
|
.\" Redistribution and use in source and binary forms, with or without
|
|
.\" modification, are permitted provided that the following conditions
|
|
.\" are met:
|
|
.\" 1. Redistributions of source code must retain the above copyright
|
|
.\" notice, this list of conditions and the following disclaimer.
|
|
.\" 2. Redistributions in binary form must reproduce the above copyright
|
|
.\" notice, this list of conditions and the following disclaimer in the
|
|
.\" documentation and/or other materials provided with the distribution.
|
|
.\" 3. All advertising materials mentioning features or use of this software
|
|
.\" must display the following acknowledgement:
|
|
.\" This product includes software developed by the University of
|
|
.\" California, Berkeley and its contributors.
|
|
.\" 4. Neither the name of the University nor the names of its contributors
|
|
.\" may be used to endorse or promote products derived from this software
|
|
.\" without specific prior written permission.
|
|
.\"
|
|
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
|
|
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
|
|
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
.\" SUCH DAMAGE.
|
|
.\"
|
|
.\" @(#)ln.1 8.2 (Berkeley) 12/30/93
|
|
.\" $FreeBSD$
|
|
.\"
|
|
.Dd December 30, 1993
|
|
.Dt LN 1
|
|
.Os BSD 4
|
|
.Sh NAME
|
|
.Nm ln ,
|
|
.Nm link
|
|
.Nd make links
|
|
.Sh SYNOPSIS
|
|
.Nm
|
|
.Op Fl fisv
|
|
.Ar source_file
|
|
.Op target_file
|
|
.Nm
|
|
.Op Fl fisv
|
|
.Ar source_file ...
|
|
.Op target_dir
|
|
.Nm link
|
|
.Ar source_file Ar target_file
|
|
.Sh DESCRIPTION
|
|
The
|
|
.Nm
|
|
utility creates a new directory entry (linked file) which has the
|
|
same modes as the original file.
|
|
It is useful for maintaining multiple copies of a file in many places
|
|
at once without using up storage for the
|
|
.Dq copies ;
|
|
instead, a link
|
|
.Dq points
|
|
to the original copy.
|
|
There are two types of links; hard links and symbolic links.
|
|
How a link
|
|
.Dq points
|
|
to a file is one of the differences between a hard and symbolic link.
|
|
.Pp
|
|
The options are as follows:
|
|
.Bl -tag -width flag
|
|
.It Fl f
|
|
If the target file already exists,
|
|
then unlink it so that the link may occur.
|
|
(The
|
|
.Fl f
|
|
option overrides any previous
|
|
.Fl i
|
|
options.)
|
|
.It Fl i
|
|
Cause
|
|
.Nm
|
|
to write a prompt to standard error if the target file exists.
|
|
If the response from the standard input begins with the character
|
|
.Sq Li y
|
|
or
|
|
.Sq Li Y ,
|
|
then unlink the target file so that the link may occur.
|
|
Otherwise, do not attempt the link.
|
|
(The
|
|
.Fl i
|
|
option overrides any previous
|
|
.Fl f
|
|
options.)
|
|
.It Fl s
|
|
Create a symbolic link.
|
|
.It Fl v
|
|
Cause
|
|
.Nm
|
|
to be verbose, showing files as they are processed.
|
|
.El
|
|
.Pp
|
|
By default,
|
|
.Nm
|
|
makes
|
|
.Em hard
|
|
links.
|
|
A hard link to a file is indistinguishable from the original directory entry;
|
|
any changes to a file are effectively independent of the name used to reference
|
|
the file.
|
|
Hard links may not normally refer to directories and may not span file systems.
|
|
.Pp
|
|
A symbolic link contains the name of the file to
|
|
which it is linked. The referenced file is used when an
|
|
.Xr open 2
|
|
operation is performed on the link.
|
|
A
|
|
.Xr stat 2
|
|
on a symbolic link will return the linked-to file; an
|
|
.Xr lstat 2
|
|
must be done to obtain information about the link.
|
|
The
|
|
.Xr readlink 2
|
|
call may be used to read the contents of a symbolic link.
|
|
Symbolic links may span file systems and may refer to directories.
|
|
.Pp
|
|
Given one or two arguments,
|
|
.Nm
|
|
creates a link to an existing file
|
|
.Ar source_file .
|
|
If
|
|
.Ar target_file
|
|
is given, the link has that name;
|
|
.Ar target_file
|
|
may also be a directory in which to place the link;
|
|
otherwise it is placed in the current directory.
|
|
If only the directory is specified, the link will be made
|
|
to the last component of
|
|
.Ar source_file .
|
|
.Pp
|
|
Given more than two arguments,
|
|
.Nm
|
|
makes links in
|
|
.Ar target_dir
|
|
to all the named source files.
|
|
The links made will have the same name as the files being linked to.
|
|
.Pp
|
|
When the utility is called as
|
|
.Nm link ,
|
|
exactly two arguments must be supplied,
|
|
neither of which may specify a directory.
|
|
No options may be supplied in this simple mode of operation,
|
|
which performs a
|
|
.Xr link 2
|
|
operation using the two passed arguments.
|
|
.Sh SEE ALSO
|
|
.Xr link 2 ,
|
|
.Xr lstat 2 ,
|
|
.Xr readlink 2 ,
|
|
.Xr stat 2 ,
|
|
.Xr symlink 2 ,
|
|
.Xr symlink 7
|
|
.Sh COMPATIBILITY
|
|
The
|
|
.Fl i
|
|
and
|
|
.Fl v
|
|
options are non-standard and their use in scripts is not recommended.
|
|
.Sh HISTORY
|
|
An
|
|
.Nm
|
|
command appeared in
|
|
.At v1 .
|
|
The simplified
|
|
.Nm link
|
|
command conforms to
|
|
.St -susv2 .
|