tldr/pages/common/ln.md

# ln

> Creates links to files and folders.

- Create a symbolic link to a file (or folder):

`ln -s {{path/to/file}} {{path/to/symlink}}`

- Overwrite an existing symbolic to point to a different file:

`ln -sf {{path/to/new/file}} {{path/to/file/symlink}}`

- Create a hard link to a file:

`ln {{path/to/file}} {{path/to/hardlink}}`
Adds some examples for ln Hopefully this will help people remember if the source is the first or second argument 2014-02-17 16:59:07 +00:00			`# ln`

Formatted all pages according to guidelines. 2016-01-07 17:31:27 +00:00			`> Creates links to files and folders.`
Adds some examples for ln Hopefully this will help people remember if the source is the first or second argument 2014-02-17 16:59:07 +00:00
reword to prevent ambiguity "original" can be associated with the origin of the link and lead to confusion if not read carefully. Also, the third example seems to have been copied from the prior example but not fully adapted: "original/file" should have said (if I'm reading this correctly) "original/folder". 2015-08-10 19:03:34 +01:00			`- Create a symbolic link to a file (or folder):`
Adds some examples for ln Hopefully this will help people remember if the source is the first or second argument 2014-02-17 16:59:07 +00:00
reword to prevent ambiguity "original" can be associated with the origin of the link and lead to confusion if not read carefully. Also, the third example seems to have been copied from the prior example but not fully adapted: "original/file" should have said (if I'm reading this correctly) "original/folder". 2015-08-10 19:03:34 +01:00			`ln -s {{path/to/file}} {{path/to/symlink}}`
Adds some examples for ln Hopefully this will help people remember if the source is the first or second argument 2014-02-17 16:59:07 +00:00
reword to prevent ambiguity "original" can be associated with the origin of the link and lead to confusion if not read carefully. Also, the third example seems to have been copied from the prior example but not fully adapted: "original/file" should have said (if I'm reading this correctly) "original/folder". 2015-08-10 19:03:34 +01:00			`- Overwrite an existing symbolic to point to a different file:`
add a separate example for overwriting a symlink to make it clear what the -T option does, as discussed in #180 2015-03-15 11:40:20 +00:00
reword to prevent ambiguity "original" can be associated with the origin of the link and lead to confusion if not read carefully. Also, the third example seems to have been copied from the prior example but not fully adapted: "original/file" should have said (if I'm reading this correctly) "original/folder". 2015-08-10 19:03:34 +01:00			`ln -sf {{path/to/new/file}} {{path/to/file/symlink}}`
add a separate example for overwriting a symlink to make it clear what the -T option does, as discussed in #180 2015-03-15 11:40:20 +00:00
Formatted all pages according to guidelines. 2016-01-07 17:31:27 +00:00			`- Create a hard link to a file:`
Adds some examples for ln Hopefully this will help people remember if the source is the first or second argument 2014-02-17 16:59:07 +00:00
reword to prevent ambiguity "original" can be associated with the origin of the link and lead to confusion if not read carefully. Also, the third example seems to have been copied from the prior example but not fully adapted: "original/file" should have said (if I'm reading this correctly) "original/folder". 2015-08-10 19:03:34 +01:00			`ln {{path/to/file}} {{path/to/hardlink}}`