From: "Hongzheng Wang" <wanghz@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] [9fans ] What's the best access method to Plan9 from Linux
Date: Fri, 8 Feb 2008 18:35:10 +0800 [thread overview]
Message-ID: <b954b2060802080235g6812ab56qf74ea010a5ae6350@mail.gmail.com> (raw)
In-Reply-To: <599f06db0802080214j78e6cd57ha04ae1e5b584ee1d@mail.gmail.com>
On Feb 8, 2008 6:14 PM, Gorka Guardiola <paurea@gmail.com> wrote:
It sounds really interesting. I will have a try. Thanks.
> I think the simplest way would be:
>
> Configure your Plan 9 box as a CPU server which should be described
> here
> http://plan9.bell-labs.com/wiki/plan9/Configuring_a_Standalone_CPU_Server/index.html
> and use drawterm to connect to it:
> http://swtch.com/drawterm/
> from drawterm you can access your local fs in /mnt/term so you can
> copy things back
> and forth also.
> --
> - curiosity sKilled the cat
>
--
HZ
next prev parent reply other threads:[~2008-02-08 10:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 9:13 Hongzheng Wang
2008-02-08 9:28 ` Uriel
2008-02-08 9:43 ` Lluís Batlle
2008-02-08 10:14 ` Gorka Guardiola
2008-02-08 10:35 ` Hongzheng Wang [this message]
2008-02-08 15:33 Brian L. Stuart
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=b954b2060802080235g6812ab56qf74ea010a5ae6350@mail.gmail.com \
--to=wanghz@gmail.com \
--cc=9fans@cse.psu.edu \
/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).