symlink

I have the following File object pointing to a directory via symbolic link, File directory = new File("/path/symlink/foo/bar"); String[] files = directory.listFiles(); listFiles() returns null, is this because of the symlink? if yes, how will I go about this if I really want to list the files in bar using the path that contains a symlink? According to what I've seen while Googling this puzzling behavior, Java requires that you call .getCanonicalFile() on a File whose path contains a link before you can use it in other file operations. So: File directory = new File("/path/symlink/foo/bar")

Closed. This question is off-topic. It is not currently accepting answers. Learn more . Want to improve this question? Update the question so it's on-topic for Stack Overflow. From a high-level standpoint (meaning only worrying about the results and the interface, not the implementation), what is the difference in behavior, if any, between an NTFS reparse point that points to a directory and a symbolic link that points to the same directory? Are they resolved at the same level in the stack, or is it possible for one to be unresolvable at a certain time when the other one can be resolved (e.g.

I have a lot of relative symbolic links that I want to move to another directory. How can I move symbolic links (those with a relative path) while preserving the right path? You can turn relative paths into full paths using readlink -f foo . So you would do something like: ln -s $(readlink -f $origlink) $newlink rm $origlink EDIT: I noticed that you wish to keep the paths relative. In this case, after you move the link, you can use symlinks -c to convert the absolute paths back into relative paths. daxim This is a perl solution that preserves relative paths: use strictures; use File::Copy qw