Re: [1.7] hard link error on FAT32 with zsh
* 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
Re: [1.7] hard link error on FAT32 with zsh
On Dec 11 21:36, Thorsten Kampe wrote: Hi, I was testing the latest 1.7 DLL snapshot (1.7.2s(0.218/5/3) 20091209 12:02:30) and the current 1.7 one (that you get from setup-1.7.exe). I am starting zsh and get the following error: zsh: failed to create hard link as lock file /home/thorsten/.zhistory.LOCK: operation not permitted. This relates to the following setting in .zshrc: HISTFILE=~/.zhistory. Zsh starts but no history is available. Cygwin is located on a FAT32 thumb drive. That's why. FAT32 does not support hardlinks. 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
Re: [1.7] hard link error on FAT32 with zsh
* Corinna Vinschen (Mon, 14 Dec 2009 11:58:29 +0100) On Dec 11 21:36, Thorsten Kampe wrote: Hi, I was testing the latest 1.7 DLL snapshot (1.7.2s(0.218/5/3) 20091209 12:02:30) and the current 1.7 one (that you get from setup-1.7.exe). I am starting zsh and get the following error: zsh: failed to create hard link as lock file /home/thorsten/.zhistory.LOCK: operation not permitted. This relates to the following setting in .zshrc: HISTFILE=~/.zhistory. Zsh starts but no history is available. Cygwin is located on a FAT32 thumb drive. 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... I used to test 1.7 DLLs and in some snapshot the error was introduced. 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
Re: [1.7] hard link error on FAT32 with zsh
On Dec 14 13:22, Thorsten Kampe wrote: * Corinna Vinschen (Mon, 14 Dec 2009 11:58:29 +0100) On Dec 11 21:36, Thorsten Kampe wrote: Hi, I was testing the latest 1.7 DLL snapshot (1.7.2s(0.218/5/3) 20091209 12:02:30) and the current 1.7 one (that you get from setup-1.7.exe). I am starting zsh and get the following error: zsh: failed to create hard link as lock file /home/thorsten/.zhistory.LOCK: operation not permitted. This relates to the following setting in .zshrc: HISTFILE=~/.zhistory. Zsh starts but no history is available. Cygwin is located on a FAT32 thumb drive. 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... I used to test 1.7 DLLs and in some snapshot the error was introduced. It's not a bug, it's a feature. Hardlinks on FAT don't exist. They have been faked in 1.5 by copying the file. The decision was made a coupld of weeks back to drop this fake since the application should know that the underlying filesystem is not capable of creating hardlinks. It's in the mail archive and in the What's new section of the User's Guide. 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
Re: [1.7] hard link error on FAT32 with zsh
-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. - -- Don't work too hard, make some time for fun as well! Eric Blake e...@byu.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
Re: [1.7] hard link error on FAT32 with zsh
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 e...@byu.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 doc...@fruitbat.org or peter.cas...@oracle.com 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
[1.7] hard link error on FAT32 with zsh
Hi, I was testing the latest 1.7 DLL snapshot (1.7.2s(0.218/5/3) 20091209 12:02:30) and the current 1.7 one (that you get from setup-1.7.exe). I am starting zsh and get the following error: zsh: failed to create hard link as lock file /home/thorsten/.zhistory.LOCK: operation not permitted. This relates to the following setting in .zshrc: HISTFILE=~/.zhistory. Zsh starts but no history is available. Cygwin is located on a FAT32 thumb drive. 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
