@Biswapriyo Device names may be standardised within Linux possibly (I don't know), but there is no standard regarding these on Unix as a whole. On what system do you have a capitalised /Dev directory?
I think compatibility with ln -s /far/away/file.txt local.dir which would create local.dir/file.txt, so if local.dir is . it should behave the same way.
ahah yes @FaheemMitha, I understoond. What led me off was that the [source] would always be a file (or whatever would serve as placeholder there). Instead, that is explained as a dir
Oh, and I suppose that in the third and fourth forms, the link name would have to be the same as the original filename, though the man page doesn't explicitly state that.
Though it would not hurt it to.
I know some people complain about verbose documentation, but unless the author is trying to write War and Peace, more is generally better when it comes to technical documentation.
@Archemar Let's swap (1) and (2). And log a call to whom?
It was approximately a link-only answer, but the real issue, to me, is that all the answers from that user (all posted a few hours ago) point to posts on a couple of blogs, likely owned by the same person/organization. Although not (all) link-only answer, they seem to be there only to drive traffic.
@StephenKitt My sixth sense told me that at least one moderator was aware of that issue already, but I couldn't restrain from writing here to be completely sure :-)
@fra-san I only saw the tip of the iceberg with that one late answer that I deleted as link-only; I didn't go looking at the rest of their answers. Thanks again for being alert!
@fra-san right, I just like to encourage people to flag for mods since that’s the best way to get their attention (in aggregate, mods are more active on their flag queue than in chat, IME)