Timeline for Copying symlinks as symlinks
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 12, 2024 at 17:21 | comment | added | GMaster |
@TheorVHP There is a subtle difference between -f and -e. See the help readlink --help for the explanation. (Should not be a macOS thing, but I don't have access to macOS to check)
|
|
| Apr 10, 2024 at 13:15 | comment | added | TheorVHP |
@GMaster, yes, readlink -f worked. Using -e instead resulted in an error. Is that because I’m using macOS?
|
|
| Apr 9, 2024 at 8:47 | comment | added | GMaster |
@TheorVHP Yes. readlink -e symlink
|
|
| Apr 7, 2024 at 13:08 | comment | added | TheorVHP | @GMaster, thanks. That makes sense. Is there a way to automatically determine the full real path to the source file from a relative symlink? | |
| Apr 6, 2024 at 13:18 | comment | added | TheorVHP | @OliverKnodel, I agree. I misspoke. I was intending to ask about a solution if I don’t know the original path. | |
| Apr 5, 2024 at 16:35 | comment | added | Jim L. |
@OliverKnodel Right idea, but other way 'round: ln -s $(realpath source) destination
|
|
| Apr 5, 2024 at 12:53 | comment | added | Oliver Knodel |
You don't need to know the inode if you use ln -s: ln -s destination $(realpath source-file).
|
|
| Apr 5, 2024 at 11:41 | comment | added | GMaster |
cp -P will work as long as the original symlink created is a absolute symlink to the source rather than a relative one.
|
|
| S Apr 5, 2024 at 11:33 | review | First questions | |||
| Apr 5, 2024 at 14:52 | |||||
| S Apr 5, 2024 at 11:33 | history | asked | TheorVHP | CC BY-SA 4.0 |