From: "Russ Cox" <rsc@swtch.com>
To: 9fans@9fans.net
Subject: Re: [9fans] 9vx and local file systems
Date: Fri, 18 Jul 2008 22:37:46 -0400 [thread overview]
Message-ID: <20080719023506.97E031E8C22@holo.morphisms.net> (raw)
In-Reply-To: <8d0d960c72b3cb1c2dd913c00ec87511@quanstro.net>
>> Well, I use vx32 as a terminal for both lguest and remote machines. No
>> real need for venfi/fossil. For edit, I import; to build etc. I cpu in
>> an acme window so i get the error stuff.
>
> what's the advantage over drawterm in this configuration?
In the case you quote, you'd have many of the advantages
of a standalone Plan 9 terminal, like local handling of graphics
and the mouse, the ability to connect to many machines
simultaneously, the ability to withstand those machines
rebooting, and so on. It depends a lot on what you're doing.
Here's another example.
For about seven years I had the luxury of running Plan 9
as my day-to-day system, but I couldn't easily keep doing
that and work with the people around me at MIT; around
2003, I gave it up and switched to FreeBSD and Linux.
(You'll note that's when the p9p CVS logs begin.)
I haven't booted an actual Plan 9 terminal in a couple of years.
Since then, I've had the smaller luxury of running Plan 9
as a venti server, now atop some nice hardware we bought
from Coraid. The Coraid box has a tiny, slow IDE flash disk
for a root file system, fine for holding a few binaries but
not really usable as a general file system. To build the binaries,
I have a second Plan 9 server with a bigger, faster root disk.
I've used drawterm to connect to it, edit and compile venti,
and submit patches. As I look forward to finishing at MIT,
I can't leave Plan 9 boxes for others to deal with. A few months
ago, I converted the main venti server (the Coraid hw) to run
FreeBSD, which is what all our other servers run. That leaves
the second Plan 9 server, which I still use for the occasional
drawterm session to submit a patch to sources. But when I
leave MIT, I can't reasonably keep using that machine as my
own personal server. It'll have to be a group server running
FreeBSD.
The advantage of 9vx over drawterm, for me, is that 9vx
doesn't require a cpu server.
9vx is how I'm going to deal with not having my own
personal Plan 9 cpu server to drawterm into. Having a local
Plan 9 install, stored right in my non-Plan 9 home directory,
lets me keep using and occasionally contributing to Plan 9
without having to maintain and house a server.
I haven't spent quite enough time setting up a comfortable
9vx that I could stop using drawterm today, but maybe
tomorrow.
Russ
next prev parent reply other threads:[~2008-07-19 2:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <071820081822.3544.4880DF75000734D900000DD822218675169B0A02D2089B>
2008-07-18 19:00 ` erik quanstrom
2008-07-18 19:50 ` Roman V. Shaposhnik
2008-07-18 20:20 ` erik quanstrom
2008-07-18 20:28 ` ron minnich
2008-07-19 1:31 ` erik quanstrom
2008-07-19 2:10 ` ron minnich
2008-07-19 2:37 ` Russ Cox [this message]
2008-07-21 13:26 ` [9fans] (no subject) kokamoto
2008-07-21 14:45 ` a
2008-07-21 15:17 ` [9fans] 9vx vs drawterm Tim Wiess
2008-07-21 18:32 ` [9fans] Sam Benjamin Huntsman
2008-07-18 20:31 ` [9fans] 9vx and local file systems Russ Cox
2008-07-18 21:55 ` Francisco J Ballesteros
2008-07-18 20:35 ` Russ Cox
2008-07-18 18:22 Brian L. Stuart
2008-07-18 20:39 ` Russ Cox
2008-07-18 20:55 ` Charles Forsyth
2008-07-18 20:50 ` Sape Mullender
2008-07-18 20:55 ` Charles Forsyth
2008-07-18 22:10 ` Brian L. Stuart
2008-07-20 7:53 ` Russ Cox
2008-07-23 14:40 ` Brian L. Stuart
2008-07-23 17:51 ` Russ Cox
2008-07-23 18:50 ` Brian L. Stuart
2008-07-24 19:14 ` Brian L. Stuart
[not found] ` <1cb06bb5ba32c2070a940af01f4d91c3@plan9.bell-labs.com>
2008-07-24 19:24 ` Brian L. Stuart
2008-07-24 19:26 ` David Leimbach
2008-07-24 23:23 ` Francisco J Ballesteros
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=20080719023506.97E031E8C22@holo.morphisms.net \
--to=rsc@swtch.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).