Mail Archives: cygwin/2009/12/15/03:00:13
* Peter A. Castro (Mon, 14 Dec 2009 11:31:14 -0800 (PST))
>
> On Mon, 14 Dec 2009, Eric Blake wrote:
> >
> > 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.
>
> 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....
As mentioned this is a portable installation on a thumb drive. I would
use NTFS if there was a way to disable ACLs.
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
- Raw text -