Yes, I am aware of the darling-dmg project - but I was talking about interoperability, and there is nothing that beats hooking up genuine Apple code somehow. AFAIK darling-dmg is an independent HFS+ implementation, just like the linux kernel's. This is important for dual-boot systems where journals written by one OS would be applied and played back by another OS, in an unclean shutdown. (and especially subsequent auto-reboot into the other OS). For the purpose of journal inter-operability, read-only implementation is also of little use. I wasn't talking about using fuse just for the sake of it - I was talking about using genuine Apple HFS+ related code somehow (and "via fuse" being one such route). If you could hook up apple's HFS+ kernel modules directly to the linux kernel by some kind of on-the-fly binary API translation, that would be most interesting; other than that, source-level hooks is the next best thing. -------------------------------------------- On Wed, 5/2/14, A. C. Censi <accensi@xxxxxxxxx> wrote: Subject: Re: [PATCH v2 00/15] hfsplus: introduce journal replay functionality To: htl10@xxxxxxxxxxxxxxxxxxxxx Date: Wednesday, 5 February, 2014, 14:11 On Wed, Feb 5, 2014 at 11:16 AM, Hin-Tak Leung <htl10@xxxxxxxxxxxxxxxxxxxxx> wrote: About the fuse-based HFS+ project Have a look at https://github.com/LubosD/darling-dmg darling-dmgThis project allows ordinary users to directly mount OS X disk images under Linux via FUSE. Supported file types DMG (UDIF) files containing an Apple Disk Image.Apple Disk Images containing an HFS+/HFSX file system. HFS+/HFSX file systems (incl. file systems embedded within HFS).As you can see, the list is recursive. That means darling-dmg, can mount DMG files or unpacked DMG files or a single partition carved out of the latter. Read only access only. See also the Issues page. -- A. C. Censi accensi [em] gmail [ponto] com accensi [em] montreal [ponto] com [ponto] br -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html