Spotlight (mdimport) runs as root, so on a MacFUSE volume, spotlight won't be able to create an index and hence the disk will be unsearchable (on leopard) by any finder methods. I run a lot of video files on the particular NTFS volume, and using spotlight is my preferred method of tracking down files so I can watch them. Using NTFS-3g I have fiddled around with the mount-time (boot auto mount) options, to no success. setting allow_other, seems to have no effect on root processes, and allow_root denies all access except to root.
My main issue here is not the theory behind root access, but how to actually do it - what options to use and how. The options wiki page is thick on technical theory, and thin on practical theory. Again I apologise for my ignorance regarding macFUSE. It is a truly great system (and I don't know why apple has not implemented something like this as standard in Leopard).... On 04/02/2008, Amit Singh <[EMAIL PROTECTED]> wrote: > > > On Feb 3, 12:23 pm, "Chris Cleeland" <[EMAIL PROTECTED]> wrote: > > > What is driving the OP's need for root access to a FUSE filesystem? > > I don't know the OP's need, but there can be plenty of reasons for > root access to a MacFUSE file system. If any system daemon or > component running as root (Spotlight is a canonical example) wants to > access a MacFUSE volume, you'll need to explicitly turn off MacFUSE's > blanket denial. > > > Is it possible to do something with FUSE similar to what NFS does with > > 'root'--translation to a different UID? > > Of course, but lets not mix the issues at hand--the issue I was > talking about is allowing a process running as root access to a > MacFUSE volume. I was *not* talking about root access so that root > owned files on the file system can be accessed. > > Besides, there's no need to reinvent the wheel--it's already been > reinvented. The file system itself can do whatever it pleases and > advertise any UIDs it wants. sshfs already translates remote UIDs and > GIDs to that of the local user. You can also use the > 'defer_permissions' MacFUSE option, which will stop the Mac OS X > kernel from doing any permission checks itself, and will simply let > through all operations to the user-space file system (which can still > disallow operations if it so chooses). > > 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 -~----------~----~----~----~------~----~------~--~---
