9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Drawterm or VMWare terminal?
Date: Thu, 27 Feb 2003 09:42:34 -0500	[thread overview]
Message-ID: <03c0815c70324a38dbb0748b39176d20@plan9.bell-labs.com> (raw)
In-Reply-To: <fi77a.7769$g77.61994124@news-text.cableinet.net>

It depends on the details of your network, and on
personal preferences.  If drawterm works well then
VMware might be overkill, but if it doesn't then
VMware might save you.  Drawterm requires a
lower-latency network to feel good than a real
Plan 9 terminal typically does, because drawterm
only displays graphics while a real Plan 9 terminal
runs at least rio and perhaps your other apps locally.

You need to recompile your kernel to get tcp support.
In the section that says


boot boot #S/sdC0/
	il
	local

you should change it to say


boot boot #S/sdC0/
	il
	tcp
	local

and then you can choose "tcp" as the boot method.
In addition to 567, you need to open port 564, which is
the 9fs tcp port.  You also need to make sure your kfs
is listening, with

	disk/kfscmd 'listen tcp!*!564'

Then you should be able to boot.

Another consideration is that using drawterm will
encrypt your sessions.  Using a terminal will encrypt
your cpu sessions but not your file system traffic.

Russ



  reply	other threads:[~2003-02-27 14:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-27  9:35 Robby
2003-02-27 14:42 ` Russ Cox [this message]
2003-02-27 14:49   ` Dan Cross
2003-02-27 14:54     ` Russ Cox
2003-02-27 15:11       ` Dan Cross
2003-02-27 15:19         ` Russ Cox
2003-02-27 15:49           ` Dan Cross
2003-02-27 15:57             ` rob pike, esq.
2003-02-27 15:59               ` Dan Cross
2003-02-27 16:04                 ` Boyd Roberts

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=03c0815c70324a38dbb0748b39176d20@plan9.bell-labs.com \
    --to=rsc@plan9.bell-labs.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).