Hi all,=A0

can Plan9 access a USB disk = formatted with HFS plus (i.e. the Mac OS Extended (& journaled) file sy= stem?

The part about USB is just because it happen= s to be an USB drive, but basically I don't know how to mount the /dev/= sdD.D/data. Of course, dossrv can't do it (already tried).

Thanks,

Ruben=A0

Hello !=C2=A0

Plan9 can't mount HFS= or HFS+ filesystems (no fileservers :) ) but you can use USB disk by forma= tting it to a supported filesystem (fossil(4), kfs(4)). I think, that your = Mac USB disk is labaled as UUID, and UUID is unsopported. Please read prep(= 8) for how to lebel and format disks. :)

Hi all,=C2=A0

can Plan9 access a USB disk formatted with HFS plus (i.e. the Mac OS = Extended (& journaled) file system?

The part about USB is just because it happens to be an = USB drive, but basically I don't know how to mount the /dev/sdD.D/data.= Of course, dossrv can't do it (already tried).

Thanks,

Ruben=C2=A0

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 commit= ment I wanted to give to this, which was only the moderately convenient rem= ote access. I know how to use disk/fdisk and disk/prep, more or less, to cr= eate partitions compatible with P9, this is not a problem.

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

I have caved in and just used a (far smaller) FA= T 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 underst= and, 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 b= e 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,=A0<= /div>

Ruben<= /div>

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

On Fri Mar =A07 04:01:31 EST= 2014, paurea@gmail.com wrote:
> This would probably make for a nice GSoC project (even if, for the pur= poses 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/HF= SPLUS/tn1150.html#BTrees

keep in mind that hfs+ support will be a little difficult without gpt=
partitions. =A0so gpt support might be even more useful.

- erik

--001a113a9c02493f9304f4178b0d-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Sat, 8 Mar 2014 07:35:12 -0500 To: 9fans@9fans.net Message-ID: In-Reply-To: References: <656c0f615d55ce5f418af43c59d01fe1@mikro.quanstro.net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Accessing Mac OS Extended drives Topicbox-Message-UUID: c53dc10a-ead8-11e9-9d60-3106f5b1d025 > 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. needs to be in export's namespace. easiest way to do this is to start it on boot and add to /lib/namespace. - erik From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <656c0f615d55ce5f418af43c59d01fe1@mikro.quanstro.net> From: =?ISO-8859-1?Q?Rub=E9n_Berenguel?= Date: Sat, 8 Mar 2014 13:59:51 +0100 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a11c11ed868976104f417f39c Subject: Re: [9fans] Accessing Mac OS Extended drives Topicbox-Message-UUID: c541fee6-ead8-11e9-9d60-3106f5b1d025 --001a11c11ed868976104f417f39c Content-Type: text/plain; charset=ISO-8859-1 Thanks for the quick reply. Where is exactly the proper point to consider it as "started on boot"? I really don't know how the Plan9 boot process follows along (I guess "something" loads /lib/profile which in turn loads /rc/bin/termrc, but I'm not even sure about this ordering), and so far the documentation for this is a little... too twisty. Ruben On Sat, Mar 8, 2014 at 1:35 PM, erik quanstrom wrote: > > 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. > > needs to be in export's namespace. easiest way to do this is to start it > on > boot and add to /lib/namespace. > > - erik > > --001a11c11ed868976104f417f39c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Thanks for the quick reply. Where is exactly the proper po= int to consider it as "started on boot"? I really don't know = how the Plan9 boot process follows along (I guess "something" loa= ds /lib/profile which in turn loads /rc/bin/termrc, but I'm not even su= re about this ordering), and so far the documentation for this is a little.= .. too twisty.

Ruben

On Sat, Mar 8, 2014 at 1:35 PM, erik quanstrom <qua= nstro@quanstro.net> wrote:

> A mildly related questi= on, 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<= br> > machine with the current username, in its own namespace, and as such a= n
> external drive (say, usbfat: mounted) won't be there (since the mo= untpoint
> won't be in the remotely connected namespace.) Is there any workar= ound for
> this? I can drawterm and cp, but I'd like to simplify it and just = 9import
> via fuse and move files when needed.

needs to be in export's namespace. =A0easiest way to do this is t= o start it on
boot and add to /lib/namespace.

- erik

--001a11c11ed868976104f417f39c-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Sat, 8 Mar 2014 08:03:11 -0500 To: 9fans@9fans.net Message-ID: <5ede24014831aca7fb8032baa529a2f8@mikro.quanstro.net> In-Reply-To: References: <656c0f615d55ce5f418af43c59d01fe1@mikro.quanstro.net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Accessing Mac OS Extended drives Topicbox-Message-UUID: c5475e36-ead8-11e9-9d60-3106f5b1d025 On Sat Mar 8 08:01:20 EST 2014, ruben@mostlymaths.net wrote: > Thanks for the quick reply. Where is exactly the proper point to consider > it as "started on boot"? I really don't know how the Plan9 boot process > follows along (I guess "something" loads /lib/profile which in turn loads > /rc/bin/termrc, but I'm not even sure about this ordering), and so far the > documentation for this is a little... too twisty. it doesn't really have to be started at boot time, newns() will ignore errors. so as long as the relevant srv files are available before newns() is called, you can access them. - erik From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <5ede24014831aca7fb8032baa529a2f8@mikro.quanstro.net> References: <656c0f615d55ce5f418af43c59d01fe1@mikro.quanstro.net> <5ede24014831aca7fb8032baa529a2f8@mikro.quanstro.net> From: =?ISO-8859-1?Q?Rub=E9n_Berenguel?= Date: Sat, 8 Mar 2014 15:08:45 +0100 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a11c3e70ace0de304f418e9b3 Subject: Re: [9fans] Accessing Mac OS Extended drives Topicbox-Message-UUID: c555e0c8-ead8-11e9-9d60-3106f5b1d025 --001a11c3e70ace0de304f418e9b3 Content-Type: text/plain; charset=ISO-8859-1 Sorry to be bothersome again, but still can't figure it out. I need /srv/dos available in /lib/namespace, so I can mount the external drive before anything else is done on the system, but to do so I need to execute dossrv, and in a namespace file I can't execute anything beside bind/mount and related commands (at least according to namespace(6)) Ruben On Sat, Mar 8, 2014 at 2:03 PM, erik quanstrom wrote: > On Sat Mar 8 08:01:20 EST 2014, ruben@mostlymaths.net wrote: > > > Thanks for the quick reply. Where is exactly the proper point to consider > > it as "started on boot"? I really don't know how the Plan9 boot process > > follows along (I guess "something" loads /lib/profile which in turn loads > > /rc/bin/termrc, but I'm not even sure about this ordering), and so far > the > > documentation for this is a little... too twisty. > > it doesn't really have to be started at boot time, newns() will ignore > errors. > so as long as the relevant srv files are available before newns() is > called, > you can access them. > > - erik > > --001a11c3e70ace0de304f418e9b3 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Sorry to be bothersome again, but still can't figure i= t out. I need /srv/dos available in /lib/namespace, so I can mount the exte= rnal drive before anything else is done on the system, but to do so I need = to execute dossrv, and in a namespace file I can't execute anything bes= ide bind/mount and related commands (at least according to namespace(6))

Ruben

On Sat, Mar 8, 2014 at 2:03 PM, erik quanstrom <quanstro@quanstro.net> wrote:

On Sat Mar =A08 08:01:20 EST= 2014, ruben@mostlymaths.net w= rote:

> Thanks for the quick reply. Where is exactly the proper point to consi= der
> it as "started on boot"? I really don't know how the Pla= n9 boot process
> follows along (I guess "something" loads /lib/profile which = in turn loads
> /rc/bin/termrc, but I'm not even sure about this ordering), and so= far the
> documentation for this is a little... too twisty.

it doesn't really have to be started at boot time, newns() will i= gnore errors.
so as long as the relevant srv files are available before newns() is called= ,
you can access them.

- erik

The thing is, I don't want access to HFS+ from my Plan= 9 host. I want my Plan9 host to serve a HFS+ drive. Access is required, but= it's not the end goal.

On Sat, Mar 8, 2014 at 4:16 PM, Jeff Sickel <jas@corpus-callosum.c= om> wrote:

I agree with Gorka, this would be a good GSoC project.

But there are other ways to mount the device. =A0Have you tried u9fs (h= ttp://plan9.bell-labs.com/magic/man2html/4/u9fs)? =A0Or drawterm from a= Mac with the drive connected? =A0Or running Inferno hosted on the Mac and = exporting the volume?

Any of these would make the HFSX file system available to your Plan 9 host.=

-jas

I don't seem to have=A0=E8fs, which is weird (the Raspberry Pi distri= bution is 9atom, isn't it?.) At least, its source is not in sys/src/cmd= . I pulled changes 3 or 4 days ago.

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.=A0<= div>

I finally managed to exportfs the drive, I'm not sur= e if due to a combination of things in /lib/namespace or the -t flag in lis= ten1 did the trick, or the combination of the two. I was happy for around 3= 0 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.

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

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

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

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

1) mac9p =97 ask fsb for more = details (or google mac9p and find his hg repo or the github = fork)

2) cifs =97 read the aquarela man = page

3) 9pfuse =97 I=92ve not tested this with = recent fuse versions

4) nfs =97 this shouldn=92t 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).

