From: blstuart@bellsouth.net
To: 9fans@9fans.net
Subject: Re: [9fans] Adventures of a home user
Date: Tue, 21 Apr 2009 17:03:16 -0500 [thread overview]
Message-ID: <e8c061e8db364e6e26b98b31592a93de@bellsouth.net> (raw)
In-Reply-To: <ea634cc80904210055h169fe038u828a82c57161b0ac@mail.gmail.com>
> On Mon, Apr 20, 2009 at 6:42 PM, Balwinder S Dheeman <bdheeman@gmail.com>wrote:
>
>> I don't who and why one referred you to try 9vx
>>
>
> Maybe because it's faster, and easy to install. It only took a few minutes
> to download it, unpack it, and start using it. It's an easy way to get
> acquainted with the Plan 9 environment, and to practice using it. Running
> Plan 9 in QEMU is awkward and slow, and my processor doesn't support an
> accelerator. I can see very well how 9vx might be useful for me, at some
> point.
One way it can be useful is as a replacement for drawterm.
It feels a little more like using a real plan9 terminal than
drawterm does. That's how I use it at home. I have a file/
auth/cpu server, and from my FreeBSD machine, I run 9vx
with the -b option. It's asks for the protocol, the fileserver
and the auth server IP addresses and then I get the same
prompt for username and password I'd get at a real terminal.
Plus, I get the ability to run Plan9 code either locally on
my terminal or I can cpu into the cpu server. Pretty much
as soon as I got my hands on 9vx, I stopped using drawterm
altogether.
BLS
next prev parent reply other threads:[~2009-04-21 22:03 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-19 1:01 Jim Habegger
2009-04-19 1:05 ` john
2009-04-19 1:08 ` erik quanstrom
2009-04-19 10:15 ` yy
2009-04-19 14:16 ` Jim Habegger
2009-04-19 14:34 ` erik quanstrom
2009-04-19 14:43 ` Anthony Sorace
2009-04-19 15:37 ` Jim Habegger
2009-04-20 10:42 ` Balwinder S Dheeman
2009-04-21 7:55 ` Jim Habegger
2009-04-21 22:03 ` blstuart [this message]
2009-04-20 5:01 ` Jim Habegger
2009-04-20 5:13 ` andrey mirtchovski
2009-04-20 5:38 ` André Günther
2009-04-20 5:22 ` Federico G. Benavento
2009-04-20 7:14 ` Jim Habegger
2009-04-21 3:38 ` Jim Habegger
2009-04-21 5:14 ` john
2009-04-21 7:05 ` Federico G. Benavento
2009-04-21 3:52 ` Jim Habegger
2009-04-21 3:55 ` Jim Habegger
2009-04-21 12:06 ` erik quanstrom
2009-04-21 22:13 ` blstuart
2009-04-21 6:02 ` Jim Habegger
2009-04-21 6:31 ` Anthony Sorace
2009-04-21 6:59 ` Jim Habegger
2009-04-21 9:10 ` Jim Habegger
2009-04-21 11:26 ` erik quanstrom
2009-04-21 15:26 ` john
2009-04-21 15:34 ` erik quanstrom
2009-04-21 20:01 ` Jim Habegger
2009-04-21 21:28 ` Karin Willers
2009-04-21 22:23 ` blstuart
2009-04-22 0:29 ` john
2009-04-22 1:07 ` Jim Habegger
2009-04-23 9:12 ` Jim Habegger
2009-04-23 10:23 ` Eris Discordia
2009-04-23 15:55 ` maht
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=e8c061e8db364e6e26b98b31592a93de@bellsouth.net \
--to=blstuart@bellsouth.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).