a symbolic link

A symbolic link is like a sticky note that just says "the file you want is over there at this address," with the address written out. The note itself holds no real content, it only points. If the thing at that address gets moved or deleted, the note still hangs there, now pointing at nothing. A symbolic link (or soft link) is exactly that: a tiny special file whose entire content is a path name to another file.

Mechanically it is quite different from a hard link. A symbolic link is its own little file, with its own inode, and the data it stores is simply a text path, for example /home/alice/report.txt. When the OS is resolving a path and runs into a symlink, it reads the stored path and continues resolving from there, in effect substituting the target's path for the link. Because it points by path rather than by the file's true identity, a symlink can do things a hard link cannot: it can point across different file systems, and it can point at directories. But it can also dangle, if you delete or rename the target, the link still exists and still holds the old path, and following it now fails because nothing is there.

Why it matters: symbolic links are wonderfully flexible for shortcuts, for redirecting a well-known path to wherever the real file currently lives, and for linking across devices, things hard links cannot do. The honest trade-off is reliability: a symlink is only a path, so it has no knowledge of, and no hold over, its target. Deleting the target does not warn the link and does not free anything special; you are simply left with a dangling link. The crisp distinction to remember: a hard link is another real name for the data and keeps it alive; a symbolic link is just a pointer to a name and can break.