X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.8 required=5.0 tests=AWL,BAYES_00,TVD_RCVD_IP X-Spam-Check-By: sourceware.org Date: Mon, 14 Dec 2009 11:31:14 -0800 (PST) From: "Peter A. Castro" To: Cygwin List Subject: Re: [1.7] hard link error on FAT32 with zsh In-Reply-To: <4B2639AC.1060708@byu.net> Message-ID: References: <20091214105829 DOT GE8059 AT calimero DOT vinschen DOT de> <4B2639AC DOT 1060708 AT byu DOT net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Mon, 14 Dec 2009, Eric Blake wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > According to Thorsten Kampe on 12/14/2009 5:22 AM: >>> That's why. FAT32 does not support hardlinks. >> >> Well, then why don't I get this error with the latest 1.5 DLL? It's the >> same thumb drive, the same installation... > > It _didn't_ work. In 1.5, you ended up creating a copy, which meant there > was no locking after all. If zsh then depended on that attempt at locking > working, you would have gotten into inconsistent states. > > 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. You may not have to. The code thats doing this is dependent on the link() function existing. However, there's an alternative path in that code in case link() is unavailable. I'll hack Configure to undefine link's usage and see what it does. On a side not, Thorsten, you should be able to set your history file to an NTFS filesystem as a workaround. Not ideal, I know, but it should be servicable for the time being. Or, for that matter, why are you still using FAT32? Just curious.... > - -- > Don't work too hard, make some time for fun as well! > > Eric Blake ebb9 AT byu DOT net > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (Cygwin) > Comment: Public key at home.comcast.net/~ericblake/eblake.gpg > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAksmOawACgkQ84KuGfSFAYA2pwCgmtM6fw/F8WM2CjbVtbNH1Zgs > hI8An3emaP4qePXhEf4G2F3IBRvEWUCS > =LQ5E > -----END PGP SIGNATURE----- > > -- > 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 > -- Peter A. Castro or "Cats are just autistic Dogs" -- Dr. Tony Attwood -- 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