Aliases and links
Aliases and links both allow you to create other names for the same file and even
have those names in other directories. You can have "/Users/you/fred" and "/Users/you/desktop/stuff" be the same thing: edit either one and you'll see the changes in the other.
There are actually three forms of linking in Mac OS X: aliases, hard links, and
symbolic links. These are all really file system features, but HFS+ supports
all three, and for the example given above, all three are identical.
But there are differences. Hard links come over from the Unix world, and
are simply directory entries pointing to the same inode. The inode is the
traditional Unix metadata that has information about permissions, ownership
and disk blocks used; if two directory entries point to the same inode, they
are pointing to the same file. Technically HFS+
file systems don't have inode tables. However,just
about everything works as though they did. See
Usenix2000 invitedtalks sanchez_html/)
and Apple.com technotes
A hard link can't refer to a directory (because it would just be too easy to
completely screw up the file system) and it can't refer to a file on another file system
(because inode numbers are only unique to an individual file system).
A symbolic link is again from Unix, but is really just a text file that contains the path
to another file. Its metadata is marked so that that path is interpreted rather than
being seen as text. A symbolic link can refer to a directory, a file on
a different file system, or even another symbolic link.
Aliases are a Mac invention, and are similar in concept to symbolic links, but
don't depend upon the original path name to find the "real" file. It uses
a "unique identity" instead. If you renamed
or moved a file referenced by a symbolic link, the link would be broken and would not
work, but an alias still would.
If you stay away from the command line, your Mac will always do the "right thing"
with regard to aliases, but you can get confused if you mess with
aliases in Terminal. You cannot "see" the original file with ordinary terminal
commands; if "fred" is an alias for "tom", "cat fred" will come up empty.
You can "vi fred", but whatever you put in there won't change "tom" in any way.
Interestingly, an alias does store path name information, apparently
as redundancy: if the file can't be found from the unique identity, OS X (the file system
driver, really) will try to find it by path name. There seems to be confusion in
some documentation; Apple documentation says:
In versions of Mac OS X before 10.2, aliases located a file or folder
using its unique identity first and its pathname second. Beginning with
Mac OS X 10.2, aliases reversed this search order by using the pathname
first and unique identity second. This means that if you move a file
and replace it with an identically named file, aliases to the original
file now point to the new file. Similarly, if you move a file on the
same volume (without replacing it), aliases use the unique identify
information to locate the file.
When a file or folder moves, the alias may update either its path
information or unique identify information to account for the change. If
a file moves somewhere on the same volume, the alias updates its internal
record with the new path information for the file. Similarly, if the
original file is replaced by a file with the same name, but a different
unique identity, the alias updates its internal record with the unique
identity of the new file.
Note that the difficulties that come from moving with aliases are
only confusing when moving the original to a different file system.
If this page was useful to you, please help others find it:
More Articles by Tony Lawrence
- Find me on Google+
This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.
Jump to Comments
Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.
Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.
We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.