August 2008
November 2007
January 2007
macfuse - Google Code
by 5 othersMacFUSE 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 (File-system 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.
Besides making many existing FUSE file systems available on Mac OS X, MacFUSE opens up a whole new set of opportunities for Macintosh developers, who can now put intuitive and innovative interfaces around all kinds of information.
September 2006
TNPI - DIY .mac
by 7 othersRetain the useful features: Regardless of whether or not I renew my subscription, I want to retain the features I have found most useful (iDisk, iSync (between computers), iCal sharing, and Backup).
Enhance the useful features: Simply retaining the useful features would be an utter failure. The most value can be found in addressing the shortcomings of each feature. For iDisk, speed and disk space are the impediments to its usefulness. iSync already works quite well. iCal sharing works well but publish and subscribe updates are terribly slow. Backup is hamstrung by the iDisk space issue.
1
(8 marks)