Closed GoogleCodeExporter closed 8 years ago
See this:
http://code.google.com/p/macfuse/issues/list?
can=1&q=kld_load_from_memory&colspec=ID+Type+Status+Priority+Milestone+Owner+Sum
mary&cells=tile
s
As you can see, this was reported multiple times. Look at the details in:
http://code.google.com/p/macfuse/issues/detail?id=346
This was fixed a while ago. The problem was that Apple's Xcode was putting a
certain "load command" (data)
in binaries it compiled. However, that load command was not recognized by
kextload on PowerPC Tiger. The
"fix" was to strip that load command out of PowerPC Tiger binaries.
I just checked MacFUSE-1.7 that's currently up for download. The PowerPC kext
does not have the
problematic load command, so I don't see how you are running into this.
How do you know you are running MacFUSE-1.7? Are you sure it's not an earlier
version of MacFUSE?
Can you post the contents of
/System/Library/Filesystems/fusefs.fs/Support/fusefs.kext/Contents/Info.plist?
Just out of curiosity, what's the reason behind sticking to 10.4.6 (as opposed
to, say, 10.4.11)?
Original comment by si...@gmail.com
on 26 Aug 2008 at 4:08
Apologies for not seeing the previous reports.
I'm not on a ppc... However, it is a Thinkpad (wink, wink), x86 Intel pentium M
1.7
I wasn't surprised by the problem encountered, I was just checking if it was a
quick
permissions change, or small edit.
Another important point you bring up is the possibility of a previous MacFUSE
version. After posting, I realized that my version of Truecrypt(5.1.1) uses
MacFUSE-1.3. I found this out by installing Truecrypt-6.0 (which uses
MacFUSE-1.7)
and running into the same error.
I have since reinstalled Truecrypt(5.1.1) - which is working fine - therefore
the
Info.plist you requested reflects this (MacFuse-1.3):
----------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>CFBundleDevelopmentRegion</key>
<string>English</string>
<key>CFBundleExecutable</key>
<string>fusefs</string>
<key>CFBundleIdentifier</key>
<string>com.google.filesystems.fusefs</string>
<key>CFBundleInfoDictionaryVersion</key>
<string>6.0</string>
<key>CFBundleName</key>
<string>MacFUSE (File System In User Space)</string>
<key>CFBundlePackageType</key>
<string>KEXT</string>
<key>CFBundleSignature</key>
<string>FUSE</string>
<key>CFBundleVersion</key>
<string>1.3.0</string>
<key>OSBundleLibraries</key>
<dict>
<key>com.apple.kpi.bsd</key>
<string>8.0.0</string>
<key>com.apple.kpi.iokit</key>
<string>8.0.0</string>
<key>com.apple.kpi.libkern</key>
<string>8.0.0</string>
<key>com.apple.kpi.mach</key>
<string>8.0.0</string>
<key>com.apple.kpi.unsupported</key>
<string>8.0.0</string>
</dict>
</dict>
</plist>
---------------------------
Being that I'm using 10.4.6 on unsupported hardware, I understand there might be
other issues that are beyond the scope here. Tonight I'll try using the
MacFUSE-1.3
that is contained in Truecrypt5.1.1 (which is currently working fine) with
sshfs1.0.
I'll post the results here tomorrow. If there's any other info you need, or if
because I'm too unconventional (hardware/software wise) and you think we should
stop
here, I understand.
Original comment by dme...@yahoo.com
on 26 Aug 2008 at 10:19
Of all the unsupported hardware/software you are using, I'm mainly concerned
about the MacFUSE version *and*
distribution (as in, is it the official MacFUSE distribution, and is it the
latest version).
The only MacFUSE I am willing to support here is the latest version of the
official distribution. Although in this
case, if you are not on PowerPC, then yes, your OS is the culprit too.
If it's the "real" MacFUSE 1.7 that you tried, it can't possibly have this
error--there must be some confusion
somewhere.
Original comment by si...@gmail.com
on 26 Aug 2008 at 10:37
> If it's the "real" MacFUSE 1.7 that you tried, it can't possibly have this
error--there must be some confusion
somewhere.
Well never mind. If you are using an unsupported OS, you could have a version
of kextload that doesn't
recognize the load command.
Original comment by si...@gmail.com
on 26 Aug 2008 at 10:40
Just wanted to mention...
It's working!!!!! Well... MacFUSE-1.3 that is. Given my unconventional setup,
that's
all I could hope for.
I am able to use sshfs with no problems, mounting my G5 (a real mac), an Ubuntu
server, and different boxes I have running DSL (damnsmalllinux), all on my
Thinkpad. :-)
Original comment by dme...@yahoo.com
on 7 Sep 2008 at 12:33
Original issue reported on code.google.com by
dme...@yahoo.com
on 26 Aug 2008 at 2:56