On Nov 27 16:53, Fergus wrote: > Fergus wrote: > FAT32 + [1.7] + XWin stopped being a viable combination after 1.7.60 > for the reasons you describe at > http://cygwin.com/ml/cygwin-xfree/2009-11/msg00081.html > (incidentally I find the -nolock switch has no useful effect).
You should put this to the cygwin-xfree list. Didn't the -nolock switch work for others? > So a FAT32 user is stuck with > EITHER > reverting to 1.7.0-60 if using XWin > OR > using 1.7.0-curr but without XWin. OR having a NTFS partition for issues with crippled filesystems. > Is there any likelihood that Cygwin chiefs would reconsider the > decision leading to this restriction so that the up-to-date > combination > FAT32 + [1.7.0-curr] + Xwin > remained a possibility? No, not really. This is something which should be fixed by a new Xwin. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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