Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 1 Apr 2005 17:23:02 +1000 (EST) From: Luke Kendall Subject: zsh startup oddity To: cygwin AT cygwin DOT com MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Message-Id: <20050401072302.134FE85080@pessard.research.canon.com.au> We found, on a release of Cygwin that's now probably almost a year old, that: If the /home directory had been created by Cygwin mkdir, and If the /etc/passwd shell specified shell to run was zsh, Then /etc/passwd would not run $HOME/.zprofile (I.e. after starting a login zsh, you'd have to explicitly source ~/.zlogin or whatever). But /etc/passwd would source $HOME/.zprofile if /home had been created by Windows Explorer. We used getfacl to examine the ACLs of directories created by mkdir and directories created by Explorer in detail. We used both setfacl and Explorer's GUI ACL thing to adjust the ACL until they appeared identical (both to getfacl and to the Explorer GUI ACL viewing thing), but with no joy: there still seemed to be a difference between Cygwin-created directories and Explorer-created ones. It went into our "to further explore one day" basket. Perhaps the problem has gone away now. I just thought I'd mention it in case this was interesting information for anyone. Brian Dessent's comment about setting the ACL for c:/cygwin reminded me of it. luke -- 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/