From: "David Leimbach" <leimy2k@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] naive 9vx/fossil question
Date: Wed, 2 Jul 2008 10:49:37 -0700 [thread overview]
Message-ID: <3e1162e60807021049gd4d48f1h8b17fcfa9a83c0c@mail.gmail.com> (raw)
In-Reply-To: <20080702172816.GA3703@secousse.ipgp.jussieu.fr>
[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]
9vx is capable of communication over a unix domain socket, so it should work
with p9p programs.
That said, you *should* be able to access resources from 9vx via any p9p
supported platform.
If you just want to transfer files, why not just use the #Z device in 9vx
though to mount the host system's FS?
Works great here.
"bind '#Z/host/system/path' somewhere/in/Plan9"
etc.
On Wed, Jul 2, 2008 at 10:28 AM, <lejatorn@gmail.com> wrote:
> Hello,
>
> I have a plan9/linux dual boot on my machine. Is there any way I can
> access (i.e: read and/or write) the fossil partition of my plan9
> install from 9vx on linux?
> Actually, is there any way at all I can access that partition from
> linux?
>
> I'm just looking for an easy way to transfer some of the conf files I
> have on the native plan9 to the 9vx on linux. Of course I can boot
> plan9 and mount one of my linux ext partitions and use it as a transfer
> partition but that's not very convenient.
>
> With 9vx I can now easily try some plan9-ish stuff without losing the
> ability to ... listen to music on my computer. ☺
> Yes, as silly as it sounds, it's actually a big win for me and I'm
> really glad 9vx exists just for that. So, thanks a lot Russ.
>
> Cheers,
> Mathieu.
>
>
>
[-- Attachment #2: Type: text/html, Size: 1577 bytes --]
next prev parent reply other threads:[~2008-07-02 17:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 17:28 lejatorn
2008-07-02 17:49 ` David Leimbach [this message]
2008-07-02 17:54 ` Anthony Martin
2008-07-02 18:03 ` Russ Cox
2008-07-02 22:35 ` lejatorn
2008-07-02 23:06 ` lejatorn
2008-07-02 23:12 ` erik quanstrom
2008-07-03 8:49 ` lejatorn
2008-07-03 11:06 ` Russ Cox
2008-07-03 15:34 ` lejatorn
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=3e1162e60807021049gd4d48f1h8b17fcfa9a83c0c@mail.gmail.com \
--to=leimy2k@gmail.com \
--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).