Jump to content

MacFUSE 0.1 Released


Colonel

For months now, many of use have been happily running Mac OS X along side of Windows on our Intel Macs. But we've always face the problem with Mac OS X not being able to write over to our Windows drive. Well, just a few days ago Amit Singh of Mac OS X Internals and current Google employee have found a way to solve this problem. MacFUSE's Google Code site gives us more in depth details.

"MacFUSE implements a mechanism that makes it possible to implement a fully functional file system in a user-space program on Mac OS X (10.4 and above). It aims to be API-compliant with the FUSE (Filesystem in USErspace) mechanism that originated on Linux. Therefore, many existing FUSE file systems become readily usable on Mac OS X. The core of MacFUSE is in a dynamically loadable kernel extension.

 

How FUSE-compliant is MacFUSE? Well, enough so that many popular FUSE file systems can be easily compiled and work on Mac OS X--often out of the box. Examples of file systems that work have been tested (to varying degrees) include sshfs, ntfs-3g (read/write NTFS), ftpfs (read/write FTP), wdfs (WebDAV), cryptofs, encfs, bindfs, unionfs, beaglefs (yes, including the entire Beagle paraphernalia), and so on."

A dream come true for dual booters everywhere, has finally become a reality.


User Feedback

Recommended Comments



Hi,

 

I followed the instructions and installed these 2 files. It worked 2 days, and even mounted the partition as r/w after reboots, without other efforts, but after these 2 days, it mounts as network drives, but read-only (Zero KB, Zero KB free in finder). Have anybody this strange behaviour? Did you find a fix for this problem? Thanks in advance :whistle:

Edited by XanthraX
Link to comment
Share on other sites

Hi,

 

I followed the instructions and installed these 2 files. It worked 2 days, and even mounted the partition as r/w after reboots, without other efforts, but after these 2 days, it mounts as network drives, but read-only (Zero KB, Zero KB free in finder). Have anybody this strange behaviour? Did you find a fix for this problem? Thanks in advance ;)

update your ntfs-3g driver to the latest

it should fix it

http://chucker.mystfans.com/opensource/ntf...20070116-r4.dmg

Link to comment
Share on other sites

Hi,

 

I followed the instructions and installed these 2 files. It worked 2 days, and even mounted the partition as r/w after reboots, without other efforts, but after these 2 days, it mounts as network drives, but read-only (Zero KB, Zero KB free in finder). Have anybody this strange behaviour? Did you find a fix for this problem? Thanks in advance :D

 

The zero sizes are because of a "paranoid kext" http://code.google.com/p/macfuse/wiki/MACFUSE_AND_THE_FINDER

Link to comment
Share on other sites

Ummm... JaS 10.4.8 Intel AMD SSE2 SSE3 release... it shows my NTFS drive as a mounted disk in OS X. I can read and write to it. I didn't realize you needed FUSE for this?

 

I can't tell you if it was ever working before because I've never had an IDE NTFS drive, only SATA until now.

Link to comment
Share on other sites

You can solve the zero-size/zero-available issue by opening Terminal and typing:

killall Finder

 

It's case-sensitive. Once you do this, the correct sizes should show up on the disks.

Link to comment
Share on other sites

Not sure how a) others are able to see the NTFS drive as a normal disk, mine looks like a network share, and b ) how ethereal is able to write NTFS natively (there's gotta be something going on there).

That being said, I have access to my windows partition. Has anyone confirmed write reliability? Obviously it's a beta product, but when dealing with data i would expect taht integrity is concern #1. What about speed? What if I ran a parallels virtual disk of of my ntfs drive?

Many questions, I guess i'll get on testing out some of them myself and post some experiences.

IAN

Edited by Mr.Sticky
Link to comment
Share on other sites

Write seems reliable.

You can change the icon to something other than a network share.

1. Get info on the item with the icon you wish to apply to your NTFS drive.

2. Click on the icon in the top left corner, and hit command-C.

3. Get info on your NTFS drive.

4. Click on the icon in the top left corner, and hit command-V.

 

Ta da, a new icon.

Link to comment
Share on other sites

Yeah, i'm not so concerned about the icon, the problem is that I dont normally have my network drives on my desktop (because I have a bunch of shares attached). Is there a way around that? Does everyone's actually attach as a network type device?

Link to comment
Share on other sites

I haven't kept up with this since it first came out, but it worked great for a day and now it says zero [k] free. I tried updating it about a month ago and it still doesn't work right.

 

Goodtime

Link to comment
Share on other sites



×
×
  • Create New...