12-01-2009
hardlink - is a pointer, name, that points to a data; i.e. it`s just an alternative filename; it has same inode number as the file it was created from
copy - obviously, copy of the data; point to a different direction that file it was copyed from; has different inode number
also difference is in system calls, but that`s somewhat deep-diving into issue
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 OPENSOLARIS
clri
clri(1M) System Administration Commands clri(1M)
NAME
clri, dcopy - clear inode
SYNOPSIS
clri [-F FSType] [-V] special i-number
dcopy [-F FSType] [-V] special i-number
DESCRIPTION
clri writes zeros on the inodes with the decimal i-number on the file system stored on special. After clri, any blocks in the affected
file show up as missing in an fsck(1M) of special.
Read and write permission is required on the specified file system device. The inode becomes allocatable.
The primary purpose of this routine is to remove a file that for some reason appears in no directory. If it is used to zap an inode that
does appear in a directory, care should be taken to track down the entry and remove it. Otherwise, when the inode is reallocated to some
new file, the old entry will still point to that file. At that point, removing the old entry will destroy the new file. The new entry will
again point to an unallocated inode, so the whole cycle is likely to be repeated again and again.
dcopy is a symbolic link to clri.
OPTIONS
-F FSType Specify the FSType on which to operate. The FSType should either be specified here or be determinable from /etc/vfstab by
matching special with an entry in the table, or by consulting /etc/default/fs.
-V Echo the complete command line, but do not execute the command. The command line is generated by using the options and argu-
ments provided by the user and adding to them information derived from /etc/vfstab. This option should be used to verify and
validate the command line.
USAGE
See largefile(5) for the description of the behavior of clri and dcopy when encountering files greater than or equal to 2 Gbyte ( 2^31
bytes).
FILES
/etc/default/fs Default local file system type
/etc/vfstab List of default parameters for each file system
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
fsck(1M), vfstab(4), attributes(5), largefile(5)
NOTES
This command might not be supported for all FSTypes.
SunOS 5.11 16 Sep 1996 clri(1M)