'noappledouble' can make the Finder unhappy under some circumstances.
There's no way around it. File systems just don't work that way (that
you can simply "deny" certain file operations and all software layers
above the file system will still be magically happy).

When I implemented this option, I wrote the following note in the
changelog:

"I personally am not too excited about this option, but here it is in
case somebody wants to experiment. I haven't tested this, especially
in how it might affect the Finder and other applications. Use at your
own peril."

If you want the Finder to be more amenable to non-Apple file systems,
you should file bugs/feature requests with Apple.

Amit

On Jan 8, 6:27 am, iDeveloper <[email protected]> wrote:
> Hi
>
> I am creating a read-write file system using the template provided by
> MacFUSE 2.0. I am using the mount option noappledouble.
> All write operations work fine and give the desired output except when
> I copy a file or drag-drop a file from the local file system to the
> mounted FS.
>
> On drag-drop, an empty file is created on the FS and then I get a
> prompt that I might need to enter an admin password to change the file
> named "whatever the file is" and on entering the password, the old
> file is deleted and a new file is created to which the contents are
> finally written.
>
> On copy-pasting, I do not get the alert but the password dialog opens
> up directly before the copy operation is complete. I don't face this
> problem when copying files from the terminal.
>
> The password dialog shows com.apple.desktopservices as asking for
> password. Can someone please help me find out where the problem lies?
>
> Thank you.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to