Yep, that's the scenario I was in. Installed MacFuse on Tiger; upgraded to Leopard, then upgraded to latest MacFuse and couldn't get it to install.
That's ok...it gave me a good excuse to buy a new MacBook with Leopard pre-installed. MacFuse works great now! Thanks for the help folks! On Feb 24, 2:29 am, paintrain <[email protected]> wrote: > No, the problem was not with the MacPorts version, I just used that as > an intermediate step to get more verbose feedback on what > was going wrong after my MacFuse for tiger stopped working when > upgrading to leopard and the official 2.0.3,2 dmg would not install. > > On Feb 24, 12:03 am, Amit Singh <[email protected]> wrote: > > > > > There's no "activation stage" in the official MacFUSE package. > > > Are you talking about the MacPorts "distribution" of MacFUSE? You > > should report issues with that on the MacPorts web site. > > > There's an official binary distribution which users are strongly > > encouraged to use. The core MacFUSE software is not something that > > lends itself too well to being repackaged or recompiled on end user > > machines. > > > Amit > > > On Feb 23, 2:04 pm, paintrain <[email protected]> wrote: > > > > Hi, I got into the same trouble when upgrading my MacBook Pro to > > > leopard 10.5.6 from latest tiger: > > > > It looks like the problem is in the activation stage of the new > > > package: > > > > I tried to install macfuse (old version though) via MacPorts: sudo > > > port -v install macfuse > > > and got this complaint: > > > ---> Activating macfuse @1.7_1 > > > Error: Target org.macports.activate returned: Image error: /Library/ > > > Frameworks/MacFUSE.framework/Headers already exists and does not > > > belong to a registered port. Unable to activate port macfuse > > > > Then I removed the MacFuse.framework directory, tried to complete port > > > install again, and now I got a complaint about the odd fusefs symlink > > > in /Library/Filesystems/ > > > ---> Activating macfuse @1.7_1 > > > Error: Target org.macports.activate returned: can't create directory "/ > > > Library/Filesystems/fusefs.fs": file already exists > > > Warning: the following items did not execute (for macfuse): > > > org.macports.activate > > > > Then I removed this symlink, and re-executed the port install , and > > > now it worked ok! Hence, my next step was to download and install the > > > MacFUSE-2.0.3,2.dmg which now also worked ok, showing up as installed > > > in System preferences and everything :-) > > > > So I suppose, if you remove the MacFUSE.framework directory and that > > > fusefs.fs symlink you may be able to install the dmg without the > > > MacPorts installation, although I haven´t tested this myself. > > > > Hope this helps you guys out... > > > > On Feb 20, 5:14 pm, Steven R <[email protected]> wrote: > > > > > I am also in the same situation, it appears migration to Leopard > > > > resulted in an inability to uninstall MacFUSE via System Preferences > > > > or the command line methods described. > > > > Any other suggestions greatly appreciated. > > > > Thanks > > > > > On Feb 5, 3:43 pm, Mike <[email protected]> wrote: > > > > > > Hi Amit, > > > > > Could it have something to do with me originally having Tiger on this > > > > > box, then installing some older versions of MacFusion and ExpanDrive, > > > > > then migrating toLeopard, then trying to upgrade to MacFUSE 2? > > > > > > I'm wondering if I should just wipe the disk and and start with a > > > > > fresh install of the OS; or is there some easier way to clean the > > > > > files from the disk? > > > > > > thanks! > > > > > > On Feb 5, 12:24 pm, Amit Singh <[email protected]> wrote: > > > > > > > Given that you are onLeopard, there should be nothing pointing to / > > > > > > System/Library/Filesystems in an official MacFUSE installation. The > > > > > > MacFUSE package also doesn't create a fusefs.fs symlink. This > > > > > > doesn't > > > > > > look like a correct/official installation to me. > > > > > > > Amit > > > > > > > On Feb 5, 5:06 am, Mike <[email protected]> wrote: > > > > > > > > Hi Amit, > > > > > > > > Sorry about that, I should have given a little more detail. I was > > > > > > > trying to uninstall using the instructions in the FAQ and that is > > > > > > > when I stumbled onto the strange symlink with a double // in the > > > > > > > path. > > > > > > > the fusefs symlink lives in /Library/Filesystems/ > > > > > > > > Last login: Thu Feb 5 00:00:32 on ttys000 > > > > > > > minimac:~ rivaryans$ cd / > > > > > > > minimac:/ rivaryans$ ls > > > > > > > Applications dev > > > > > > > Desktop DB etc > > > > > > > Desktop DF home > > > > > > > Developer mach.sym > > > > > > > Library mach_kernel > > > > > > > Network mach_kernel.ctfsys > > > > > > > System net > > > > > > > User Guides And Information private > > > > > > > Users sbin > > > > > > > Volumes tmp > > > > > > > bin usr > > > > > > > cores var > > > > > > > minimac:/ rivaryans$ ls -es /Library/FileSystems/ > > > > > > > total 8 > > > > > > > 8 fusefs.fs > > > > > > > minimac:/ rivaryans$ cd /Library/Filesystems > > > > > > > minimac:Filesystems rivaryans$ ls -el > > > > > > > total 8 > > > > > > > lrwxr-xr-x 1 root admin 38 Dec 30 19:40 fusefs.fs -> /System// > > > > > > > Library/Filesystems/fusefs.fs > > > > > > > minimac:Filesystems rivaryans$ > > > > > > > > The /System/Library/Filesystems/ folder looks like this > > > > > > > > minimac:Filesystems rivaryans$ cd /System/Library/Filesystems > > > > > > > minimac:Filesystems rivaryans$ ls > > > > > > > AppleShare cd9660.fs hfs.fs ntfs.fs > > > > > > > ufs.fs > > > > > > > URLMount cddafs.fs msdos.fs smbfs.fs > > > > > > > webdav.fs > > > > > > > afpfs.fs ftp.fs nfs.fs udf.fs > > > > > > > zfs.fs > > > > > > > minimac:Filesystems rivaryans$ > > > > > > > > Any ideas? > > > > > > > > Thanks! > > > > > > > > On Feb 5, 12:18 am, Amit Singh <[email protected]> wrote: > > > > > > > > > In which directory does this symlink exist? > > > > > > > > > See Q 2.3 and 1.2 in the MacFUSE FAQ for information on how to > > > > > > > > uninstall broken MacFUSE installations manually. > > > > > > > > > Amit > > > > > > > > > On Feb 4, 9:14 pm, Mike <[email protected]> wrote: > > > > > > > > > > Here is a follow up. I have tried to run the > > > > > > > > > uninstall-macfuse-core.sh > > > > > > > > > script on my install and it looks like I have a bad symlink > > > > > > > > > generated > > > > > > > > > as it won't uninstall fuse. > > > > > > > > > > minimac:filesystems rivaryans$ ls -le > > > > > > > > > total 8 > > > > > > > > > lrwxr-xr-x 1 root admin 38 Dec 30 19:40 fusefs.fs -> > > > > > > > > > /System// > > > > > > > > > Library/Filesystems/fusefs.fs > > > > > > > > > > I'm at a point where I am not able to install any version of > > > > > > > > > MacFUSE > > > > > > > > > and I can't seem to clean off the old versions. > > > > > > > > > > On Feb 4, 8:27 pm, Mike <[email protected]> wrote: > > > > > > > > > > > Hi, > > > > > > > > > > I'm trying to install MacFUSE 2.0.3 from the MacFUSE System > > > > > > > > > > Preferences onLeopardrunning on a Mac Mini. I click the > > > > > > > > > > Install > > > > > > > > > > MacFUSE button and it spins for a while then comes back and > > > > > > > > > > says > > > > > > > > > > "MacFUSE does not appear to be installed." > > > > > > > > > > > Any ideas how I can fix this? > > > > > > > > > > > Thanks > > > > > > > > > > Mike- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
