Hi all,
We have worked some more on the 64-bit locking and would like some
feedback on the following build:
http://www.tuxera.com/mac/macfuse-core-10.5-2.1.9.dmg
(Despite the label it only works on 10.6 at the moment.)
This solution should be a lot more proper than the one previously
published. This build has a lot of debug code and will flood your
'dmesg' buffer with locking-related log messages. This is useful since
if you would experience any file system lockups, you can report the
contents of the dmesg buffer to this mailing list (if you manage to
retrieve it).
You can test it on the 32-bit kernel as well, as the same locking
solution is enabled for both kernel flavors.
This build should be much more suited for a shared environment.
Regards,
- Erik
Dave Carlton skrev 2010-10-18 17.14:
Jeff, I agree, putting it up on GitHub would be a good idea. I am about ready
to start my new project which involves MacFUSE and would like to see it there.
You can count on extensive testing on my part once I get going. Used to run the
Open Firmware department at Apple and know how to test and report :)
On Oct 18, 2010, at 07:12 , Jeff Mancuso wrote:
For what it's worth, I'd strongly recommend against hosting this build
anywhere public until it has gone through a bit more testing. Like
Erik mention, it's not designed to work well in a shared-driver
environment. This would be a pretty poor solution to integrate into
the public MacFUSE line. It's also very beta and has known bugs that
can lead to deadlock in somewhat rare situations.
Drawing on experience here at ExpanDrive, we had many users install
the non-threadsafe "unofficial" 64 bit DMG, with all sorts of
problems. It was a decidedly "bad idea" - but nobody liked to hear
that what seemed to run well, was actually rather unsafe and would
eventually lead to problems.
Until the developers [tuxera, mostly] get this a little farther along
and we can all agree on a solution to either namespace the driver to
individual projects [like tuxera] or to have a better locking
mechanism, hosting these files publicly for anybody to download
probably isn't prudent. Anyone who wants to run it to help develop/
test will almost certainly have the dev chain installed, and it's easy
enough to build.
That being said, I do think moving this project to Github is a pretty
good idea. I have the "macfuse" account on github and am happy to
bring the project there, or as a sub-project of ExpanDrive [since we
use it fairly extensively :)]
-Jeff
ExpanDrive, Inc.
On Oct 18, 3:22 am, Graham Perrin<[email protected]> wrote:
On Sep 30 2009, 2:51 am, Amit Singh<[email protected]> wrote:
I've recompiled the preference pane to include a 64-bit version.
download it from the "files" section of this group:
http://groups.google.com/group/macfuse/files
Currently at<http://groups.google.com/group/macfuse/files>:
you won't be able to upload new content
So: where should we host new files?
FWIW I have seen at least one other group shifting to GitHub.
--
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.
--
_________________________________________________________________
| Erik Larsson
| File System Developer
| Tuxera Inc. Fax: +358-98-565-7002
| Bulevardi 2-4 A, 7th floor Email: [email protected]
| 00120 Helsinki, Finland http://tuxera.com
--
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.
