1 .\" Copyright (c) 1980, 1990, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" This code is derived from software contributed to Berkeley by
5 .\" the Institute of Electrical and Electronics Engineers, Inc.
7 .\" Redistribution and use in source and binary forms, with or without
8 .\" modification, are permitted provided that the following conditions
10 .\" 1. Redistributions of source code must retain the above copyright
11 .\" notice, this list of conditions and the following disclaimer.
12 .\" 2. Redistributions in binary form must reproduce the above copyright
13 .\" notice, this list of conditions and the following disclaimer in the
14 .\" documentation and/or other materials provided with the distribution.
15 .\" 3. All advertising materials mentioning features or use of this software
16 .\" must display the following acknowledgement:
17 .\" This product includes software developed by the University of
18 .\" California, Berkeley and its contributors.
19 .\" 4. Neither the name of the University nor the names of its contributors
20 .\" may be used to endorse or promote products derived from this software
21 .\" without specific prior written permission.
23 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
24 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
25 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
26 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
27 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
28 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
29 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
30 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
31 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
32 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
35 .\" @(#)ln.1 8.2 (Berkeley) 12/30/93
55 .Ar source_file Ar target_file
59 utility creates a new directory entry (linked file) which has the
60 same modes as the original file.
61 It is useful for maintaining multiple copies of a file in many places
62 at once without using up storage for the
67 There are two types of links; hard links and symbolic links.
70 to a file is one of the differences between a hard and symbolic link.
72 The options are as follows:
75 Unlink any already existing file, permitting the link to occur.
77 Create a symbolic link.
81 to be verbose, showing files as they are processed.
89 A hard link to a file is indistinguishable from the original directory entry;
90 any changes to a file are effectively independent of the name used to reference
92 Hard links may not normally refer to directories and may not span file systems.
94 A symbolic link contains the name of the file to
95 which it is linked. The referenced file is used when an
97 operation is performed on the link.
100 on a symbolic link will return the linked-to file; an
102 must be done to obtain information about the link.
105 call may be used to read the contents of a symbolic link.
106 Symbolic links may span file systems and may refer to directories.
108 Given one or two arguments,
110 creates a link to an existing file
114 is given, the link has that name;
116 may also be a directory in which to place the link;
117 otherwise it is placed in the current directory.
118 If only the directory is specified, the link will be made
119 to the last component of
122 Given more than two arguments,
126 to all the named source files.
127 The links made will have the same name as the files being linked to.
129 When the utility is called as
131 exactly two arguments must be supplied,
132 neither of which may specify a directory.
133 No options may be supplied in this simple mode of operation,
136 operation using the two passed arguments.
147 option is non-standard and its use in scripts is not recommended.