X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Wed, 15 Jul 2009 19:53:18 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: .#* lock files under X, for files I edit???
Message-ID:	<20090715175318.GW27613@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<4A157FF5 DOT 6030407 AT cornell DOT edu> <23656848 DOT post AT talk DOT nabble DOT com> <4A159713 DOT 50303 AT cornell DOT edu> <23671375 DOT post AT talk DOT nabble DOT com> <4A16BEA9 DOT 8020608 AT cornell DOT edu> <23672879 DOT post AT talk DOT nabble DOT com> <24494476 DOT post AT talk DOT nabble DOT com> <24495013 DOT post AT talk DOT nabble DOT com> <24497846 DOT post AT talk DOT nabble DOT com> <24501895 DOT post AT talk DOT nabble DOT com>
MIME-Version:	1.0
In-Reply-To:	<24501895.post@talk.nabble.com>
User-Agent:	Mutt/1.5.19 (2009-02-20)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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 Jul 15 09:49, Eric Blake wrote:
> Rather, it seems that the REAL problem is that cygwin1.dll cannot
> recognize attempts to create symlinks on the clearcase MVFS file system.
> 
> $ df -T .
> Filesystem    Type   1K-blocks      Used Available Use% Mounted on
> M:/u_fabt_eblake
>            unknown     1024000    512000    512000  50% /project/fabt
> $ volinfo .
> Device Type        : 7
> Characteristics    : 10
> Volume Name        : <CCase>
> Serial Number      : 36984713
> Max Filenamelength : 255
> Filesystemname     : <MVFS>
> Flags              : 3
>   FILE_CASE_SENSITIVE_SEARCH  : TRUE
>   FILE_CASE_PRESERVED_NAMES   : TRUE
>   FILE_UNICODE_ON_DISK        : FALSE
>   FILE_PERSISTENT_ACLS        : FALSE
>   FILE_FILE_COMPRESSION       : FALSE
>   FILE_VOLUME_QUOTAS          : FALSE
>   FILE_SUPPORTS_SPARSE_FILES  : FALSE
>   FILE_SUPPORTS_REPARSE_POINTS: FALSE
>   FILE_SUPPORTS_REMOTE_STORAGE: FALSE
>   FILE_VOLUME_IS_COMPRESSED   : FALSE
>   FILE_SUPPORTS_OBJECT_IDS    : FALSE
>   FILE_SUPPORTS_ENCRYPTION    : FALSE
>   FILE_NAMED_STREAMS          : FALSE
>   FILE_READ_ONLY_VOLUME       : FALSE
>   FILE_SEQUENTIAL_WRITE_ONCE  : FALSE
>   FILE_SUPPORTS_TRANSACTIONS  : FALSE
> $ touch foo
> $ ln -s foo bar
> $ readlink bar || echo $?
> 1
> $ cat bar
> !<symlink>~foo
> $ file bar
> bar: data
> 
> Maybe we should be trying to change cygwin to cause
> symlink() to fail with a proper errno on MVFS, and then
> revisit the emacs side of the equation to see how emacs
> handles failure to create a symlink when errno is ENOSYS
> (or whatever errno cygwin uses).  Or maybe it is just
> a matter of detecting that if the file system does not
> support DOS attributes (which are essential in creating
> new-style symlinks), that an old-style symlink must be
> created on that filesystem.

That's something we can do.  I'll look into it.


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

- Raw text -