fchmod st_mode file type unset?

[JT Olds]

Hey, another quick question,

Background: I have a low-level interface FUSE filesystem working on
Linux that I am porting to OS X.

when setattr is called due to fchmod, on Linux FUSE the st_mode field
will include the filesystem type flags (the higher order flags of the
mode like S_IFDIR, S_IFREG, etc). Is this another intentional
difference between fuse4x and fuse? Or is this lower level than FUSE,
and fuse is just passing along OS-level data? Should these fields have
the higher order flags?

-JT

[Anatol Pomozov]

Hi

On Fri, Jun 1, 2012 at 6:32 PM, JT Olds <he...@jtolds.com> wrote:

Hey, another quick question,

Background: I have a low-level interface FUSE filesystem working on
Linux that I am porting to OS X.

when setattr is called due to fchmod, on Linux FUSE the st_mode field
will include the filesystem type flags (the higher order flags of the
mode like S_IFDIR, S_IFREG, etc). Is this another intentional
difference between fuse4x and fuse? 

 

No, this is a bug that was reported and fixed already. The fix is available in 0.9.1. Right now this fuse4x version is available only in Homebrew, I filed a request to macports as well [1].

Here is a binary package for this version https://dl.dropbox.com/u/3842605/Fuse4X-0.9.1.dmg I'll upload it to github in a few days.

[1] http://trac.macports.org/ticket/34707

[JT Olds]

Awesome, thanks. Sorry for the list-spam.

[Anatol Pomozov]

Hi

No worries. If you have a chance please grab the latest version and test that  st_mode in FUSE_STAT works exactly as you expect. Let me know the result.

[JT Olds]

Looks good. No surprises now.