Just got this working yesterday, and I don't think it's related to
the ._ files (also called AppleDouble files; google that for more
info).   MacFuse 1.5.1 newly supports the st_flags field, so in your
stat struct, try explicitly adding this field and setting it 0.  That
is, your stat struct should now look like:

struct stat {
         dev_t           st_dev;           /* ID of device containing
file */
         mode_t          st_mode;          /* Mode of file (see below)
*/
         nlink_t         st_nlink;         /* Number of hard links */
         ino_t         st_ino;          /* File serial number */
         uid_t           st_uid;           /* User ID of the file */
         gid_t           st_gid;           /* Group ID of the file */
         time_t        st_atime;     /* time of last access */
         time_t        st_mtime;     /* time of last data modification
*/
         time_t        st_ctime;     /* time of last status change */
         off_t           st_size;          /* file size, in bytes */
         uint32_t        st_flags;         /* user defined flags for
file */
}

Search for chflags(2) for more info about this new field.

On Jun 10, 3:02 am, qabi <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I'm working on a filesystem that stores data remotely (imapfs on
> google code). To improve responsiveness, a local cache is kept on
> disk.
>
> However I cannot seem to copy files to the filesystem with Finder. It
> varies between telling me that the file cannot be written since it is
> locked, and because of not enough permissions (the same file). The
> filesystem doesn't support permissions, so uid and gid are both 777.
>
> I can see that the file is copied to the local on-disk cache just
> fine, but still the complaints about being locked or permissions.
>
> I suspect it has something to do with the ._ files, but it's hard to
> debug, since I have no idea how these files are used and should
> behave. The ._ file is also written fine (with another name, since
> that seems necesarry) to the cache dir.
>
> Any help on how to debug such issues, or an authorative description of
> the ._ file concept would be very much appreciated.
>
> Thanks,
>
> -dennis
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"macfuse-devel" group.
To post to this group, send email to macfuse-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/macfuse-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to