On Nov 4, 4:57 pm, unsound <[EMAIL PROTECTED]> wrote: > Thanks a lot Amit. You were 100% correct. Removing the use_ino flag > internally and recompiling did solve the issue. > Does this have any impact on the operation of the file system? From > what I understand, it now works exactly like MacFUSE 0.4.0, which > didn't pass the internal inode information on to the operating > system... correct assumption?
Quite incorrect. I didn't say that you remove use_ino and use that as the fix. I only wanted you to experiment. No, it doesn't work exactly like MacFUSE 0.4.0 either. MacFUSE does, and always has supported use_ino. Please reread what I said carefully. I was talking about *parents'* inode numbers (which is an additional thing you can retrieve in OS X), not inode numbers in general. I wouldn't advise removing use_ino and shipping your package. I did say I'd release a point update soon--very soon. Amit --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "macfuse-devel" 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-devel?hl=en -~----------~----~----~----~------~----~------~--~---
