[comp.sys.sequent] ptx conversion

stevedc@syma.sussex.ac.uk (Stephen Carter) (04/30/91)

From sc@admin.sussex.ac.uk Tue Apr 30 14:15:51 1991
From: Steve Carter <sc@uk.ac.sussex.admin>
Date: Tue, 30 Apr 91 14:17:34 +0100
Message-Id: <8143.9104301317@admin.sussex.ac.uk>
To: stevedc@uk.ac.sussex.syma
Status: R


			ptx
			---

We are just about to take delivery of an S2000 with ptx.  We are already
running Dynix V3.0.17 on our S27.  Having two machines will enable us to
keep our users on the S27 and load our work onto an 'empty' ptx machine.

Does anyone have any words of wisdom for us before we start the hard
slog?


Stephen Carter, Systems Manager, The Administration,
The University of Sussex, Falmer, Brighton BN1 9RH, UK
Tel: +44 273 678203  Fax: +44 273 678335     JANET: stevedc@uk.ac.sussex.syma
EARN/BITNET  : stevedc@syma.sussex.ac.uk      UUCP: stevedc@syma.uucp
ARPA/INTERNET: stevedc%syma.sussex.ac.uk@nsfnet-relay.ac.uk 


BTW The machine is not the machine from which I'm posting.  I very
kindly am able to guest on it.  Thanks Williandy.

 

dsm@prism.gatech.EDU (Daniel McGurl) (05/01/91)

In article <4972@syma.sussex.ac.uk> stevedc@syma.sussex.ac.uk (Stephen Carter) writes:

>Does anyone have any words of wisdom for us before we start the hard
>slog?

Yes, don't expect much system stuff to transfer.

Here are the big problems that we've had with PTX.

1)  No socket library:  PTX uses streams instead of sockets, so anything using
    sockets has to be modified.

2)  The machine supports symlinks, but doesn't have a non-POSIX lstat.
    Thus, if you have a home-grown backup program that isn't posix, you
    may well have to re-write it.

3)  THe software is very immature.

-- 
Danny McGurl                               "How straightforward the game
Office of Information Technology and       when all its rules are respected."
Information and Computer Science Major at:
Georgia Institute of Technology                     ARPA: dsm@prism.gatech.edu

jarrell@vtserf.cc.vt.edu (Ron Jarrell) (05/03/91)

Out of sheer curiosity, is there a new marketing name for the S2000
series?  I mean, first there was the Balance, then the Symmetry, 
is the S2000 a different name?
-- 
Ron Jarrell
Virginia Tech Computing Center
jarrell@vtserf.cc.vt.edu

holzman@sequent.com (05/04/91)

In article <1689@vtserf.cc.vt.edu> jarrell@vtserf.cc.vt.edu (Ron Jarrell) writes:

>Out of sheer curiosity, is there a new marketing name for the S2000
>series?  I mean, first there was the Balance, then the Symmetry, 
>is the S2000 a different name?

The S2000 or Symmetry/2000 is our new Intel 486-based product family. This 
gives the industry its first Open Mainframe system (S2000/700), plus powerful
new entry-level (S2000/40) and mid-range systems (S2000/200 & S2000/400) for
workgroup and departmental computing. 


-- 
Alan Holzman				Internet = holzman@sequent.com 
Sequent Computer Systems Inc.		UUCP = ...!sequent!holzman 
Operating Systems Product Manager	AOL = AHOLZMAN 
(503) 578-5184				C$S = 76665,3406 
(503) 578-7562 (FAX)

csg@pyramid.pyramid.com (Carl S. Gutekunst) (05/04/91)

>The S2000 or Symmetry/2000 is our new Intel 486-based product family. This 
>gives the industry its first Open Mainframe system (S2000/700)....

Gee, Al, you write the same silly marketing nonsense working for Sequent as
you did working for Pyramid.

(Open Mainframe? Out of i486 chips? OK, I suppose that's not any sillier than
Pyramid calling its 9000 systems a "mini mainframe." So what do you call an
Amdahl running UTS? Chopped germanium?)

:-)

<csg>