Re: [9fans] Accessing Mac OS Extended drives

[Jeff Sickel <jas@corpus-callosum.com>]

[-- Attachment #1: Type: text/plain, Size: 1942 bytes --]

Rubén, 

For better, or worse, nothing really serves HFS+ these days.  Apple’s transitioning from AFP to SMB2 when sharing files.  I can’t say I’m disappointed that AFP is finally going away.

Until someone writes an HFSX fs device support you won’t be able to mount a drive formatted under OSX.  You could mount a FAT device, within reason.

I’ve had trouble getting Plan 9’s NFS server to serve up bits that OSX client can actually use.  Someone else’s milage may vary.  Same goes for CIFS.

Now if you’re trying to exportfs to a Mac there are several levels of pain you can go through:

 1) mac9p — ask fsb for more details (or google mac9p and find his hg repo or the github fork)
 2) cifs — read the aquarela man page
 3) 9pfuse  — I’ve not tested this with recent fuse versions
 4) nfs — this shouldn’t be painful, but it is

But I usually find that connecting to my Plan 9 cpu servers through drawterm or Inferno tends to be the best bridge|least pain (though mac9p tends to be a really good option).

-jas

On Mar 9, 2014, at 3:39 AM, Rubén Berenguel <ruben@mostlymaths.net> wrote:

> Thanks Steve. In any case, I can't serve HFS+ serving files because P9 can't access them. But I could serve a FAT device. 
> 
> I finally managed to exportfs the drive, I'm not sure if due to a combination of things in /lib/namespace or the -t flag in listen1 did the trick, or the combination of the two. I was happy for around 30 seconds, which is the time 9pfuse (9import) took to issue a "broken pipe" on my terminal, killing the connection to my remote disk. Pretty fed up of setting up a remote drive by now.
> 
> 
> On Sat, Mar 8, 2014 at 7:27 PM, Steve Simon <steve@quintile.net> wrote:
> > I want my
> > Plan9 host to serve a HFS+ drive.
> 
> If you want to serve files (rather than  a block device) from plan9 to
> a mac then plan9 has an nfs server and, two cifs servers available.
> 
> -Steve
> 
> 


[-- Attachment #2: Type: text/html, Size: 2979 bytes --]