The Finder is happy to create aliases to most files and folders, provided they aren’t immediately inside a bundle or package. Then it gets all fussy. But why?
Updates replace an expiring developer ID installer certificate. All are Universal binaries, fully signed and notarized.
Which should you use, and what are their strengths and drawbacks? Symbolic links, hard links, aliases and bookmarks explained – oh, and a mention of firmlinks too.
How can you create and resolve Finder Aliases at the command line? And two further utilities you may find helpful for working with Aliases.
They’re Base-64 encoded data which is related to the Finder Alias. Here’s how to resolve them in an app, at the command line, and in code.
Use Finder aliases at the command line, compare extended attributes of two files, and normalise Unicode strings.
This page is for your support questions and comments on my free utilities Precize, Alifix and alisma, which […]
So resolving an Alias doesn’t always update data in the Alias file, even though it returns the correct path when possible. This is becoming a mess.
Links – hard links, symlinks, and Finder Aliases – are the most complex and confusing of simple concepts in computing. Do they get any better after research?
It’s all too easy to change the information in a Finder Alias when you’re inspecting it. Here’s how to avoid that, and a new version of Precize to help.