(1) whats use with soft link over hard link?
while we create a soft/symbolic link "ln -s" ,here creating a new file with it's own new inode that just points to the name of the file we want.
In case of hard link, we are actually creating another file instance of the original file, both will have the same inode number (ls -i).
Here we can't use a hard link which crosses file system boundaries/partitions. The reason for this goes back to the fact that inodes are allocated for each file system, and are not managed by any central process. Thus,we may have a file in one partition with the inode 12345 and a completely different file in another partitions with inode 12345 .... so, hard links across partitions would really leads to wrong results.
anything else!!!!!
Creating Hard link:
ex:> ln file Hfile
here file is the actual file and Hfile is the hard link.
Creating Soft link:
ex:> ln -s file Sfile
here file is the actual file and Sfile is a file which has a target to actual file.
while we create a soft/symbolic link "ln -s" ,here creating a new file with it's own new inode that just points to the name of the file we want.
In case of hard link, we are actually creating another file instance of the original file, both will have the same inode number (ls -i).
Here we can't use a hard link which crosses file system boundaries/partitions. The reason for this goes back to the fact that inodes are allocated for each file system, and are not managed by any central process. Thus,we may have a file in one partition with the inode 12345 and a completely different file in another partitions with inode 12345 .... so, hard links across partitions would really leads to wrong results.
anything else!!!!!
Creating Hard link:
ex:> ln file Hfile
here file is the actual file and Hfile is the hard link.
Creating Soft link:
ex:> ln -s file Sfile
here file is the actual file and Sfile is a file which has a target to actual file.
No comments :
Post a Comment