I am experiencing apparently non-deterministic behavior when using open (the command line program) on a directory in my fuse filesystem. Sometimes it works as expected, launching a finder window with the directory contents. Other times it does something nutty, which I eventually figured out was it trying to open whatever has the same inode number on the actual root filesystem. So for instance I type "open /mnt/images" and it launches 0xED because both have inode 28 on their respective filesystems. I haven't spotted a pattern as to when it does the right vs. wrong thing.
My impression from the fuse docs is that st_dev (which I'm pretty sure is the struct stat field at issue here) is ignored if you set it from a fuse filesystem. Is this a bug in my code, something I'm neglecting which is leading to probably uninitialized memory being used? Or is it a bug elsewhere? Any tips appreciated. -- Paul Phillips | It's not enough to bash in heads - you've got to Apatheist | bash in minds. Empiricist | -- Capt Hammer up hill, pi pals! |----------* http://www.improving.org/paulp/ *---------- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MacFUSE" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/macfuse?hl=en -~----------~----~----~----~------~----~------~--~---
