Answer by spectras for Why not design having the softlink (symlink) and...
I think you are confused by the word “link” in “hardlink”/“softlink”. Despite the apparent naming symmetry, those are completely different things.Soft links:If you come from some microsoft background,...
View ArticleAnswer by kasperd for Why not design having the softlink (symlink) and...
Before I started using Unix I used AmigaOS which have links which both have some of the aspects of symlinks and of hardlinks. I never really got to understand how they behaved.Then I got to use Unix...
View ArticleAnswer by Norman Gray for Why not design having the softlink (symlink) and...
The idea you describe exists already, in the form of the 'Alias' in Apple's HFS+ filesystem. If you create an alias for a file, then you can use that alias to refer to the file in future. The alias...
View ArticleAnswer by terdon for Why not design having the softlink (symlink) and...
I don't really understand what you mean. I think you have misunderstood what hard links are. First of all, all files are hardlinks. Every single one. A file is just a link pointing to an inode. A...
View ArticleAnswer by luckyrumo for Why not design having the softlink (symlink) and...
I see the following disadvantages: with hard links there is no "original" path of the file anymore, i.e. you can't distinguish a file from its links. I often use links as shortcuts to files which are...
View ArticleWhy not design having the softlink (symlink) and hardlink in the same "link"?
I haven't used hardlinks for a long time and never really needed them until I was asked in an interview. I read their difference from symlinks here: What is the difference between a hard link and a...
View Article
