From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: matt@proweb.co.uk, 9fans@cse.psu.edu
Subject: Re: [9fans] planning an installation
Date: Sun, 9 Jul 2000 17:46:55 -0400 [thread overview]
Message-ID: <200007092146.RAA08961@smtp2.fas.harvard.edu> (raw)
I was hopnig to do a single computer installation but from reading through
the list archive I have half drawn the conclusion that this is not the way
to go. Plan9's distributed architecture is attractive on a network but am I
*forced* to have 3 machines dedicated to getting my first workstation going?
Not so. The installation process sets up a standalone machine.
If you expand to multiple machines, the recommended setup is
an auth server and a file server as machines separate from any
terminals. If you're strapped for machines or space, though,
this isn't always practical. It's possible to have one machine do
everything although the file service in particular is not as efficient
as using the standalone file server. But it's quite usable. In fact,
I'm using a terminal booted from such a wonder-machine
right now.
On the machine I installed on I couldn't get the network going. I did manage
to get it to respond to pings once but it has elluded me since. (on a
related note how do I ping out - i can't find a ping command anywhere!!)
It's called "ip/ping".
On the machine I installed on I couldn't get the network going. I did manage
to get it to respond to pings once but it has elluded me since. (on a
related note how do I ping out - i can't find a ping command anywhere!!)
netstat -i will print information about how your
network card is configured. That might be a good
place to start.
Russ
next reply other threads:[~2000-07-09 21:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-09 21:46 Russ Cox [this message]
2000-07-09 22:45 ` Matt
[not found] <200007100932.KAA10477@pw001.proweb.co.uk>
2000-07-10 18:55 ` Matt
-- strict thread matches above, loose matches on Subject: below --
2000-07-10 4:53 pip
2000-07-10 6:57 ` Matt
2000-07-09 21:13 Matt
2000-07-09 21:58 ` Kevin McQuiggin
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=200007092146.RAA08961@smtp2.fas.harvard.edu \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
--cc=matt@proweb.co.uk \
/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).