From mboxrd@z Thu Jan  1 00:00:00 1970
Message-Id: <200006151619.MAA20956@cse.psu.edu>
From: "Russ Cox" <rsc@plan9.bell-labs.com>
Date: Thu, 15 Jun 2000 12:18:55 -0400
To: stevemw@mindspring.com, 9fans@cse.psu.edu
Subject: Re: [9fans] File/cpu servers..?
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: be5453aa-eac8-11e9-9e20-41e7f4b1d025

  I'm also awaiting a concise set of instructions for installing a
  self-contained terminal/CPU-server/disk-server. It would be ideal if
  WORM backups, DNS, and the whole set of Plan9 services could be
  functional on one system. I think people at the Labs are working on
  getting out a basic document.

I plan to have such an addendum to the
Getting Started document late tonight.

For now, I will note the following.
The intended use of the system is to have
separate machines for everything -- a file
server, a cpu server, and terminals.
That said, it is probably unrealistic
to expect single users to dedicate a
minimum of three machines to get a Plan 9
network going.

There are ways to have a combination
cpu/auth/file server via kfs, and
in fact I configured one last night and
am using a terminal booted from it at
the moment.  You currently can't have
WORM-style backups on kfs, though.  For
that you need to run a dedicated file
server, as the WORM management code
lives in the standalone file server code
only.

  I did this, replaced /386/9pcdisk with the resulting file, and also
  ran gzip 9pcdisk to standard out (naming the results 9pcdisk.gz) for a

You'll get an even smaller 9pcdisk.gz if you
do mk 'CONF=pcdisk' 9pcdisk.gz, which strips
the binary en route to gzip.  mk 'CONF=pcdisk' install
installs the kernels too, although as discussed
earlier, you will want to comment out the line
in /sys/src/9/pc/mkfile that tries to toss them
over to "dinar".

Russ