Thanks, this saved my life. It was driving me nuts trying to remember how to do this. This is simple and concise. Five stars!
For some reason I can't get this command to work. Please help.On an intel x86 BSD box with 4G ram.C:\>ln -s'ln' is not recognized as an internal or external command,operable program or batch file.C:\>
This comment has been removed by the author.
Hey Alex! After using linux for many years, I was still struggeling too to remember the order of the 'ln -s' params. But I think this will be my saviour: it's the same order as 'cp'. Do this and see if it helps:$ echo test > org$ cp org copy # order is intuitive$ ln -s org live.copy # order becomes intuitive (for me at least)The terms for ln is swapped, though. The 'org' is the target (source for cp), and the live.copy the link-name (target for cp).
Thanks, this saved my life. It was driving me nuts trying to remember how to do this. This is simple and concise. Five stars!
ReplyDeleteFor some reason I can't get this command to work. Please help.
ReplyDeleteOn an intel x86 BSD box with 4G ram.
C:\>ln -s
'ln' is not recognized as an internal or external command,
operable program or batch file.
C:\>
This comment has been removed by the author.
ReplyDeleteHey Alex!
ReplyDeleteAfter using linux for many years, I was still struggeling too to remember the order of the 'ln -s' params.
But I think this will be my saviour: it's the same order as 'cp'. Do this and see if it helps:
$ echo test > org
$ cp org copy # order is intuitive
$ ln -s org live.copy # order becomes intuitive (for me at least)
The terms for ln is swapped, though. The 'org' is the target (source for cp), and the live.copy the link-name (target for cp).