X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Thorsten Kampe Subject: Unable to read history on latest Cygwin Date: Mon, 14 Dec 2009 15:07:52 +0100 Lines: 24 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit User-Agent: MicroPlanet-Gravity/2.9.14 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Hi, the new Cygwin 1.7 release is soon to be released. According to Cygwin Project Co-Leader Corinna Vinschen, Cygwin will drop "fake support" for emulating hardlinks on FAT32: "Hardlinks on FAT [...] have been faked in 1.5 by copying the file. The decision was made a couple of weeks back to drop this fake since the application should know that the underlying filesystem is not capable of creating hardlinks." The result of that is that I'm not able to run zsh "portable" from a FAT32 USB thumb drive: "zsh: failed to create hard link as lock file /home/thorsten/.zhistory.LOCK: operation not permitted". (Zsh is running but history is neither saved nor written). histfcntllock also results in errors. "Your best bet now might be to report this as an upstream bug to zsh, and recommend that they use an alternative approach, such as symlink locking (the way emacs does things), if hard link locking doesn't work because of the underlying file system." Bash does not exihibit the error. Thorsten -- 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