cmd/ln - Revision history

Woozle at 13:32, 14 December 2025

2025-12-14T13:32:57Z

← Older revision		Revision as of 13:32, 14 December 2025
Line 1:		Line 1:
	[[category:Linux]]		[[category:Linux]]
	'''<code>ln</code>''' is the Linux command for creating a link to a file or folder.		{{fmt/title\|command: <code>ln</code>}}
			==About==
			'''<code>ln</code>''' is the [[Linux]] command for creating a link to a file or folder.

	This page so far only discusses ''symbolic'' links, not ''hard'' links. (TODO)		This page so far only discusses ''symbolic'' links, not ''hard'' links. ({{hashtag\|TODO}})
	==General Syntax==		==General Syntax==
	ln {{fmt/opt\|-r}} --symbolic {{arg\|filespec of existing file/folder}} {{arg\|filespec for new link}}		ln {{fmt/opt\|-r}} --symbolic {{arg\|filespec of existing file/folder}} {{arg\|filespec for new link}}

Woozle: clarification & tidying

2024-12-11T22:19:52Z

clarification & tidying

← Older revision		Revision as of 22:19, 11 December 2024
Line 2:		Line 2:
	'''<code>ln</code>''' is the Linux command for creating a link to a file or folder.		'''<code>ln</code>''' is the Linux command for creating a link to a file or folder.

	~~To create a relative~~ link:		This page so far only discusses ''symbolic'' links, not ''hard'' links. (TODO)
	ln -r --symbolic {{arg\|existing file}} {{arg\|link ~~to create~~}}		==General Syntax==
	* ~~Relative links will still work even if~~ the folder ~~containing both files (~~the ~~original and the link)~~ is ~~moved or copied~~.		ln {{fmt/opt\|-r}} --symbolic {{arg\|filespec of existing file/folder}} {{arg\|filespec for new link}}
	* ~~Note that a~~ link cannot have the same name as a folder in the same directory.		===scenarios===
			* If you're in the folder '''where you want the link to be created''':
			ln {{fmt/opt\|-r}} --symbolic {{arg\|path to existing file/folder}} ./{{arg\|name for new link}}
			* If you're in the folder '''where the existing/real file is''':
			ln {{fmt/opt\|-r}} --symbolic ./{{arg\|name of existing file}} {{arg\|path to new link}}
			===notes===
			* A link cannot have the same name as a folder in the same directory (same rule as if it were a regular file).
			* The <code>-r</code> option just tells <code>ln</code> to ''calculate'' the relative path from the link to the existing file, and ''use that'' as the link URL; see "Relative Links" below.
			==Errors==
	* The error message "ln: failed to create symbolic link '{{arg\|filename}}': File exists" can be maddeningly misleading. It seems to always report the existing file, even when the problem is actually that the ''second'' filename (the link-name) already exists. Translation:		* The error message "ln: failed to create symbolic link '{{arg\|filename}}': File exists" can be maddeningly misleading. It seems to always report the existing file, even when the problem is actually that the ''second'' filename (the link-name) already exists. Translation:
	** "<tt>'{{arg\|arg 1}}': File exists</tt>" (arg 1 should be {{arg\|existing file}}): The link-name is the same as an existing file, possibly a folder.		** "<tt>'{{arg\|arg 1}}': File exists</tt>" (arg 1 should be {{arg\|existing file}}): The link-name is the same as an existing file, possibly a folder.
	*** The fact that <code>ln</code> reports the first param instead of the second one seems to be a {{l/sub\|bug}}. Yes, the first param is a file that does exist, but that's not the problem.		*** The fact that <code>ln</code> reports the first param instead of the second one seems to be a {{l/sub\|bug}}. Yes, the first param is a file that does exist, but that's not the problem.
	** "<tt>'{{arg\|arg 2}}': File exists</tt>" (arg 2 should be {{arg\|name for link}}): You've got the arguments backwards, and are trying to create a link under the same name as the existing file (to a file which doesn't exist).		** "<tt>'{{arg\|arg 2}}': File exists</tt>" (arg 2 should be {{arg\|name for link}}): You've got the arguments backwards, and are trying to create a link under the same name as the existing file (to a file which doesn't exist).
	==~~=another way to think of it=~~==		==Relative Links==
	~~If you're in~~ the ~~folder '''where~~ you ~~want~~ the link ~~to go~~'~~'':~~		Note that when <code>ln</code> creates a relative link using the <code>-r</code> option, all it is doing is calculating the relative path for you and then using that as the link's target-string (URL). You can create a relative link without <code>-r</code> by just specifying a relative path. There's no difference between an absolute link and a relative link except whether the URL uses any relative-path syntax (e.g. "../", or no initial "/").
	ln -r -~~-symbolic {{arg\|relative~~ path}}/~~{{arg\|name of file~~/~~folder}}~~ .~~/{{arg\|name for link}}~~

	~~If you're in~~ the folder ~~'''where~~ the ~~existing/real file is''':~~		Relative links will still work even if the folder containing both files (the original and the link) is moved or copied, which can be useful for making links within a portable code repository. ([[Git]] does store link-files by default.)
	~~ln -r --symbolic ./{{arg\|name of file}} {{arg\|relative path}}/{{arg\|name for link}}~~
	~~==Example==~~
	~~I pretty much always get confused as to which is~~ the link ~~and which~~ is ~~the target~~, ~~so here's an example~~. ~~You're inside {{fmt/code\|/git/futilities/human/ff}} and you want to create a~~ link ~~called "lib" to the "lib" folder at {{fmt/code\|/git/futilities/lib}}:~~
	~~ln -r -~~-~~symbolic ../../lib/~~ .~~/lib~~
	==Notes==		==Notes==
	* [http://stackoverflow.com/questions/1347105/linux-link-all-files-from-one-to-another-directory LINUX: Link all files from one to another directory]		* [http://stackoverflow.com/questions/1347105/linux-link-all-files-from-one-to-another-directory LINUX: Link all files from one to another directory]

Woozle at 23:36, 22 June 2024

2024-06-22T23:36:25Z

← Older revision		Revision as of 23:36, 22 June 2024
Line 3:		Line 3:

	To create a relative link:		To create a relative link:
	ln -r --symbolic ./{{arg\|existing file}} {{arg\|link to create}}		ln -r --symbolic {{arg\|existing file}} {{arg\|link to create}}
	* Relative links will still work even if the folder containing both files (the original and the link) is moved or copied.		* Relative links will still work even if the folder containing both files (the original and the link) is moved or copied.
	* Note that a link cannot have the same name as a folder in the same directory.		* Note that a link cannot have the same name as a folder in the same directory.
Line 19:		Line 19:
	I pretty much always get confused as to which is the link and which is the target, so here's an example. You're inside {{fmt/code\|/git/futilities/human/ff}} and you want to create a link called "lib" to the "lib" folder at {{fmt/code\|/git/futilities/lib}}:		I pretty much always get confused as to which is the link and which is the target, so here's an example. You're inside {{fmt/code\|/git/futilities/human/ff}} and you want to create a link called "lib" to the "lib" folder at {{fmt/code\|/git/futilities/lib}}:
	ln -r --symbolic ../../lib/ ./lib		ln -r --symbolic ../../lib/ ./lib

	~~..or, in other words:~~

	~~ln -r --symbolic {{arg\|existing file}} {{arg\|alias/link to create}}~~

	==Notes==		==Notes==
	* [http://stackoverflow.com/questions/1347105/linux-link-all-files-from-one-to-another-directory LINUX: Link all files from one to another directory]		* [http://stackoverflow.com/questions/1347105/linux-link-all-files-from-one-to-another-directory LINUX: Link all files from one to another directory]

Woozle: clarifications

2024-06-22T23:12:02Z

clarifications

← Older revision		Revision as of 23:12, 22 June 2024
Line 3:		Line 3:

	To create a relative link:		To create a relative link:
	ln -r --symbolic ./{{arg\|~~real~~ file}} {{arg\|~~name for~~ link}}		ln -r --symbolic ./{{arg\|existing file}} {{arg\|link to create}}
	* Relative links will still work even if the folder containing both files (the original and the link) is moved or copied.		* Relative links will still work even if the folder containing both files (the original and the link) is moved or copied.
	* Note that a link cannot have the same name as a folder in the same directory.		* Note that a link cannot have the same name as a folder in the same directory.
Line 22:		Line 22:
	..or, in other words:		..or, in other words:

	ln -r --symbolic {{arg\|existing file}} {{arg\|alias to create}}		ln -r --symbolic {{arg\|existing file}} {{arg\|alias/link to create}}

	==Notes==		==Notes==
	* [http://stackoverflow.com/questions/1347105/linux-link-all-files-from-one-to-another-directory LINUX: Link all files from one to another directory]		* [http://stackoverflow.com/questions/1347105/linux-link-all-files-from-one-to-another-directory LINUX: Link all files from one to another directory]

Woozle: /* Example */

2024-06-22T23:09:38Z

Example

← Older revision		Revision as of 23:09, 22 June 2024
Line 22:		Line 22:
	..or, in other words:		..or, in other words:

	ln -r --symbolic {{arg\|~~actual~~ file}} {{arg\|alias}}		ln -r --symbolic {{arg\|existing file}} {{arg\|alias to create}}

	==Notes==		==Notes==
	* [http://stackoverflow.com/questions/1347105/linux-link-all-files-from-one-to-another-directory LINUX: Link all files from one to another directory]		* [http://stackoverflow.com/questions/1347105/linux-link-all-files-from-one-to-another-directory LINUX: Link all files from one to another directory]

Woozle at 17:56, 13 April 2024

2024-04-13T17:56:17Z

← Older revision		Revision as of 17:56, 13 April 2024
Line 10:		Line 10:
	*** The fact that <code>ln</code> reports the first param instead of the second one seems to be a {{l/sub\|bug}}. Yes, the first param is a file that does exist, but that's not the problem.		*** The fact that <code>ln</code> reports the first param instead of the second one seems to be a {{l/sub\|bug}}. Yes, the first param is a file that does exist, but that's not the problem.
	** "<tt>'{{arg\|arg 2}}': File exists</tt>" (arg 2 should be {{arg\|name for link}}): You've got the arguments backwards, and are trying to create a link under the same name as the existing file (to a file which doesn't exist).		** "<tt>'{{arg\|arg 2}}': File exists</tt>" (arg 2 should be {{arg\|name for link}}): You've got the arguments backwards, and are trying to create a link under the same name as the existing file (to a file which doesn't exist).
			===another way to think of it===
			If you're in the folder '''where you want the link to go''':
			ln -r --symbolic {{arg\|relative path}}/{{arg\|name of file/folder}} ./{{arg\|name for link}}

			If you're in the folder '''where the existing/real file is''':
			ln -r --symbolic ./{{arg\|name of file}} {{arg\|relative path}}/{{arg\|name for link}}
	==Example==		==Example==
	I pretty much always get confused as to which is the link and which is the target, so here's an example. You're inside {{fmt/code\|/git/futilities/human/ff}} and you want to create a link called "lib" to the "lib" folder at {{fmt/code\|/git/futilities/lib}}:		I pretty much always get confused as to which is the link and which is the target, so here's an example. You're inside {{fmt/code\|/git/futilities/human/ff}} and you want to create a link called "lib" to the "lib" folder at {{fmt/code\|/git/futilities/lib}}:

Woozle at 16:48, 13 April 2024

2024-04-13T16:48:07Z

← Older revision		Revision as of 16:48, 13 April 2024
Line 3:		Line 3:

	To create a relative link:		To create a relative link:
	ln -r --symbolic ./{{arg\|~~existing~~ file}} {{arg\|name for link}}		ln -r --symbolic ./{{arg\|real file}} {{arg\|name for link}}
	* Relative links will still work even if the folder containing both files (the original and the link) is moved or copied.		* Relative links will still work even if the folder containing both files (the original and the link) is moved or copied.
	* Note that a link cannot have the same name as a folder in the same directory.		* Note that a link cannot have the same name as a folder in the same directory.

Woozle at 13:51, 21 September 2023

2023-09-21T13:51:01Z

← Older revision		Revision as of 13:51, 21 September 2023
Line 7:		Line 7:
	* Note that a link cannot have the same name as a folder in the same directory.		* Note that a link cannot have the same name as a folder in the same directory.
	* The error message "ln: failed to create symbolic link '{{arg\|filename}}': File exists" can be maddeningly misleading. It seems to always report the existing file, even when the problem is actually that the ''second'' filename (the link-name) already exists. Translation:		* The error message "ln: failed to create symbolic link '{{arg\|filename}}': File exists" can be maddeningly misleading. It seems to always report the existing file, even when the problem is actually that the ''second'' filename (the link-name) already exists. Translation:
	** "<tt>'{{arg\|~~existing file~~}}': File exists</tt>": The link-name is the same as an existing file, possibly a folder.		** "<tt>'{{arg\|arg 1}}': File exists</tt>" (arg 1 should be {{arg\|existing file}}): The link-name is the same as an existing file, possibly a folder.
	*** The fact that <code>ln</code> reports the first param instead of the second one seems to be a bug. Yes, the first param is a file that does exist, but that's not the problem.		*** The fact that <code>ln</code> reports the first param instead of the second one seems to be a {{l/sub\|bug}}. Yes, the first param is a file that does exist, but that's not the problem.
	** "<tt>'{{arg\|~~name for link~~}}': File exists</tt>": You've got the arguments backwards, and are trying to create a link under the same name as the existing file (to a file which doesn't exist).		** "<tt>'{{arg\|arg 2}}': File exists</tt>" (arg 2 should be {{arg\|name for link}}): You've got the arguments backwards, and are trying to create a link under the same name as the existing file (to a file which doesn't exist).
	==Example==		==Example==
	I pretty much always get confused as to which is the link and which is the target, so here's an example. You're inside {{fmt/code\|/git/futilities/human/ff}} and you want to create a link called "lib" to the "lib" folder at {{fmt/code\|/git/futilities/lib}}:		I pretty much always get confused as to which is the link and which is the target, so here's an example. You're inside {{fmt/code\|/git/futilities/human/ff}} and you want to create a link called "lib" to the "lib" folder at {{fmt/code\|/git/futilities/lib}}:

Woozle at 12:59, 21 September 2023

2023-09-21T12:59:58Z

← Older revision		Revision as of 12:59, 21 September 2023
Line 6:		Line 6:
	* Relative links will still work even if the folder containing both files (the original and the link) is moved or copied.		* Relative links will still work even if the folder containing both files (the original and the link) is moved or copied.
	* Note that a link cannot have the same name as a folder in the same directory.		* Note that a link cannot have the same name as a folder in the same directory.
			* The error message "ln: failed to create symbolic link '{{arg\|filename}}': File exists" can be maddeningly misleading. It seems to always report the existing file, even when the problem is actually that the ''second'' filename (the link-name) already exists. Translation:
			** "<tt>'{{arg\|existing file}}': File exists</tt>": The link-name is the same as an existing file, possibly a folder.
			*** The fact that <code>ln</code> reports the first param instead of the second one seems to be a bug. Yes, the first param is a file that does exist, but that's not the problem.
			** "<tt>'{{arg\|name for link}}': File exists</tt>": You've got the arguments backwards, and are trying to create a link under the same name as the existing file (to a file which doesn't exist).
	==Example==		==Example==
	I pretty much always get confused as to which is the link and which is the target, so here's an example. You're inside {{fmt/code\|/git/futilities/human/ff}} and you want to create a link called "lib" to the "lib" folder at {{fmt/code\|/git/futilities/lib}}:		I pretty much always get confused as to which is the link and which is the target, so here's an example. You're inside {{fmt/code\|/git/futilities/human/ff}} and you want to create a link called "lib" to the "lib" folder at {{fmt/code\|/git/futilities/lib}}:

Woozle at 13:09, 14 September 2023

2023-09-14T13:09:55Z

← Older revision		Revision as of 13:09, 14 September 2023
Line 4:		Line 4:
	To create a relative link:		To create a relative link:
	ln -r --symbolic ./{{arg\|existing file}} {{arg\|name for link}}		ln -r --symbolic ./{{arg\|existing file}} {{arg\|name for link}}
	Relative links will still work even if the folder containing both files (the original and the link) is moved or copied.		* Relative links will still work even if the folder containing both files (the original and the link) is moved or copied.
			* Note that a link cannot have the same name as a folder in the same directory.
	==Example==		==Example==
	I pretty much always get confused as to which is the link and which is the target, so here's an example. You're inside {{fmt/code\|/git/futilities/human/ff}} and you want to create a link called "lib" to the "lib" folder at {{fmt/code\|/git/futilities/lib}}:		I pretty much always get confused as to which is the link and which is the target, so here's an example. You're inside {{fmt/code\|/git/futilities/human/ff}} and you want to create a link called "lib" to the "lib" folder at {{fmt/code\|/git/futilities/lib}}: