Folder matching one on the SSHFS server needed on the Mac client

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install MacFUSE
2. Run [ sshfs -ovolname="VolumeName" -oping_diskarb user@0.0.0.0: FolderName ]

sshfs wouldn't connect until I added a folder in the user home directory. 
(e.g., /Users/username/
FolderName). Without the folder I get the error [ mount_fusefs: 
/Users/username/FolderName: No 
such file or directory ] when trying to connect. I just created two blank 
folders with the same names 
in the home directories of the server and client and it works great.

I downloaded and installed [ MacFUSE-0.1.0b006.dmg ]. I'm running Mac OS X 
10.4.8 build 8L127. 
If it matters, I'm also on a PowerPC Mac.

Original issue reported on code.google.com by timbaumg...@gmail.com on 17 Jan 2007 at 1:59

[GoogleCodeExporter]

Requiring the folder to already exist is normal, and the way it's intended to 
work.

It's a little weird to think of it this way at first, but mounting a Unix 
filesystem
doesn't create a new branch on the directory tree, but grafts a disk directory 
onto
an existing folder. Therefore, the usual sequence (for all Unixes) is

1. Create an empty directory
2. Mount the filesystem onto that folder/directory
3. Use the filesystem
4. Unmount the filesystem
5. Erase the empty directory (or leave it around for repeating at step 2)

The Mac is a bit different in that if you use -oping_diskarb, the Mac will
automatically clean up the directory (step 5) when you eject the disk. But the 
other
steps remain, even the one of creating empty directories as mountpoints.

Original comment by motown...@gmail.com on 17 Jan 2007 at 5:51

[GoogleCodeExporter]

Ahhh! I see. I am familiar with mounting in Unix, but I was assuming that the 
filesystem would be automatically 
mounted to the /Volumes folder on a Mac, and not to a folder of the same name 
in the user's home directory. 
Any chance that this may be what happens in future versions? Or maybe just a 
command line option to specify 
what folder that the filesystem is mounted to?

Original comment by timbaumg...@gmail.com on 17 Jan 2007 at 6:44

[GoogleCodeExporter]

Nevermind! I was thinking that the mount point part of the command was the 
folder on the server. In that case, 
maybe something to choose which folder to mount?

Original comment by timbaumg...@gmail.com on 17 Jan 2007 at 6:52

[GoogleCodeExporter]

To specify the folder on the _server_ to mount, just put that after the colon, 
no
space, like:

sshfs [...] user@1.2.3.4:/tmp /Volumes/othertemp

As for putting your mountpoint in /Volumes, that's a good idea (and what I do) 
but
you still have to do it manually. Just create a folder in /Volumes, and mount 
on it.
That's actually what happens behind the scenes with disks you attach.

For the command-line tools, we're aiming for functional equivalence with the 
Unix
command-line tools, which means making your own mountpoint folder. When it 
comes to
the GUI wrappers (that we demoed and hope to be able to release soon), though,
_those_ definitely will take care of automatically creating folders in /Volumes 
for
you, and make this a simpler experience.

Closing.

Original comment by motown...@gmail.com on 17 Jan 2007 at 2:38

• Changed state: Invalid