Re: [9fans] Accessing Mac OS Extended drives

["Rubén Berenguel" <ruben@mostlymaths.net>]

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

Thanks all for the prompt replies. I add a few answers:

@Sergey: The point is using an existing HFS+ with ~500 GB of data. Moving
all the data and reformatting is way beyond the time commitment I wanted to
give to this, which was only the moderately convenient remote access. I
know how to use disk/fdisk and disk/prep, more or less, to create
partitions compatible with P9, this is not a problem.

@David: Using Plan9ports is a weird way to manage a HFS+ formatted device:
linux and Mac OS have HFS+ support, BSD has partial support, all built-ins.

I have caved in and just used a (far smaller) FAT device.

A mildly related question, though (I'm getting a little lost among
namespaces):

How can I (I guess it's possible?) exportfs an external drive? As far as I
understand, 9import (or in general, import) will connect to my remote
machine with the current username, in its own namespace, and as such an
external drive (say, usbfat: mounted) won't be there (since the mountpoint
won't be in the remotely connected namespace.) Is there any workaround for
this? I can drawterm and cp, but I'd like to simplify it and just 9import
via fuse and move files when needed.

Thanks,

Ruben

On Fri, Mar 7, 2014 at 5:49 PM, erik quanstrom <quanstro@quanstro.net>wrote:

> On Fri Mar  7 04:01:31 EST 2014, paurea@gmail.com wrote:
> > This would probably make for a nice GSoC project (even if, for the
> purposes of
> > the project is a read only, without all the bells and whistles,
> > version of HFS+). It is documented for example here:
> > http://dubeiko.com/development/FileSystems/HFSPLUS/tn1150.html#BTrees
>
> keep in mind that hfs+ support will be a little difficult without gpt
> partitions.  so gpt support might be even more useful.
>
> - erik
>
>

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