jed-users mailing list

[2006 Date Index] [2006 Thread Index] [Other years]
[Thread Prev] [Thread Next]      [Date Prev] [Date Next]

Re: Jed under Cygwin/WinXP


On 5/1/06, John E. Davis <davis@xxxxxxxxxxxxx> wrote:
On Mon, 1 May 2006 12:37:51 -0500, you said:
>After adding some debugging information, it looks like Cygwin doesn't
>report consistent device/inode information for files accessed via
>Samba (windows file sharing).  Google searching turns up some
>information on this:
>
>   <http://cygwin.com/ml/cygwin/2006-04/msg00383.html>

Does this mean that it is a cygwin bug?

Yes.  Cygwin is not generating device/inode numbers consistently,
when used on a remote share.

However, part of the problem appears to be inherent in SMB (the windows
file sharing protocol).  Also, some underlying filesystems (FAT) do not even
have the concept of an device/inode, so Cygwin has to create one.

>From what I can see, they've got some work-arounds/patches on this for
>some versions of Samba.  Testing those snapshots doesn't fix my
>problem, so I'm suspect the Samba version I'm using may be too old, or
>something else I don't have time to test at this point.

Perhaps I did not read msg00383.html very carefully, but it seemed to
me like the problem is with cygwin.

Yes, but you may want to put a workaround in Jed when running on Cygwin
to not try and do inode comparisons when building for cygwin.

>Anyway, commenting out the call to find_file_buffer_via_inode in
>find_file_buffer lets things work properly, at least in my initial
>testing.   Inode testing may need to be made conditional on !CYGWIN.
>But at least you're aware of it for now.

If the problem turns out to be cygwin, then is there a version number
that can be used?  That is

   #if __CYGWIN_VERSION > xxyyzz
      .
      .
   #endif

I think the work around in jed is going to be to not do inode
comparisons when built under Cygwin.

Thanks,
Pete


[2006 date index] [2006 thread index]
[Thread Prev] [Thread Next]      [Date Prev] [Date Next]