Closed GoogleCodeExporter closed 8 years ago
No, issues specific to sshfs.app (the GUI wrapper) should *NOT* be reported
here. If people continue to reoprt
issues with sshfs.app (even after the download being marked as "unsupported"
and me having said that
umpteen times in the mailing list and here), I guess it'd be more appropriate
to simply remove the download
link. People need to understand that sshfs.app is how it is (minimal, skeletal)
because it was written only for a
single demo. If we ever do a GUI for MacFUSE, sshfs.app is not representative
of that GUI!
It's fine by me if people discuss sshfs.app related matters in the mailing
list, because unlike a formal "issue
report", it doesn't create extra and unnecessary work for me.
Issues with sshfs/sshfs-static could be MacFUSE issues though, but it's often
obvious that they're not. If you
think you've found a bug in MacFUSE through your use of sshfs, then, by all
means please do report it here.
Original comment by si...@gmail.com
on 27 Apr 2007 at 10:53
I should apologise: I'm subscribed to macfuse-devel for abridged e-mail (whilst
I'm keenly interested, I can't
describe myself as developer) but honestly, I don't recall the statements re
sshfs.app
Up until now I have watched progress via e-mail; now I see the sticky at
<http://groups.google.com/group/macfuse-devel>. Sorry!
Keep up the great work,
Graham
Original comment by grahampe...@gmail.com
on 27 Apr 2007 at 3:43
No worries and no need for apologies.
I *do* want all possible feedback from users--just that this issues list is
only for MacFUSE Core. Since sshfs.app
is not being worked upon and was never meant to be a "product", formal missing
feature requests or even GUI
bug reports for sshfs.app don't really serve much purpose.
Original comment by si...@gmail.com
on 27 Apr 2007 at 3:56
Re <http://code.google.com/p/macfuse/issues/detail?id=155#c4> I'll predict that
an appropriate option at
mount time will allow defaulting to the proper path :-)
Original comment by grahampe...@gmail.com
on 27 Apr 2007 at 4:36
Original comment by si...@gmail.com
on 27 Apr 2007 at 7:30
> I'll predict that an appropriate option at
> mount time will allow defaulting to the proper path
For the record:
public test of non-public MacFusion 1.1 Beta 2 with MacFUSE 0.3.0
results in a cross reference
from this MacFUSE issue-157
to a new MacFusion issue
http://code.google.com/p/macfusion/issues/detail?id=56
Original comment by grahampe...@gmail.com
on 10 May 2007 at 9:47
non-public MacFusion 1.1 Beta 2 with MacFUSE 0.3.0
I tried entering
~
in the server path field of MacFusion, the volume mounted but still, I'm taken
to a path one step *below* my
home directory and privileges are not what they should be,
[grahamperrin:/Volumes] gjp22% ls -alR MacFUSE-issue-157/
MacFUSE-issue-157/:
total 0
drwxrwxrwx 1 gjp22 staff 0 May 10 13:30 .
-rwxrwxrwx 1 16777216 staff 0 Feb 17 2006 Icon
drwxrwxrwx 1 16777216 staff 0 Feb 17 2006 Network Trash Folder
drwxrwxrwx 1 38091 staff 0 May 8 19:18 gjp22
MacFUSE-issue-157/Network Trash Folder:
total 0
MacFUSE-issue-157/gjp22:
total 0
Original comment by grahampe...@gmail.com
on 10 May 2007 at 10:19
Testing with MacFUSE 0.3.0 and unsupported sshfs.app 0.3.0
same problem
[grahamperrin:/Volumes] gjp22% ls -alR ndrive.uscs.susx.ac.uk/
ndrive.uscs.susx.ac.uk/:
total 0
drwxrwxrwx 1 gjp22 staff 0 May 10 13:30 .
-rwxrwxrwx 1 16777216 staff 0 Feb 17 2006 Icon
drwxrwxrwx 1 16777216 staff 0 Feb 17 2006 Network Trash Folder
drwxrwxrwx 1 38091 staff 0 May 8 19:18 gjp22
ndrive.uscs.susx.ac.uk/Network Trash Folder:
total 0
ndrive.uscs.susx.ac.uk/gjp22:
total 0
I should experiment with additional options but it's curious that SFTP clients
such as Cyberduck default to my
home directory gjp22 without difficulty. Not forgetting server adminisatrators'
advice that for this particular
service, a path should _not_ be specified.
Original comment by grahampe...@gmail.com
on 10 May 2007 at 10:23
Original issue reported on code.google.com by
grahampe...@gmail.com
on 27 Apr 2007 at 10:43