Jeff, Thanks for the response! Great blog, btw.
Apparently on the CentOS server, the "corrupted" file's character encoding is "audio/mpeg": $ file -bi index.html audio/mpeg One of the files that was not corrupted in CentOS had the encoding "text/plain; charset=us-ascii": $ file -bi index.html text/plain; charset=us-ascii In OS X 10.5 under the directory that is "fused" to CentOS, the following is the encoding for both files: $file -bi index.html regular file I don't know what encoding the Simon application is using when writing the file, but I think it strange that it is basically using the same process each time (afaik) to write report HTML files and some consistently are "corrupted" and some aren't. If I knew that the Simon application should be designating an encoding type and it isn't, I could ask that they change that, but I'm wondering whether there is something I need to configure with MacFUSE such that it will properly report file encoding instead of "regular file", unless that is the normal way it should be designated. I'm not sure if the filesystem matters, but the CentOS server volume is using ext3 (according to "df -T" on the server), the local fuse volume where files are being written to is fusefs (according to "df -T fusefs" on the OS X 10.5 box which is using MacFUSE 2.0.3,2). Gary --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
