01-17-2011
Hardlinks on directories are not impossible by design - the mkdir system call produces them, look at the "." and ".." entries in the newly created directory - but they are dangerous, because
this capability may produce loops in the file hierarchy or otherwise corrupt the file system. (taken from the POSIX man page for the link system call/function, see:
Man Page for link (POSIX Section 3) - The UNIX and Linux Forums). Therefore they are not allowed on most Unix implementations.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi all!
I'd like to know the differences between hard links and soft links. I've already read the ln manpage, but i'm not quite sure of what i understood.
Does a hard link sort of copy the file to a new name, give it the same inode number and same rights?
What exactly should I do to do this:... (3 Replies)
Discussion started by: penguin-friend
3 Replies
2. UNIX for Dummies Questions & Answers
Someone asked me a question today about the difference between a hard link and a soft link. That got me thinking and maybe someone can answer.
Why would I ever use a hard link if I can use a soft link instead? (2 Replies)
Discussion started by: dangral
2 Replies
3. UNIX for Dummies Questions & Answers
Hi All,
Can any one please explain me what is the difference between hard link and soft link in UNIX.
Thanks in advance
Raja Chokalingam. (2 Replies)
Discussion started by: RAJACHOKALINGAM
2 Replies
4. UNIX for Dummies Questions & Answers
hello folks
how y'all doin
well i have some questions about symbolic link and hard link
hope some one answer me
i open terminal and join as root
and i wrote ln -s blah blah
then i wrote ls
i see red file called blah blah
but didn't understand what is this can some one explain and... (2 Replies)
Discussion started by: detective linux
2 Replies
5. UNIX for Advanced & Expert Users
Hello,
In unix, the normal user can't create a hardlink for a directory. why..?
Is there any difference between creating a hard link for a file and directory?
The super user can create a hard link for directories.
Why we cannot create and super user can create.?
Please, can anyone help... (1 Reply)
Discussion started by: nagalenoj
1 Replies
6. UNIX for Dummies Questions & Answers
Hi
PLease let me know the usage of Hard Link vs Soft Link
i.e what is the basic difference and what happens when one file is changed or deleted in both the cases???
thanks (3 Replies)
Discussion started by: skyineyes
3 Replies
7. UNIX for Dummies Questions & Answers
Hi Experts,
Please help me out to find out difference between a hard link and a soft link.
I am new in unix plz help me with some example commands ( for creating such links).
Regards
S.Kamakshi :) (2 Replies)
Discussion started by: kamakshi s
2 Replies
8. Shell Programming and Scripting
Goodmorning everybody.
A question:
How can i match if a file is an hard link or not? (6 Replies)
Discussion started by: Guccio
6 Replies
9. UNIX for Advanced & Expert Users
Hello,
Please move this if I chose the wrong forum category. This question pertains to Unix and Linux I believe. I google the difference between hard and symbolic/soft links and I understand the difference. What I am trying to find is a real example of a hard link being used in a Operating... (11 Replies)
Discussion started by: jaysunn
11 Replies
10. Shell Programming and Scripting
How can I create a hard link to a file, then rename the hard link to a different name? (2 Replies)
Discussion started by: fhill2
2 Replies
LINK(2) Linux Programmer's Manual LINK(2)
NAME
link - make a new name for a file
SYNOPSIS
#include <unistd.h>
int link(const char *oldpath, const char *newpath);
DESCRIPTION
link creates a new link (also known as a hard link) to an existing file.
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.
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 old-
path 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, 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.
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.
SEE ALSO
symlink(2), unlink(2), rename(2), open(2), stat(2), ln(1)
Linux 2.0.30 1997-12-10 LINK(2)