From: maht <maht-9fans@maht0x0r.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] plan9 on qemu and 9vx
Date: Fri, 12 Mar 2010 12:37:59 +0000 [thread overview]
Message-ID: <4B9A35A7.2000007@maht0x0r.net> (raw)
In-Reply-To: <138575261003120253t4eb3a9b6k4d5902288c8c8f3@mail.gmail.com>
On 12/03/2010 10:53, hugo rivera wrote:
> Hello,
> I have a Slackware installation running on my box. On top of it, I
> often use qemu to run plan9, but it's inconvenient to constantly keep
> track of the things I do there, like C programs, because many of them
> are also useful under Slackware (then I compile them under linux with
> p9p's 9c). So the approach I've taken is to run 9vx and invoke
> % aux/listen1 -tv tcp!192.168.1.2!12345 /bin/exportfs
> from there. Then, from plan9 inside qemu, I run
> % import -A tcp!192.168.1.1!12345 /usr/hugo /n/temp
> and then bind anything I want inside /n/temp to my namespace in plan9.
> That way I don't need to keep track of anything I do inside qemu.
> But the next step I want to take is to run just a terminal with qemu,
> probably using the plan9 iso image, and have 9vx as my fileserver. Do
> you know if this is even possible? I'm not sure it is since 9vx is not
> actually plan9. Can you offer me some hints on how to do it?
> Saludos a todos,
>
>
I use u9fs and run it on my Linux / BSD machines using tcpserver (though
inetd works too)
I run them with -a none :) but it's a private LAN. Auth does work but I
don't use it.
You can also run u9fs on the end of ssh, e.g.
tcpserver localhost 564 ssh remote u9fs -a none
see http://man.cat-v.org/plan_9/4/u9fs for more details
next prev parent reply other threads:[~2010-03-12 12:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 10:53 hugo rivera
2010-03-12 12:37 ` maht [this message]
2010-03-12 15:44 ` yy
2010-03-12 16:53 ` ron minnich
2010-03-12 17:02 ` hugo rivera
2010-03-12 18:48 ` ron minnich
2010-03-12 23:31 ` Tim Newsham
2010-03-13 14:02 ` hugo rivera
2010-03-13 18:09 ` ron minnich
2010-03-14 11:24 ` hugo rivera
2010-03-12 23:04 ` Gorka Guardiola
2010-03-12 23:10 ` ron minnich
2010-03-12 23:50 ` erik quanstrom
2010-03-13 1:29 ` Russ Cox
2010-03-13 2:11 ` erik quanstrom
2010-03-13 19:38 ` EBo
2010-03-13 21:00 ` ron minnich
2010-03-14 1:20 ` EBo
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=4B9A35A7.2000007@maht0x0r.net \
--to=maht-9fans@maht0x0r.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).