1 .\" $NetBSD: link.2,v 1.26 2011/08/08 19:50:17 wiz Exp $
3 .\" Copyright (c) 1980, 1991, 1993, 2011
4 .\" The Regents of the University of California. All rights reserved.
6 .\" Redistribution and use in source and binary forms, with or without
7 .\" modification, are permitted provided that the following conditions
9 .\" 1. Redistributions of source code must retain the above copyright
10 .\" notice, this list of conditions and the following disclaimer.
11 .\" 2. Redistributions in binary form must reproduce the above copyright
12 .\" notice, this list of conditions and the following disclaimer in the
13 .\" documentation and/or other materials provided with the distribution.
14 .\" 3. Neither the name of the University nor the names of its contributors
15 .\" may be used to endorse or promote products derived from this software
16 .\" without specific prior written permission.
18 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
19 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
20 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
21 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
22 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
23 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
24 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
25 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
26 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
27 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30 .\" @(#)link.2 8.3 (Berkeley) 1/12/94
37 .Nd make a hard file link
43 .Fn link "const char *name1" "const char *name2"
45 .Fn linkat "int fd1" "const char *name1" "int fd2" "const char *name2" "int flags"
50 atomically creates the specified directory entry (hard link)
52 with the attributes of the underlying object pointed at by
54 If the link is successful: the link count of the underlying object
59 share equal access and rights
67 is not deleted and the link count of the
72 must exist for the hard link to
78 must be in the same file system.
80 may not be a directory unless the caller is the super-user
81 and the file system containing it supports linking to directories.
83 When operating on a symlink,
85 resolves the symlink and creates a hard link on the target.
91 but it will link on the symlink itself if the flag is clear.
95 is partially implemented.
102 values different than
105 Upon successful completion, a value of 0 is returned.
106 Otherwise, a value of \-1 is returned and
108 is set to indicate the error.
111 will fail and no link will be created if:
114 A component of either path prefix denies search permission, or
115 the requested link requires writing in a directory with a mode
116 that denies write permission.
118 The directory in which the entry for the new link
119 is being placed cannot be extended because the
120 user's quota of disk blocks on the file system
121 containing the directory has been exhausted.
127 One of the pathnames specified
128 is outside the process's allocated address space.
130 An I/O error occurred while reading from or writing to
131 the file system to make the directory entry.
133 Too many symbolic links were encountered in translating one of the pathnames.
135 The link count of the file named by
139 .It Bq Er ENAMETOOLONG
140 A component of a pathname exceeded
142 characters, or an entire path name exceeded
146 A component of either path prefix does not exist, or the file named
151 The directory in which the entry for the new link is being placed
152 cannot be extended because there is no space left on the file
153 system containing the directory.
155 A component of either path prefix is not a directory.
157 The file system containing the file named by
159 does not support links.
163 is a directory and the effective
164 user ID is not super-user,
165 or the file system containing the file does not permit the use of
169 The requested link requires writing in a directory on a read-only file
174 and the file named by
176 are on different file systems.
188 is partially implemented.