2 .\" Copyright (c) 1980, 1990, 1993
3 .\" The Regents of the University of California. All rights reserved.
5 .\" This code is derived from software contributed to Berkeley by
6 .\" the Institute of Electrical and Electronics Engineers, Inc.
8 .\" Redistribution and use in source and binary forms, with or without
9 .\" modification, are permitted provided that the following conditions
11 .\" 1. Redistributions of source code must retain the above copyright
12 .\" notice, this list of conditions and the following disclaimer.
13 .\" 2. Redistributions in binary form must reproduce the above copyright
14 .\" notice, this list of conditions and the following disclaimer in the
15 .\" documentation and/or other materials provided with the distribution.
16 .\" 4. Neither the name of the University nor the names of its contributors
17 .\" may be used to endorse or promote products derived from this software
18 .\" without specific prior written permission.
20 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
32 .\" @(#)ln.1 8.2 (Berkeley) 12/30/93
52 .Ar source_file Ar target_file
56 utility creates a new directory entry (linked file) which has the
57 same modes as the original file.
58 It is useful for maintaining multiple copies of a file in many places
59 at once without using up storage for the
64 There are two types of links; hard links and symbolic links.
67 to a file is one of the differences between a hard and symbolic link.
69 The options are as follows:
72 If the target file already exists,
73 then unlink it so that the link may occur.
76 option overrides any previous
80 If the target file already exists and is a directory, then remove it
81 so that the link may occur.
84 option should be used with either
94 option is a no-op unless
102 is a symbolic link, do not follow it.
103 This is most useful with the
105 option, to replace a symlink which may point to a directory.
109 to write a prompt to standard error if the target file exists.
110 If the response from the standard input begins with the character
114 then unlink the target file so that the link may occur.
115 Otherwise, do not attempt the link.
118 option overrides any previous
124 for compatibility with other
128 Create a symbolic link.
132 to be verbose, showing files as they are processed.
140 A hard link to a file is indistinguishable from the original directory entry;
141 any changes to a file are effectively independent of the name used to reference
143 Hard links may not normally refer to directories and may not span file systems.
145 A symbolic link contains the name of the file to
147 The referenced file is used when an
149 operation is performed on the link.
152 on a symbolic link will return the linked-to file; an
154 must be done to obtain information about the link.
157 call may be used to read the contents of a symbolic link.
158 Symbolic links may span file systems and may refer to directories.
160 Given one or two arguments,
162 creates a link to an existing file
166 is given, the link has that name;
168 may also be a directory in which to place the link;
169 otherwise it is placed in the current directory.
170 If only the directory is specified, the link will be made
171 to the last component of
174 Given more than two arguments,
178 to all the named source files.
179 The links made will have the same name as the files being linked to.
181 When the utility is called as
183 exactly two arguments must be supplied,
184 neither of which may specify a directory.
185 No options may be supplied in this simple mode of operation,
188 operation using the two passed arguments.
196 options are non-standard and their use in scripts is not recommended.
197 They are provided solely for compatibility with other
205 extention and should not be used in portable scripts.