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
RMDIR(2) Linux Programmer's Manual RMDIR(2)
NAME
rmdir - delete a directory
SYNOPSIS
#include <unistd.h>
int rmdir(const char *pathname);
DESCRIPTION
rmdir() deletes a directory, which must be empty.
RETURN VALUE
On success, zero is returned. On error, -1 is returned, and errno is set appropriately.
ERRORS
EACCES Write access to the directory containing pathname was not allowed, or one of the directories in the path prefix of pathname did not
allow search permission. (See also path_resolution(7).
EBUSY pathname is currently in use by the system or some process that prevents its removal. On Linux this means pathname is currently
used as a mount point or is the root directory of the calling process.
EFAULT pathname points outside your accessible address space.
EINVAL pathname has . as last component.
ELOOP Too many symbolic links were encountered in resolving pathname.
ENAMETOOLONG
pathname was too long.
ENOENT A directory component in pathname does not exist or is a dangling symbolic link.
ENOMEM Insufficient kernel memory was available.
ENOTDIR
pathname, or a component used as a directory in pathname, is not, in fact, a directory.
ENOTEMPTY
pathname contains entries other than . and .. ; or, pathname has .. as its final component. POSIX.1-2001 also allows EEXIST for
this condition.
EPERM The directory containing pathname has the sticky bit (S_ISVTX) set and the process's effective user ID is neither the user ID of the
file to be deleted nor that of the directory containing it, and the process is not privileged (Linux: does not have the CAP_FOWNER
capability).
EPERM The file system containing pathname does not support the removal of directories.
EROFS pathname refers to a directory on a read-only file system.
CONFORMING TO
SVr4, 4.3BSD, POSIX.1-2001.
BUGS
Infelicities in the protocol underlying NFS can cause the unexpected disappearance of directories which are still being used.
SEE ALSO
rm(1), rmdir(1), chdir(2), chmod(2), mkdir(2), rename(2), unlink(2), unlinkat(2)
COLOPHON
This page is part of release 3.27 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 2008-05-08 RMDIR(2)