I've noticed that if I do (*) a chown -R administrator.SYSTEM / then chown goes out onto the network and tries to access shares called //bin, //var, //usr etc., and can block for long periods, too.
Now, I do understand that really I should be doing (**) chown -R administrator.SYSTEM `cygpath -w / | sed 's|\\|/|g'` to restrict the chown to only affect Cygwin files anyway, but I'm still interested in how the spurious //bin etc. names are generated. (I.e. whether that's actually a bug?) Regards, luke ----- (*) I'm trying to work around permission problems resulting from the Cygwin *user* not being the same person as the cygwin *installer* on a machine. (**) Typically this would evaluate to: chown -R administrator.SYSTEM C:/Cygwin -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/