Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!super.upenn.edu!dsl.cis.upenn.edu!neil
From: neil@dsl.cis.upenn.edu (Neil Radisch)
Newsgroups: comp.lang.c,comp.arch
Subject: Re: Was the 360 badly-designed?  (was Re: Compatibility with EBCDIC)
Message-ID: <1884@super.upenn.edu>
Date: Thu, 27-Aug-87 15:10:48 EDT
Article-I.D.: super.1884
Posted: Thu Aug 27 15:10:48 1987
Date-Received: Sat, 29-Aug-87 10:14:36 EDT
References: <1500@cullvax.UUCP>
Sender: news@super.upenn.edu
Reply-To: neil@dsl.cis.upenn.edu.UUCP (Neil Radisch)
Distribution: comp.lang.c
Organization: University of Pennsylvania
Lines: 21
Xref: mnetor comp.lang.c:3968 comp.arch:1983

>Eh?  Here we're arguing about hardware architecture, and this guy
>starts arguing OSs architecture.  Do you *really* mean '360', or do
>you really mean 'the software that's usually run on 360s'?  After all,
>you can get Un*x for 360s now, and it looks just about like any other
>Un*x.  (And if you went to the work, you could port OS/360 to the
>Vax!)
>
>yours for linguistic purity,
>
>Dale

Although technically true, in practice it just doesn't happen enough.
Vaxes mostly run Unix and VMS, 360's VM, Cybers NOS or KRONOS etc.
So from the point of view of a system user, the OS is representative
of the entire computer family architecture. Sure you could put
Unix on a Cyber but evey time I sit down to one, the damn thing
is running NOS or KRONOS (can you say useless).


-neil-
(Actually I just wanted to do some Cyber bashing)