X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Mon, 14 Dec 2009 10:42:27 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Unable to read history on latest Cygwin
Message-ID: <20091214154227.GC7245@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <hg5grr$frf$1 AT ger DOT gmane DOT org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <hg5grr$frf$1@ger.gmane.org>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Mon, Dec 14, 2009 at 03:07:52PM +0100, Thorsten Kampe wrote:
>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.

Why are you sending this here when Corinna suggested sending it as an
upstream bug?  Typo?

cgf

--
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