Thanks for the descriptive response, Amit - I guess I should have known better than to assume the sharing GUI would play nice with filesystem extensions. Mounting with deferred permissions didn't change much (assuming I was doing it correctly - the defer_permissions option can just be added to the fs implementation's, e.g. ntfs-3g's, command line, right?), but on trying another MacFUSE implementation (sshfs) it's clear that the permission symptoms are independent of the filesystem, and presumably of the mounting mechanism as well.
In any case, my particular problem was easily solvable with a simple "read only = yes" once I found where Leopard had moved my proper samba configuration files. The result isn't integrated well with the OS X GUI, that is, no "Shared Folder" heading in Finder nor the list item in the Sharing prefpane, but I'm hardly missing those - point being, the actual process of sharing the FUSEd volume over a network via traditional samba means seems effective and painless. Conclusively, thank you for pointing me in the right direction, and for developing such an awesome tool! On Jun 30, 6:54 pm, Amit Singh <[EMAIL PROTECTED]> wrote: > There are too many layers involved in your scenario (Mac OS X kernel > itself, various file system API layers in OS X, MacFUSE, ntfs-3g user- > space, components that deal with network sharing, and so on.) Several > end-user-facing parts of OS X simply don't support the possibility of > a third party file system. For example, they can make hardcoded > assumptions as to what a "remote" file system is. These components are > also closed source and insanely multi-layered, making things extremely > difficult to debug. (If one were to count the number of file and > process abstractions in OS X, it would blow one's mind.) > > MacFUSE takes the third party situation to the extreme because unlike > other file systems (say, NFS or AFP), which have a single personality, > MacFUSE file system can behave in arbitrary ways. Point being that > there is no one party to blame. In hindsight, parts of Mac OS X could > be written better. > > For your issue: try mounting the ntfs-3g volume with the > defer_permissions mount-time option and see what happens. That will > take the Mac OS X kernel out of file access authorization decisions. > Then, it would be entirely up to the user-space file system to allow > or deny access. > > Amit > > On Jun 30, 6:29 pm, "terry.suereth" <[EMAIL PROTECTED]> wrote: > > > > > My issue regards an NTFS volume I've mounted on my 10.5.3 Intel > > machine using MacFUSE. I am honestly not sure if I should take this > > up with MacFUSE or with ntfs-3g, so feel free to tell me to troll > > elsewhere. > > > In a nutshell, I want to network-share some of my NTFS partition - > > parts publicly read/writable, and parts read-only. However, using > > MacFUSE (including today's new version) and ntfs-3g, I have been > > unable to achieve a read-only share. File permissions are seen as > > "You have custom access" throughout the mounted volume, and I can do > > basically nothing with them; if I change an access setting in > > Leopard's Sharing prefpane, the setting does not save, and resets the > > next time I open the pane. E.g, I am only able to create a share on > > my NTFS volume that is Read/Write enabled for Everyone. > > > I've tried the baked ntfs-3g installation > > fromhttp://macntfs-3g.blogspot.com/ > > as well as installing it from source, and have been met with similar > > results. I tried mounting the volume manually with uid/gid options to > > give me personal ownership, but then my permissions just become "You > > can read and write" and I cannot edit them; plus, when the volume is > > mounted in this way, I am no longer able to add any of its contents as > > sharing locations in the Leopard prefpane. (I also tried screwing > > around with my smb.conf to this end, but was unsuccessful. I think > > Leopard has this hornswoggled somehow) > > > I feel like this is a permissions issue, e.g. Leopard needs to be able > > to administer the volume for sharing, and it also needs me to be able > > to administer it or it will ignore my sharing access settings. Or, > > maybe it's a filesystem problem of not dealing with NTFS permissions > > right at all. I'm not really sure. > > > Any ideas? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
