Considering that it's a backup application you are talking about, it's probably trying to access the MacFUSE volume as root. This is disallowed by default. See notes for 'allow_other' and 'allow_root' in http://code.google.com/p/macfuse/wiki/OPTIONS. Then try mounting the volume with '-oallow_other' and see if it works.
By the way, software can always tell the "type" (AFP, NFS, SMB, MacFUSE, ...) of the underlying file system. The operating system provides functions to do that. What the software does with that information is its business. For example, the Finder only wants to show those "remote" volumes in the sidebar whose type matches that of a hardcoded list of strings. MacFUSE is not on that list, so the Finder doesn't show MacFUSE volumes in the sidebar by default. Similarly, the Startup Disk prefpane only looks for "ntfs" volumes (and filters out "ntfs-3g" volumes) when listing bootable NTFS volumes. All volumes are distinguishable. Amit On Dec 29, 8:55 pm, cyberfunk <[email protected]> wrote: > Forward: I'm using Macfusion to mount volumes via SSHFS, but this is a > problem when the volumes are mounted manually, too (i.e. via the > commandline w/ sshfs). > > I dont know if this is a problem with Silverkeeper or with MacFUSE, > and i'm not sure exactly how to figure out which...but when I try to > use LaCie's free Silverkeeper (backup utility > @http://www.lacie.com/silverkeeper/) to select a SSHFS mounted volume > as a source, it refuses to see inside, or even read the source in the > "select source" dialog box, which is akin to an open file dialog box > as far as I can tell. I've noticed, however that in other programs > (e.g. Textedit, Word, etc) the open dialog box correctly displays the > mounted volume and the files within (and said files are accessible as > per normal). I've tried the -olocal option to treat the mounted > volume as local. And although that works fine for the Finder, it > still doesnt fix the Silverkeeper problem. > > Any suggestions on what I should try, or which program's fault this > bug is ? > > Clearly the problem lies in an interaction between > Silverkeeper and MacFUSE volumes, because Silverkeeper works with many > different brands of drive as well as mounted network shares (i've used > AFS shares successfully before as source and destination). > > My question is: How does Silverkeeper know the difference? Shouldn't > MacFUSE drives appear to it like any other drive? And more > importantly.. if Silverkeeper has this problem, what other software > has this problem that we are yet to discover? > > P.S. My overall goal here is a backup solution, for which I would > normally use rsync, but it's not installed on the remote side, and all > I have is sftp access, so I figured what I'd do was mount the ssh > access as a volume w/ MacFUSE and then use silverkeeper to do a > backup. And yes, I know, I could use rsync locally after i've mounted > the volumes w/ MacFUSE, which, essentially is my solution at the > moment. I'm more troubled by an app treating the MacFUSE volume > differently than a normal volume, as I was under the impression that > MacFUSE volumes were supposed to be indistinguishable. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
