From mboxrd@z Thu Jan  1 00:00:00 1970
From: presotto@plan9.bell-labs.com
Message-Id: <200006201451.KAA23603@cse.psu.edu>
Date: Tue, 20 Jun 2000 10:51:37 -0400
To: bill@triangle.cs.uofs.edu, 9fans@cse.psu.edu
Subject: Re: [9fans] Running Version 2 along with Version 3
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="upas-tegbslaiawsyrhiqopjqbyjtjl"
Topicbox-Message-UUID: c5ea8efe-eac8-11e9-9e20-41e7f4b1d025

This is a multi-part message in MIME format.
--upas-tegbslaiawsyrhiqopjqbyjtjl
Content-Disposition: inline
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

I was living with a Nextstation running along my newer machines until
quite recently.

So far, the authentication is the same, though we intend to change
that in the not too distant future.  Ditto the 9 protocol.

The cpu command uses a different protocol than the old systems.  You
can recompile the old cpu command on the new systems (call it ocpu
or something) and use it to talk to the old systems.  The new cpu
command uses a different port so they can both exist on the
same machine though you will have to edit ocpu.c to change the service
name to something else.

Graphics are radicly different so you can't cpu from one to the other
and use any of the graphic commands like rio, sam, etc.

Sam -r will work though since the protocol between the halves is
unchanged.

Of course, you could just port the new system to the Sun hardware.
It shouldn't be that difficult with both the new and old in hand.
We didn't because we don't really use suns, most of our old processors
are mips.


--upas-tegbslaiawsyrhiqopjqbyjtjl
Content-Type: message/rfc822
Content-Disposition: inline

Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Tue Jun 20 10:41:09 EDT 2000
Received: from cse.psu.edu ([130.203.3.50]) by plan9; Tue Jun 20 10:41:08 EDT 2000
Received: from localhost (majordom@localhost)
	by cse.psu.edu (8.8.8/8.8.8) with SMTP id KAA22728;
	Tue, 20 Jun 2000 10:25:49 -0400 (EDT)
Received: by claven.cse.psu.edu (bulk_mailer v1.5); Tue, 20 Jun 2000 10:25:36 -0400
Received: (from majordom@localhost)
	by cse.psu.edu (8.8.8/8.8.8) id KAA22689
	for 9fans-outgoing; Tue, 20 Jun 2000 10:25:31 -0400 (EDT)
X-Authentication-Warning: claven.cse.psu.edu: majordom set sender to owner-9fans using -f
Received: from mercury.bath.ac.uk (mercury.bath.ac.uk [138.38.32.81])
	by cse.psu.edu (8.8.8/8.8.8) with ESMTP id KAA22685
	for <9fans@cse.psu.edu>; Tue, 20 Jun 2000 10:25:26 -0400 (EDT)
Received: from news by mercury.bath.ac.uk with local (Exim 3.12 #1)
	id 134OaP-0002uQ-00
	for 9fans@cse.psu.edu; Tue, 20 Jun 2000 15:01:05 +0100
Received: from GATEWAY by bath.ac.uk with netnews
	for 9fans@cse.psu.edu (9fans@cse.psu.edu)
To: 9fans@cse.psu.edu
Date: Tue, 20 Jun 2000 13:58:06 GMT
From: Bill Gunshannon <bill@triangle.cs.uofs.edu>
Message-ID: <8ins9g$29pn$1@info.cs.uofs.edu>
Organization: University of Scranton
Subject: [9fans] Running Version 2 along with Version 3
Sender: owner-9fans@cse.psu.edu
Reply-To: 9fans@cse.psu.edu
Precedence: bulk

It was posted that Sparc support was not rolled into the new Plan9.
Is it possible that Version 2 systems will function along side of
Version 3 systems??  I have a whole bunch of SparcStation 1's that
made up the majority of my previous Plan9 network.  I was hoping to
continue the use of these as CPU Pool machines and Terminals.

bill

--
Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolves
bill@cs.scranton.edu     |  and a sheep voting on what's for dinner.
University of Scranton   |
Scranton, Pennsylvania   |         #include <std.disclaimer.h>
--upas-tegbslaiawsyrhiqopjqbyjtjl--