On Sunday, 29 April 2012 at 14:40, Stefan Bruda wrote:
> Hi,
> 
> Latest fuse4x installation seems to be broken on my machine.  I get
> the following:
> 
>     < godel:~ > fink list fuse
>     Information about 4692 packages read in 0 seconds.
>      i   fuse4x-dev           0.10.0-1        File System in User Space 
> (fuse4x)
>      i   fuse4x-kext          0.10.0-1        Fuse4x kernel extension
>      i   fuse4x-shlibs        0.10.0-1        fuse4x shared libraries
>     < godel:~ > sshfs kleene:/misc /mnt/kleene/
>     execl: No such file or directory
>     fuse4x kernel extension was not loaded. Please check
>     /var/log/system.log for more information.
> 
> The system log does not contain any further information.  The previous
> version worked like a charm.  I have even rebooted the machine but I
> did not have high hopes and sure enough nothing changed.
> 
> Am I doing anything wrong?  Advice is much appreciated.

Sorry, that was my fault. I thought I'd tested sshfs before
committing, but it seems my local machine had an osxfuse-based sshfs
so it wasn't testing out the fink package. Oops. Should be fixed now.

> Since I am at it, is there any way to integrate sshfs into the normal
> Finder volume handling?  I am not hoping much but I though I could
> just as well ask...

Not sure what you mean by that. If you use -o volname=foo, it should
show up as an external volume on your desktop.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Fink-users mailing list
[email protected]
List archive:
http://news.gmane.org/gmane.os.macosx.fink.user
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to