RE: 1.7.1: cvs version built in is unstable

["Roe, Kevin L." <roe2 at llnl dot gov>]

It is a "netapp, nfs"

Here are the results of the command "/usr/lib/csih/getVolInfo /cygdrive/$drive"

Device Type        : 7
Characteristics    : 10
Max Filenamelength : 255
Filesystemname     : <NTFS>
Flags              : 4004f
  FILE_CASE_SENSITIVE_SEARCH  : TRUE
  FILE_CASE_PRESERVED_NAMES   : TRUE
  FILE_UNICODE_ON_DISK        : TRUE
  FILE_PERSISTENT_ACLS        : TRUE
  FILE_FILE_COMPRESSION       : FALSE
  FILE_VOLUME_QUOTAS          : FALSE
  FILE_SUPPORTS_SPARSE_FILES  : TRUE
  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          : TRUE
  FILE_READ_ONLY_VOLUME       : FALSE
  FILE_SEQUENTIAL_WRITE_ONCE  : FALSE
  FILE_SUPPORTS_TRANSACTIONS  : FALSE

Andy wrote:
>
>Corinna Vinschen:
>>>what would cause
>>>
>>> Â Â Â open(".new.p_change.pl", O_WRONLY | O_CREAT | O_TRUNC, 0777)
>>>
>>> to fail with errno set to ENOENT.
>>
>>Just as in Linux:
>>
>>ENOENT ÂO_CREAT is not set and the named file does not exist. Or, a
>> Â Â Âdirectory component in pathname does not exist or is a dangling
>> Â Â Â symbolic link.
>
>The way I understand this, the open() call shouldn't fail with ENOENT
>given those arguments, because O_CREAT is set and there is no
>directory component in the pathname.
>
>What type of file system is your checkout on?
>
>Andy