How to Create a Symbolic Link in Linux

In the Linux file system, you will frequently encounter situations where a configuration file, a script, or a large dataset must reside in a specific, obscure system directory, but you need to access it regularly from your home folder. Copying the file wastes disk space, and if you edit the copy, the original system file remains unchanged. The solution is to create a symbolic link (often called a symlink). A symlink acts exactly like a “Shortcut” in Windows or an “Alias” in macOS; it is a tiny file that simply points the operating system to the real file located elsewhere.

Understanding Hard Links vs. Symbolic Links

Before creating a link, you must understand the two types available in Linux:

• Hard Links: These point directly to the physical data block on the hard drive. If you delete the original file, the hard link still works because the data remains on the disk until all hard links are deleted. However, hard links cannot cross different file systems (e.g., you cannot hard link a file from your SSD to an external USB drive) and cannot link to directories.
• Symbolic Links (Soft Links): These point to the file path of the original file, not the physical data. They can link to directories and cross file systems. If you delete the original file, the symlink becomes a “broken link” and points to nothing. For 99% of administrative tasks, you want a Symbolic Link.

Step-by-Step: Creating a Symbolic Link

The command to create links is ln (link). To create a symbolic link, you must add the -s (soft) flag.

1. Open your terminal application or connect via SSH.
2. The syntax is: ln -s [TARGET_FILE] [NAME_OF_LINK]. Let’s say you have a massive log file at /var/log/nginx/access.log, and you want a shortcut to it directly on your desktop.
3. Type the following command:
   ln -s /var/log/nginx/access.log ~/Desktop/nginx_logs
4. Press Enter.

You have now created a file on your Desktop named nginx_logs. If you open that file in a text editor, or use cat or grep on it, Linux will seamlessly redirect your command to the real access.log file in the /var directory. If you edit the link, you are editing the original file.

Verifying and Removing Symlinks

It is important to know how to identify a symlink so you don’t accidentally think it is the real file.

• Verifying: Run a long list command (ls -l) on the directory containing your link. For example, ls -l ~/Desktop. In the output, a symlink will have a lowercase l at the very beginning of the permission string (e.g., lrwxrwxrwx), and at the end of the line, it will show an arrow pointing to the actual target: nginx_logs -> /var/log/nginx/access.log.
• Removing: If you no longer need the shortcut, simply delete it using the standard remove command: rm ~/Desktop/nginx_logs. Crucially, deleting a symlink never deletes the original target file. (Be very careful if you are deleting a symlink to a directory; do not add a trailing slash, e.g., use rm linkname, NOT rm linkname/, or you risk deleting the contents of the target directory).

Troubleshooting Broken Links

If you try to open a symlink and receive a “No such file or directory” error, the link is broken. This happens when the original target file is moved, renamed, or deleted. The symlink is still blindly pointing to the old path. You must delete the broken link and create a new one pointing to the correct, updated location.

By utilizing symbolic links, you can organize your Linux workflow efficiently without duplicating data or breaking strict file system hierarchies.