On Mar 9, = 2014, at 3:39 AM, Rub=E9n 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

Hi Jeff, thanks:

On Sun, Mar 9, 2014 at 6:52 PM, Jeff Sickel <jas@corpus-callosum.com> wrote:

Rub=E9n,=

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’v= e had trouble getting Plan 9’s NFS server to serve up bits that OSX c= lient can actually use. Someone else’s milage may vary. S= ame goes for CIFS.

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

&nbs= p;1) mac9p — ask fsb for more details (or google mac9p and find his h= g repo or the github fork)

Hmmm... The use at your own risk doe= sn't sound really encouraging... I'm wary of kexts, even installing= fuse from brew was a little over the edge. If it wasn't because I have= used sshfs in the past and found it almost indispensable in most cases, I = would have skipped it.

2) cifs — read the aquarela man page
<= /blockquote>

Did yesterday, wasn't convinced and thought nfs would be bet= ter...

3) 9pfuse — I’ve not tested this with recent f= use versions

The pipe essential= ly breaks after ~30 seconds with the latest version of osxfuse, unknown rea= son (no matter how many d's I add to 9import). I can read the remote dr= ive during this time, access and create files. But when it dies, it dies &q= uot;hard" so I need to remove the tmp/ns.file in Mac OS, eject the fus= e volume, etc. Painful, and anyway, not that useful.

4) nfs — this shouldn’t be painful, bu= t it is

That's the impression I got from the m= an pages :(

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

Drawterm works like a charm (some day I will compile and try= the iOS version...), and I can use it with cp without any problems, everyt= hing works as expected. But I wanted a solution that was relatively straigh= tforward so that we (me and my SO) could access the drive without needing (= relatively) complicated steps.

I don't know what I'll do from this point on, s= ince this was a good "reasoned" way to justify an always on devic= e with Plan9... Now I think it will be a device with Raspbian or Plan9 depe= nding on what I want to do... And it will probably mean Raspbian more often= than not (so I can use APL.)

Ruben

-jas
=

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

Thanks Steve. In any c= ase, 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 se= conds, 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> w= rote:

> I want my
> Plan9 host to serve a HFS+ drive.

If you want to serve files (rather than a block device) from pl= an9 to
a mac then plan9 has an nfs server and, two cifs servers available.

-Steve