You can make a difference in the Apple Support Community!
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
Working with OSX Mojave and have done endless searches for information about creating hard links. Everything I can find goes back years, and nothing has worked so far. Has the ability to create hard links (via Terminal) been done away with or is it still viable? Any help would be appreciated. Thank you.
iMac 21.5″ 4K, macOS 10.14
ln '/path/to/existing/file' '/path/to/new/hardlink/filename'
That is lowercase L and lowercase N. Original Bell Labs UNIX developers liked short command names, so we get ls, ln, ed, rm, cp, etc...
If there is white space in the file path, then you will need to quote the path so the white space is protected.
PS. I did not mean to reply to VikingOSX, but I fumble fingered my reply.
Any Unix/Linux based information on creating a hardlink will apply to macOS
Also there are symbolic links as well (the ln -s ...)
macOS also has GUI level Aliases, and Catalina introduces a thing called "Synthetic Firmlinks"
Hardlinks, symbolic links, Aliases and Synthetic Firmlinks are all similar and totally different.
Hardlinks are directory entries that point to a file's metadata using file system internal file identifiers (often called an inode). Think of a directory entry as an address book entry pointing to a family member. The address book entry is not your family member, and if other family members have address book entries to the same person, you do not get extra family members. And if someone throws away their address book, your family member is not affected.
A Hardlink is a file system abstraction and can be used by any program, app, process on macOS.
A hard link does not care if you rename the any of the directory entries that point to the same file. That does not affect the file system internal file identifier. In fact the file itself does not know its name. The file itself only knows its file identifier. Names only exist in directories. The file itself does maintain a reference count for the total number of hardlinks that point at it. when a hardlink is deleted, the reference count is decremented. When the reference count goes to zero, the file is deleted (good thing address books do not have reference counts 😀
A symbolic link is a file that contains a file system path to the real file. Like writing down directions to the Taco Stand. If the Taco Stand moves, the symbolic link will not know it moved, and will not find it. In fact, if the Taco Stand changes it name, but is in the same place, the symbolic link will not find it. Symbolic links can contain absolute path information, or they can have relative path information, as in go up 2 directories, then down this subdirectory tree to this file kind of relative paths.
A symbolic link is also a file system abstraction and can be used by any program, app, process on macOS.
A macOS Alias is used by macOS GUI applications that use the file manager GUI framework. An Alias contains the internal file indentifier, but it does not increment the hardlink ref count. An Alias also contains a path to the file. So if the file is moved, the internal file system identifier can still find it. If the file is deleted, and a new file with the same name is put back in its place, the Alias path can find it (this is a common GUI app trick; save the file as a temp file, delete the original, rename the temp file to the original name; this changes the internal file system identifier). An Alias also knows if the file came from a network volume, and will attempt to reconnect to the network attached volume if you access the file via the Alias. An Alias may also have its own Icon (which can make an Alias a very large file).
Because an Alias is a GUI file manager framework abstraction, it is ONLY available to GUI applications, or programs that intentionally like against the file manager framework and use its file system access routines.
Synthetic Firmlinks are new in Catalina, and macOS uses them to glue together the Read-Only "Macintosh HD" volume and the Read/Write "Macintosh HD - data" volume. On a Catalina system "man synthetic.conf". You can also read about firmlinks at
NOTE: Hardlinks have existed on Unix based file systems since the early Bell Labs UNIX back in the '70's. Symbolic links came our of the UC Berkley (BSD) UNIX implementation. macOS Aliases have been around for awhile, at least since the '90, maybe even the late 80's. macOS Firmlinks are new in Catalina 10.15.
You’ll probably not want to try to use file system links with a remote file share, Dropbox or otherwise. Thar’s probably not a place where you’ll want to start your adventure.
The -Ffhinsv stuff is a list of the switches (controls, options, etc) available within the ln tool.
The command man ln will show the details of the ln command.
Other examples:
man man
man ln
man grep
apropos ln
apropos find
Some docs:
https://www.tldp.org/LDP/Bash-Beginners-Guide/html/
Apple’s version of bash is very old, and Apple has switched the default command shell from bash to zsh with Catalina.
https://scriptingosx.com/2019/06/moving-to-zsh/
So... many... Digits... Here... 🤪 Oh, and 1984? That probably makes you the n00b. 😉
You might also give this method try:
1 - Launch Terminal
2 - enter cd desktop
3 - hit Return
4 - enter ln -s (a space after n and s)
5 - drag the item into the Terminal after the n
6 - hit Return
AÂ symlink will be created on the Desktop to the item.
Thank you to VikingOSX and BobHarris. Looks pretty similar to the Windows cmd: mklink /h "Link" "Target" which I was able to use on my Windows laptop.
Bob, when I did the Terminal help for ln this is what I got back:
Marges-iMac:~ margehomer$ man
What manual page do you want?
Marges-iMac:~ margehomer$ ln
usage: ln [-Ffhinsv] source_file [target_file]
ln [-Ffhinsv] source_file ... target_dir
link source_file target_file
So your explanation helped as I don't have any idea what the "[-Ffhinsv]" is about, although it seems it's not even needed in the Terminal input.
Possibly, I'm having issues because I'm trying to link to a couple of files that are in my Dropbox and I keep getting the response from Terminal that the Dir/File does not exist. Yet, if I copy that same file to my Documents folder and try linking that, it works!
Spending time (retired, sheltering in place and bored to death) playing with both my iMac and Windows laptop. Keeps the brain cells from dying off. Been at this for a while, purchased my first Macintosh (remember those?) way back in 1984!
Thanks guys, gives me that push in the right direction that I needed. As for the 1984 Macintosh, if I kept the signed receipt from the guy I purchased it from, it might just be worth a few bucks today!
Again, many thanks.
Wow guys, thanks for all the information. I've actually done a copy/paste of all the responses to a document that I'll print out and be able to review.
Bob, your last response has a ton of information for me to digest. many thanks!
BobHarris wrote:
...macOS Firmlinks are new in Catalina 10.15.
FWIW... A fix for a nasty firmlink bug is first available in macOS 10.15.5:
https://www.shirtpocket.com/blog/index.php/shadedgrey/never_look_a_gift_fix_in_the_mouth/
In the Terminal, read the ln(1) man page. It expressly states that by default, it creates hard links.
man ln
Subconscious DECision. 😎
Creating Hard Links