Sono abbastanza confuso dall'animatore di sentinel su create a new file with the path and filename that the file originally had
. Inoltre è brusco, perché vuoi farlo?
Bene, se capisci perché e come funziona l'alias usando UID e il percorso del file (mentre symlink funziona solo sul percorso), allora puoi capire la differenza e la risposta altamente votata più facilmente.
On HFS and HFS+ file systems, each file and folder has a unique, persistent identifier. Aliases use this identity along with pathname information to find files and folders on the same volume.
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 identity information to locate the file.
When a file or folder moves, the alias may update either its path information or unique identity 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. (result of create a new file with the path and filename that the file originally had
)
Because aliases use a file system path to resolve a files location initially, they now offer a similar behavior to symbolic links. Symbolic links rely exclusively on path information to locate a file. If you move a file somewhere on the same volume without replacing it, symbolic links to the file break while aliases do not. The only way to fix a symbolic link is to delete it and create a new one.
riferimento