Corinna Vinschen writes > Not quite. Directory junctions appear as symlinks. Volume junctions > are treated as simple directories since they are for all practically > purposes the same as Unix mount points.
But I still see several issues at least with directory junctions. 1. When I use junction.exe to make a junction with a regular file, the junction shows up as a regular file under cygwin. When I make a junction to a directory, the junction shows up as a directory. In particular, I don't see symlinks in either case. 2. Shouldn't we have a way of identify and/or differentiating junctions from their targets. For example, cygwin (appropriately) doesn't allow you to remove junctions using 'rm' (either files or directories). But if I am writing code to manipulate files, I would like to be able to identify junctions pro-actively rather than retroactively by the fact that I can't remove them. 3. Moving a junction, moves the target file. And leaves the junction itself 'unlinked'. I'm not sure this is the logical behavior expected, particularly if it is supposed to act like a symlink. Because with symlinks, 'mv' moves the link not the target. -- View this message in context: http://old.nabble.com/Finding-junction-points-in-cygwin-tp26260606p26269606.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple