home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.arch
- Path: sparky!uunet!nntp.telebit.com!phr
- From: phr@telebit.com (Paul Rubin)
- Subject: Re: How many PC's make an Amdahl mainframe
- In-Reply-To: apas611@chpc.utexas.edu's message of Thu, 28 Jan 93 22:25:37 GMT
- Message-ID: <PHR.93Jan28195629@napa.telebit.com>
- Sender: news@telebit.com
- Nntp-Posting-Host: napa
- Organization: Telebit Corporation; Sunnyvale, CA, USA
- References: <1993Jan26.225943.21955@enterprise.rdd.lmsc.lockheed.com>
- <1993@niktow.canisius.edu> <128R02pn34lx01@JUTS.ccc.amdahl.com>
- <1993Jan28.222537.15330@chpc.utexas.edu>
- Date: Fri, 29 Jan 1993 03:56:29 GMT
- Lines: 24
-
- In article <1993Jan28.222537.15330@chpc.utexas.edu> apas611@chpc.utexas.edu (David Boles) writes:
-
- It is Friday afternoon, 5:30 pm Central time and your system jocks notice
- a problem on your central system. This system _is_ your business (10Billion
- a year, lets say) and you can tolerate essentially _no_ downtime.
-
- Your sys jocks isolate the problem to a particular process, but don't know
- whether resetting will solve the problem. You call the company and they
- [go to great lengths to fix the problem]
-
- Suppose you have PC's:
- you call Microsoft (not even toll-free) and get told that the next upgrade
- might fix that...
-
- You have workstations:
-
- you call your Sun support group etc...
-
-
- You have PC's or workstations but run a system that you have source
- code for, like GNU or BSDI:
-
- Your system jocks fix the problem without needing to depend on
- the mercy of some vendor!
-