ln: creating symbolic link `/inexistent2/path2' to `/inexistent1/path1': No such file or directory
without knowing the issued command, this leads to believe that ln tried to create entry "path1" inside directory "/inexistent1", thus writing the symlink itself there. the confusing part is "creating link to PATHNAME". btw, it is not so confusing in et_EE locale: ln: luues nimeviidet `/inexistent2/path2' -> `/inexistent1/path1': No such file or directory suggested change: ln: creating symbolic link `/inexistent2/path2' (pointing to `/inexistent1/path1'): No such file or directory or remove the symlink destination from error message: ln: creating symbolic link `/inexistent2/path2': No such file or directory as it's really irrelevant where the created symlink points, ie it can't be reason of error message. commands used to compose this email: $ LC_ALL=et_EE ln -s /inexistent1/path1 /inexistent2/path2 $ LC_ALL=C ln -s /inexistent1/path1 /inexistent2/path2 -- glen _______________________________________________ Bug-coreutils mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-coreutils
