I was able to re-compile MacFUSE and get it to load in a 10.0.0 64-bit
kernel.
Although this may be a simple fix that is all that we need to get it
working, and be stable, there is NO confirmation from Amit. As far as
I can tell, this is the only patch made public for MacFuse to work the
latest 64-bit Snow Leopard kernel. With so many people depending upon
MacFUSE to support their projects, you think there would be more
community involvement, or discussion.
I was so excited to see a post from Amit on his blog, after 5.5 months
of no activity. I thought for sure a patch to MacFUSE would be out
shortly. Nothing. The only thing is Amit commenting on how to get the
64bit kernel working on machines that normally won't enable it:
http://www.osxbook.com/blog/2009/08/31/is-your-machine-good-enough-fo...
Amit writes MacFUSE in his spare time and from what I gather, he's
rather busy at Google.
The entire Mac community benefits having him lead this project; there
are extremely few people who can produce kernel code of such
complexity and quality. While I understand your desire to have MacFUSE
working in 64-bit mode - try to avoid suggesting that Amit *owes* you
updates and notes regarding this project he gracefully pours his spare
time into without direct compensation or incentive.
-Jeff
On Sep 9, 5:52 pm, exs <extre...@gmail.com> wrote:
> I was able to re-compile MacFUSE and get it to load in a 10.0.0 64-bit
> kernel.
> Although this may be a simple fix that is all that we need to get it
> working, and be stable, there is NO confirmation from Amit. As far as
> I can tell, this is the only patch made public for MacFuse to work the
> latest 64-bit Snow Leopard kernel. With so many people depending upon
> MacFUSE to support their projects, you think there would be more
> community involvement, or discussion.
> I was so excited to see a post from Amit on his blog, after 5.5 months
> of no activity. I thought for sure a patch to MacFUSE would be out
> shortly. Nothing. The only thing is Amit commenting on how to get the
> 64bit kernel working on machines that normally won't enable it:
> http://www.osxbook.com/blog/2009/08/31/is-your-machine-good-enough-fo...
> I was able to re-compile MacFUSE and get it to load in a 10.0.0 64-bit > kernel.
I've had some issues when testing a 64-bit compiled version of the kext, built from the current SVN state. When booting my MacBook Pro / Snow Leopard 64-bit mode with the kext in place, I lose the keyboard and mouse. The current SVN state is of course not in a release state, but rather in a 'development' state. I tried to compile the code as it looked by the time of 2.0.3/2 was released, but I couldn't get that kext to load in Snow Leopard 64-bit at all.
> Although this may be a simple fix that is all that we need to get it > working, and be stable, there is NO confirmation from Amit. As far as > I can tell, this is the only patch made public for MacFuse to work the > latest 64-bit Snow Leopard kernel. With so many people depending upon > MacFUSE to support their projects, you think there would be more > community involvement, or discussion.
We'll just have to work together as a community then, to fix any Snow Leopard issues and bring MacFUSE up to date. This could lead to a community-maintained fork of MacFUSE. I don't think forking the project is a very appealing idea... it'll just lead to confusion, but if the main project is stagnant I guess we have no choice.
I wish Amit would take some time to look at this, as he's the one with good knowledge about the code and any issues that might exist with 64-bit Snow Leopard. At least he could let someone else in on the project to take on leadership if he's not able to find time for MacFUSE anymore.
>> 64-bit kernel. > I don't think forking the project is a very appealing idea
Agreed.
> if the main project is stagnant
Whilst <http://code.google.com/p/macfuse/source/list> shows not many recent changes, let's not forget that experimental support for Snow Leopard was extraordinarily early -- December 2008.
> We'll just have to work together as a community then, to fix any > Snow Leopard issues
Distinguishing between 64-bit processing, bitness of the kernel, Snow Leopard Server and Snow Leopard:
* what's the rush to have MacFUSE (*user* space) working with a 64-bit kernel in a _server_ version of the OS that's not intended for end users?
I don't devalue any community work in progress, but I wonder whether development of MacFUSE should focus, currently, on issues that affect the more common version of 10.6.
(Issues that affect MacFUSE on 10.6 Server in 64-bit kernel mode may take a sideline. Assuming that it will be some time before there exist enough everyday drivers etc. to make a 64-bit kernel practical for the masses using ordinary Snow Leopard.)
Graham Perrin wrote: >> We'll just have to work together as a community then, to fix any >> Snow Leopard issues
> Distinguishing between 64-bit processing, bitness of the kernel, Snow > Leopard Server and Snow Leopard:
> * what's the rush to have MacFUSE (*user* space) working with a 64-bit > kernel in a > _server_ version of the OS that's not intended for end users?
Whether or not it's intended for end users, the 64-bit kernel does work for end users (even on non-server Snow Leopard), and a lot of users are running the 64-bit version of the kernel, whether they should or not. (I don't think they should, but they obviously have a different opinion.)
They don't consider MacFUSE and associated file systems to completely support Snow Leopard if it can only run on one kernel flavor out of two. I get these complaints daily for NTFS-3G.
> I don't devalue any community work in progress, but I wonder whether > development of MacFUSE should focus, currently, on issues that affect > the more common version of 10.6.
That is more important, agreed. However, there doesn't seem to be many issues when running the 32-bit kernel, afaik.
> (Issues that affect MacFUSE on 10.6 Server in 64-bit kernel mode may > take a sideline. Assuming that it will be some time before there exist > enough everyday drivers etc. to make a 64-bit kernel practical for the > masses using ordinary Snow Leopard.)
> Is my view of things too simplistic?
I think this is more than a single issue that needs to be fixed. The real issue is that a lot of projects have come to depend completely on MacFUSE, which inself seems to depend more or less on one person, Amit. It seems that today the entire MacFUSE based ecosystem sort of rests on his shoulders, which makes it all very vulnerable. While this approach works for experimental software in a development phase, MacFUSE has matured to the point where it's in use by many independent projects, some commerical and some not, many striving to deliver quality software that works on the latest platforms.
If the main MacFUSE project isn't progressing, then each project using MacFUSE could of course try to fix any issues that exist, but a coordinated community effort would in that case be preferable, to avoid that each project ships its own locally modified version of MacFUSE (imagine the nightmare). For the main project, my opinion is that the group involved in developing/maintaining MacFUSE should be broadened, or the project could eventually die out.
I think you can agree with me that it is a problem that we are sitting here today, not knowing if or when MacFUSE will be updated to deal with the issues that apparently do exist. A public statement or announcement regarding future plans for the project would be much appreciated.
I'd like to thank Amit for all the amazing effort he has put into this. He really opened a whole new horizon of possibilities for Mac file systems. I could easily understand if he's not willing to continue working in his spare time just to satisfy grumpy file system developers. :) The problem is that I do now know how to plan for the future, and I think more developers than myself could agree.
Discussion subject changed to "MacFUSE ecosystem, support and infrastructure (was: Darwin Kernel Version 10.0.0: root:xnu-1456.1.25~1/RELEASE_X 86_64)" by Graham Perrin
> and a lot of users are running the 64-bit version of the kernel
Beyond the bounds of what's officially supported by Apple?
(This is interesting. I always expect a minority to push the boundaries but if people are pushing the 64-bit kernel boundary en masse, then there are implications beyond MacFUSE.)
> They don't consider MacFUSE and associated file systems to > completely support Snow Leopard if it can only run on one kernel > flavor out of two. I get these complaints daily for NTFS-3G.
Unfortunate that people voice their wishes as complaints ;) but if the wishes are frequent/many then yes: let's have (at least) a clear roadmap so that people who are waiting can have an idea of what's ahead.
> there doesn't seem to be many issues when running the 32-bit kernel, > afaik.
This is very good. I have the same impression.
> I think this is more than a single issue that needs to be fixed. The > real issue is that a lot of projects have come to depend completely > on MacFUSE, which inself seems to depend more or less on one person, > Amit. It seems that today the entire MacFUSE based ecosystem sort of > rests on his shoulders, which makes it all very vulnerable.
I don't sense vulnerability based on anyone's shoulders. Instead, I might describe the past few months as:
* a natural lull (with happily few issues for users of the 32-bit kernel)
* coinciding with broadened expectations of MacFUSE capabilities in supported and (now) unsupported environments.
> While this approach works for experimental software in a development > phase, MacFUSE has matured to the point where it's in use by many > independent projects, some commerical and some not, many striving to > deliver quality software that works on the latest platforms.
> If the main MacFUSE project isn't progressing, then each project > using MacFUSE could of course try to fix any issues that exist, but > a coordinated community effort would in that case be preferable,
+1 to co-ordinated community effort.
My main concern is that the infrastructure for issues etc. (currently Google Groups) is far from ideal. Much of what's in this Group can not be found. More on this in a separate topic.
> my opinion is that the group involved in developing/maintaining > MacFUSE should be broadened
+1 but before actively broadening things, let's have (at least) a top- knotch and communities-friendly way of receiving and resolving/ rejecting issues.
> A public statement or announcement regarding future plans for the > project would be much appreciated.
+1 as above.
> I'd like to thank Amit for all the amazing effort he has put into > this.
+100
> He really opened a whole new horizon of possibilities for Mac file > systems. I could easily understand if he's not willing to continue > working in his spare time just to satisfy grumpy file system > developers. :)
Grumpy? I don't think so. All you developers (I'm watching from the sidelines) seem to be a very civil bunch, certainly more so in/around MacFUSE than in other areas in which I dabble :)
I would like to use MacFuse with 64-bit kernel, but I have no idea how
to apply these patches. Maybe someone could post some sort of step by
step instructions here? Thanks.
> > I would like to use MacFuse with 64-bit kernel, but I have no idea how
> > to apply these patches. Maybe someone could post some sort of step by
> > step instructions here? Thanks.
> I made a package for those who don't know how to compile MacFUSE.
> Disclaimer: I'm not a MacFUSE developer so I don't guarantee anything.
> This package is provided as-is without any warranty! If it makes your
> computer explode, DON'T BLAME ME! You have been warned.
> I compiled it on my MacBook running MacOS X 10.6 and Xcode 3.2, git
> revision c537453b7be9e63eab9c8caa84ef2a064396f485 (you can fetch the
> code from my macfuse repository on github.com/wereHamster). This is
> the command that I used:
> ./macfuse_buildtool.sh -c Release -p 10.5 -t smalldist -d
> If you want to build the package yourself, clone my macfuse repository
> on github, cd into core/ and run the above command.
> tom
That worked just brilliantly :) Thanks for that. Now let's hope
there's going to be some sort of official release with some known
problems like this one, fixed.
I also applied the patches but I have some stability problems. I can
browse the share without problems, but when I open a file with
textmate, sometimes the Finder crashes. It happens quite often. Has
anyone experienced this problem too ?
<sebastiaan.swink...@googlemail.com> wrote:
> On Sep 11, 1:23 pm, Tomas Carnecky <tomas.carne...@gmail.com> wrote:
> > On Sep 11, 2009, at 12:39 PM, corvo wrote:
> > > I would like to use MacFuse with 64-bit kernel, but I have no idea how
> > > to apply these patches. Maybe someone could post some sort of step by
> > > step instructions here? Thanks.
> > I made a package for those who don't know how to compile MacFUSE.
> > Disclaimer: I'm not a MacFUSE developer so I don't guarantee anything.
> > This package is provided as-is without any warranty! If it makes your
> > computer explode, DON'T BLAME ME! You have been warned.
> > I compiled it on my MacBook running MacOS X 10.6 and Xcode 3.2, git
> > revision c537453b7be9e63eab9c8caa84ef2a064396f485 (you can fetch the
> > code from my macfuse repository on github.com/wereHamster). This is
> > the command that I used:
> > ./macfuse_buildtool.sh -c Release -p 10.5 -t smalldist -d
> > If you want to build the package yourself, clone my macfuse repository
> > on github, cd into core/ and run the above command.
> > tom
> That worked just brilliantly :) Thanks for that. Now let's hope
> there's going to be some sort of official release with some known
> problems like this one, fixed.
Ossama wrote:
> I also applied the patches but I have some stability problems. I can
> browse the share without problems, but when I open a file with
> textmate, sometimes the Finder crashes. It happens quite often. Has
> anyone experienced this problem too ?
> Thank you by advance for your replies.
> On 12 sep, 10:27, Sebastiaan Swinkels
> <sebastiaan.swink...@googlemail.com> wrote:
>> On Sep 11, 1:23 pm, Tomas Carnecky <tomas.carne...@gmail.com> wrote:
>>> On Sep 11, 2009, at 12:39 PM, corvo wrote:
>>>> I would like to use MacFuse with 64-bit kernel, but I have no idea how
>>>> to apply these patches. Maybe someone could post some sort of step by
>>>> step instructions here? Thanks.
>>> I made a package for those who don't know how to compile MacFUSE.
>>> Disclaimer: I'm not a MacFUSE developer so I don't guarantee anything.
>>> This package is provided as-is without any warranty! If it makes your
>>> computer explode, DON'T BLAME ME! You have been warned.
>>> I compiled it on my MacBook running MacOS X 10.6 and Xcode 3.2, git
>>> revision c537453b7be9e63eab9c8caa84ef2a064396f485 (you can fetch the
>>> code from my macfuse repository on github.com/wereHamster). This is
>>> the command that I used:
>>> ./macfuse_buildtool.sh -c Release -p 10.5 -t smalldist -d
>>> The package is available here:http://static.caurea.org/MacFUSE/MacFUSE-2.1.7.dmg >>> If you want to build the package yourself, clone my macfuse repository
>>> on github, cd into core/ and run the above command.
>>> tom
>> That worked just brilliantly :) Thanks for that. Now let's hope
>> there's going to be some sort of official release with some known
>> problems like this one, fixed.
-- Erich Neuwirth, University of Vienna
Faculty of Computer Science
Computer Supported Didactics Working Group
Visit our SunSITE at http://sunsite.univie.ac.at Phone: +43-1-4277-39464 Fax: +43-1-4277-39459
> Creating (as root, with sudo)
> /etc/fstab
> with an entrty like
> LABEL=MyExternalDisk none ntfs rw
> makes this ntfs disk accessible for read and write.
> No guarantees, but so far it has worked for me.
> Can anybody comment on this?
> Ossama wrote:
> > I also applied the patches but I have some stability problems. I can
> > browse the share without problems, but when I open a file with
> > textmate, sometimes the Finder crashes. It happens quite often. Has
> > anyone experienced this problem too ?
> > Thank you by advance for your replies.
> > On 12 sep, 10:27, Sebastiaan Swinkels
> > <sebastiaan.swink...@googlemail.com> wrote:
> >> On Sep 11, 1:23 pm, Tomas Carnecky <tomas.carne...@gmail.com> wrote:
> >>> On Sep 11, 2009, at 12:39 PM, corvo wrote:
> >>>> I would like to use MacFuse with 64-bit kernel, but I have no idea how
> >>>> to apply these patches. Maybe someone could post some sort of step by
> >>>> step instructions here? Thanks.
> >>> I made a package for those who don't know how to compile MacFUSE.
> >>> Disclaimer: I'm not a MacFUSE developer so I don't guarantee anything.
> >>> This package is provided as-is without any warranty! If it makes your
> >>> computer explode, DON'T BLAME ME! You have been warned.
> >>> I compiled it on my MacBook running MacOS X 10.6 and Xcode 3.2, git
> >>> revision c537453b7be9e63eab9c8caa84ef2a064396f485 (you can fetch the
> >>> code from my macfuse repository on github.com/wereHamster). This is
> >>> the command that I used:
> >>> ./macfuse_buildtool.sh -c Release -p 10.5 -t smalldist -d
> >>> The package is available here:http://static.caurea.org/MacFUSE/MacFUSE-2.1.7.dmg > >>> If you want to build the package yourself, clone my macfuse repository
> >>> on github, cd into core/ and run the above command.
> >>> tom
> >> That worked just brilliantly :) Thanks for that. Now let's hope
> >> there's going to be some sort of official release with some known
> >> problems like this one, fixed.
> --
> Erich Neuwirth, University of Vienna
> Faculty of Computer Science
> Computer Supported Didactics Working Group
> Visit our SunSITE athttp://sunsite.univie.ac.at > Phone: +43-1-4277-39464 Fax: +43-1-4277-39459
On Sep 15, 2:07 pm, Erich Neuwirth <erich.neuwi...@univie.ac.at>
wrote:
> when I open a file with textmate, sometimes the Finder crashes.
Maybe best to start a new topic with relevant details including
version numbers etc., and whether the crash occurs when you (a) use
Finder to open the TextMate file, or (b) use the File menu of TextMate
to open a file that's located within Finder. The .crash file may be
useful.
Also, a report of a crash of Finder could be cross-posted to Apple.
On Sep 15, 2:23 pm, Ossama <ossama.har...@gmail.com> wrote:
> The problems I experienced are with sshfs and macfusion.
Discussion subject changed to "MacFUSE ecosystem, support and infrastructure (was: Darwin Kernel Version 10.0.0: root:xnu-1456.1.25~1/RELEASE_X 86_64)" by 陈永仁
> > I would like to use MacFuse with 64-bit kernel, but I have no idea how
> > to apply these patches. Maybe someone could post some sort of step by
> > step instructions here? Thanks.
> I made a package for those who don't know how to compile MacFUSE.
> Disclaimer: I'm not a MacFUSE developer so I don't guarantee anything.
> This package is provided as-is without any warranty! If it makes your
> computer explode, DON'T BLAME ME! You have been warned.
> I compiled it on my MacBook running MacOS X 10.6 and Xcode 3.2, git
> revision c537453b7be9e63eab9c8caa84ef2a064396f485 (you can fetch the
> code from my macfuse repository on github.com/wereHamster). This is
> the command that I used:
> ./macfuse_buildtool.sh -c Release -p 10.5 -t smalldist -d
On Sep 11, 7:23 pm, Tomas Carnecky <tomas.carne...@gmail.com> wrote:
> I compiled it on my MacBook running MacOS X 10.6 and Xcode 3.2, git
> revision c537453b7be9e63eab9c8caa84ef2a064396f485 (you can fetch the
> code from my macfuse repository on github.com/wereHamster). This is
> the command that I used:
> ./macfuse_buildtool.sh -c Release -p 10.5 -t smalldist -d
Worked like a charm here on 10.6.2/Xcode 3.2.1, thanks a lot!
The code for the 64-bit MacFUSE kernel extension does not exist in the
tree. If you simply recompile
it (by commenting out the #ifdef guards, as the earlier poster did and
as you seem to be doing), it'll load under K64 and might even appear
to work. But at best, you'll get a kernel panic, and at worst, you'll
get data corruption. If you use it for anything realistic, it will not
work.
Please stick to booting the 32-bit kernel for now if you need to use
MacFUSE. Do not confuse the "64-bit kernel extension" with "64-bit
MacFUSE". Whether the kernel is 32-bit or 64-bit, you can use the 64-
bit MacFUSE libraries and therefore, write/use 64-bit MacFUSE file
systems.
Amit
On Nov 10, 1:09 pm, Christian Bogus <cku...@gmail.com> wrote:
> On Sep 11, 7:23 pm, Tomas Carnecky <tomas.carne...@gmail.com> wrote:
> > I compiled it on my MacBook running MacOS X 10.6 and Xcode 3.2, git
> > revision c537453b7be9e63eab9c8caa84ef2a064396f485 (you can fetch the
> > code from my macfuse repository on github.com/wereHamster). This is
> > the command that I used:
> > ./macfuse_buildtool.sh -c Release -p 10.5 -t smalldist -d
> Worked like a charm here on 10.6.2/Xcode 3.2.1, thanks a lot!
