From: "Rubén Berenguel" <ruben@mostlymaths.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Accessing Mac OS Extended drives
Date: Sat, 8 Mar 2014 13:59:51 +0100 [thread overview]
Message-ID: <CAHk2O6q6areFxRKeTcF6ZPC_Lr4WSfc4W_gGymuUnBreW+8Bmw@mail.gmail.com> (raw)
In-Reply-To: <b69fa91ee74c11329a0373e34a520afa@mikro.quanstro.net>
[-- Attachment #1: Type: text/plain, Size: 1200 bytes --]
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 <quanstro@quanstro.net>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
>
>
[-- Attachment #2: Type: text/html, Size: 1700 bytes --]
next prev parent reply other threads:[~2014-03-08 12:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 8:44 Rubén Berenguel
2014-03-07 8:54 ` Sergey Zhilkin
2014-03-07 9:00 ` Gorka Guardiola
2014-03-07 9:47 ` David Swasey
2014-03-07 16:49 ` erik quanstrom
2014-03-08 12:30 ` Rubén Berenguel
2014-03-08 12:35 ` erik quanstrom
2014-03-08 12:59 ` Rubén Berenguel [this message]
2014-03-08 13:03 ` erik quanstrom
2014-03-08 14:08 ` Rubén Berenguel
2014-03-08 14:18 ` erik quanstrom
2014-03-08 15:16 ` Jeff Sickel
2014-03-08 17:53 ` Rubén Berenguel
2014-03-08 17:58 ` erik quanstrom
2014-03-08 18:11 ` Rubén Berenguel
2014-03-09 16:42 ` erik quanstrom
2014-03-08 18:27 ` Steve Simon
2014-03-09 8:39 ` Rubén Berenguel
2014-03-09 17:52 ` Jeff Sickel
2014-03-09 18:05 ` Rubén Berenguel
2014-03-10 2:01 ` blstuart
2014-03-10 2:08 ` erik quanstrom
2014-03-10 2:19 ` blstuart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHk2O6q6areFxRKeTcF6ZPC_Lr4WSfc4W_gGymuUnBreW+8Bmw@mail.gmail.com \
--to=ruben@mostlymaths.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).