12-07-2009
Quote:
Originally Posted by
rogerben
2) But in space point of view both hard link and copying a file occupies a same space.
This is incorrect, hard-linking occupies almost no more space (just metadata) while copying (unless you are using ZFS deduplication which is quite unlikely at that time) will double the space usage.
Last edited by jlliagre; 12-07-2009 at 01:46 PM..
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. Solaris
Hi,
Can anyone explain me the usage of mcopy command and also the difference between copy and mcopy. As per my understanding through both we can copy multiple files or DOS files . Any help on this will be really helpful. (3 Replies)
Discussion started by: rogerben
3 Replies
LEARN ABOUT NETBSD
linkat
LINK(2) BSD System Calls Manual LINK(2)
NAME
link -- make a hard file link
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <unistd.h>
int
link(const char *name1, const char *name2);
int
linkat(int fd1, const char *name1, int fd2, const char *name2, int flags);
DESCRIPTION
The link() function call atomically creates the specified directory entry (hard link) name2 with the attributes of the underlying object
pointed at by name1. If the link is successful: the link count of the underlying object is incremented; name1 and name2 share equal access
and rights to the underlying object.
If name1 is removed, the file name2 is not deleted and the link count of the underlying object is decremented.
name1 must exist for the hard link to succeed and both name1 and name2 must be in the same file system. name1 may not be a directory unless
the caller is the super-user and the file system containing it supports linking to directories.
When operating on a symlink, link() resolves the symlink and creates a hard link on the target. linkat() will do the same if
AT_SYMLINK_FOLLOW is set in flags, but it will link on the symlink itself if the flag is clear.
At the moment, linkat() is partially implemented. It will return ENOSYS for fd1 and fd2 values different than AT_FDCWD.
RETURN VALUES
Upon successful completion, a value of 0 is returned. Otherwise, a value of -1 is returned and errno is set to indicate the error.
ERRORS
link() will fail and no link will be created if:
[EACCES] A component of either path prefix denies search permission, or the requested link requires writing in a directory with a
mode that denies write permission.
[EDQUOT] The directory in which the entry for the new link is being placed cannot be extended because the user's quota of disk
blocks on the file system containing the directory has been exhausted.
[EEXIST] The link named by name2 does exist.
[EFAULT] One of the pathnames specified is outside the process's allocated address space.
[EIO] An I/O error occurred while reading from or writing to the file system to make the directory entry.
[ELOOP] Too many symbolic links were encountered in translating one of the pathnames.
[EMLINK] The link count of the file named by name1 would exceed {LINK_MAX}.
[ENAMETOOLONG] A component of a pathname exceeded {NAME_MAX} characters, or an entire path name exceeded {PATH_MAX} characters.
[ENOENT] A component of either path prefix does not exist, or the file named by name1 does not exist.
[ENOSPC] The directory in which the entry for the new link is being placed cannot be extended because there is no space left on the
file system containing the directory.
[ENOTDIR] A component of either path prefix is not a directory.
[EOPNOTSUPP] The file system containing the file named by name1 does not support links.
[EPERM] The file named by name1 is a directory and the effective user ID is not super-user, or the file system containing the file
does not permit the use of link() on a directory.
[EROFS] The requested link requires writing in a directory on a read-only file system.
[EXDEV] The link named by name2 and the file named by name1 are on different file systems.
SEE ALSO
symlink(2), unlink(2)
STANDARDS
The link() function conforms to ISO/IEC 9945-1:1990 (``POSIX.1'').
BUGS
linkat() is partially implemented.
BSD
January 12, 1994 BSD