Penguin

Differences between current version and previous revision of link(2).

Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History

Newer page: version 2 Last edited on Monday, March 10, 2003 2:11:43 pm by PerryLorier
Older page: version 1 Last edited on Tuesday, June 4, 2002 12:23:42 am by perry Revert
@@ -1,172 +1,45 @@
-LINK  
-!!!LINK  
-NAME  
-SYNOPSIS  
-DESCRIPTION  
-RETURN VALUE  
-ERRORS  
-NOTES  
-CONFORMING TO  
-BUGS  
-SEE ALSO  
-----  
 !!NAME 
+link - make a new name for a file  
  
-  
-link - make a new name for a file  
 !!SYNOPSIS 
  
+ #include <unistd.h>  
+ __int link(const char *__''oldpath''__, const char *__''newpath''__);__  
  
-__#include __  
-  
-  
-__int link(const char *__''oldpath''__, const char  
-*__''newpath''__);__  
 !!DESCRIPTION 
+link(2) creates a new link (also known as a hard link) to an existing file.  
  
+If ''newpath'' exists it will ''not'' be overwritten.  
  
-__link__ creates a new link (also known as a hard link)  
- to an existing file. 
+This new name may be used exactly as the old one for any operation; both names refer to the same file (and so have the same permissions and ownership) and it is impossible to tell which name was the `original'
  
-  
-If ''newpath'' exists it will ''not'' be  
-overwritten.  
-  
-  
-This new name may be used exactly as the old one for any  
-operation; both names refer to the same file (and so have  
-the same permissions and ownership) and it is impossible to  
-tell which name was the `original'.  
 !!RETURN VALUE 
+On success, zero is returned. On error, -1 is returned, and ''errno'' is set appropriately.  
  
-  
-On success, zero is returned. On error, -1 is returned, and  
-''errno'' is set appropriately.  
 !!ERRORS 
+;[EXDEV]: ''oldpath'' and ''newpath'' are not on the same filesystem.  
+;[EPERM]: The filesystem containing ''oldpath'' and ''newpath'' does not support the creation of hard links.  
+;[EFAULT]: ''oldpath'' or ''newpath'' points outside your accessible address space.  
+;[EACCES]: Write access to the directory containing ''newpath'' is not allowed for the process's effective uid, or one of the directories in ''oldpath'' or ''newpath'' did not allow search (execute) permission.  
+;[ENAMETOOLONG]: ''oldpath'' or ''newpath'' was too long.  
+;[ENOENT]: A directory component in ''oldpath'' or ''newpath'' does not exist or is a dangling symbolic link.  
+;[ENOTDIR]: A component used as a directory in ''oldpath'' or ''newpath'' is not, in fact, a directory.  
+;[ENOMEM]: Insufficient kernel memory was available.  
+;[EROFS]: The file is on a read-only filesystem.  
+;[EEXIST]: ''newpath'' already exists.  
+;[EMLINK]: The file referred to by ''oldpath'' already has the maximum number of links to it.  
+;[ELOOP]: Too many symbolic links were encountered in resolving ''oldpath'' or ''newpath''.  
+;[ENOSPC]: The device containing the file has no room for the new directory entry.  
+;[EPERM]: ''oldpath'' is a directory.  
+;[EIO]: An I/O error occurred.  
  
-  
-__EXDEV__  
-  
-  
-''oldpath'' and ''newpath'' are not on the same  
-filesystem.  
-  
-  
-__EPERM__  
-  
-  
-The filesystem containing ''oldpath'' and ''newpath''  
-does not support the creation of hard links.  
-  
-  
-__EFAULT__  
-  
-  
-''oldpath'' or ''newpath'' points outside your  
-accessible address space.  
-  
-  
-__EACCES__  
-  
-  
-Write access to the directory containing ''newpath'' is  
-not allowed for the process's effective uid, or one of the  
-directories in ''oldpath'' or ''newpath'' did not  
-allow search (execute) permission.  
-  
-  
-__ENAMETOOLONG__  
-  
-  
-''oldpath'' or ''newpath'' was too long.  
-  
-  
-__ENOENT__  
-  
-  
-A directory component in ''oldpath'' or ''newpath''  
-does not exist or is a dangling symbolic link.  
-  
-  
-__ENOTDIR__  
-  
-  
-A component used as a directory in ''oldpath'' or  
-''newpath'' is not, in fact, a directory.  
-  
-  
-__ENOMEM__  
-  
-  
-Insufficient kernel memory was available.  
-  
-  
-__EROFS__  
-  
-  
-The file is on a read-only filesystem.  
-  
-  
-__EEXIST__  
-  
-  
-''newpath'' already exists.  
-  
-  
-__EMLINK__  
-  
-  
-The file referred to by ''oldpath'' already has the  
-maximum number of links to it.  
-  
-  
-__ELOOP__  
-  
-  
-Too many symbolic links were encountered in resolving  
-''oldpath'' or ''newpath''.  
-  
-  
-__ENOSPC__  
-  
-  
-The device containing the file has no room for the new  
-directory entry.  
-  
-  
-__EPERM__  
-  
-  
-''oldpath'' is a directory.  
-  
-  
-__EIO__  
-  
-  
-An I/O error occurred.  
 !!NOTES 
+Hard links, as created by link(2), cannot span filesystems. Use symlink(2) if this is required.  
  
-  
-Hard links, as created by __link__, cannot span  
-filesystems. Use __symlink__ if this is  
-required.  
 !!CONFORMING TO 
-  
-  
- SVr4, SVID, POSIX, BSD 4.3, X/OPEN. SVr4 documents  
- additional ENOLINK and EMULTIHOP error conditions; POSIX.1  
- does not document ELOOP. X/OPEN does not document EFAULT,  
- ENOMEM or EIO. 
+SVr4, SVID, POSIX, BSD 4.3, X/OPEN. SVr4 documents additional [ ENOLINK] and [ EMULTIHOP] error conditions; POSIX.1 does not document [ ELOOP] . X/OPEN does not document [ EFAULT] , [ ENOMEM] or [ EIO]
 !!BUGS 
+On NFS file systems, the return code may be wrong in case the NFS server performs the link creation and dies before it can say so. Use stat(2) to find out if the link got created.  
  
-  
-On NFS file systems, the return code may be wrong in case  
-the NFS server performs the link creation and dies before it  
-can say so. Use stat(2) to find out if the link got  
-created.  
 !!SEE ALSO 
-  
-  
- symlink(2), unlink(2), rename(2),  
- open(2), stat(2), ln(1)  
-----  
+symlink(2), unlink(2), rename(2), open(2), stat(2), ln(1) 
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.