The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Lawrence Stewart <stewart@serissa.com>
To: Paul Winalski <paul.winalski@gmail.com>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Old mainframe I/O speed (was: core)
Date: Sun, 24 Jun 2018 10:41:42 -0400	[thread overview]
Message-ID: <07BD6DF6-66B3-4EF3-B3B0-F2E2EBB3A209@serissa.com> (raw)
In-Reply-To: <CABH=_VTOZbdzfXrYYbb13XG5EZTxXXYDTGUaWLPRrWYx5MBuzA@mail.gmail.com>



> On 2018, Jun 24, at 9:03 AM, Paul Winalski <paul.winalski@gmail.com> wrote:
> 
> On 6/23/18, Norman Wilson <norman@oclsc.org> wrote:
>> Ron Minnich:
>> 
>>  Jon Hall used to love telling the story of the VAX backplane with the
>> glue
>>  in the board slots, which clever customers managed to damage and have
>>  repaired with a non-glued-up backplane.
> 
> That was the VAXstation-11/RC.  Marketing wanted a VAXstation with
> fewer backplane slots that it could sell at a cheaper price.  Rather
> than manufacture a different board, they just filled the extra
> backplane slots with glue to render them unusable.  "RC" officially
> stood for "restricted configuration", but we in Engineering called it
> "resin caulked".
> 
> -Paul W.

Some customers of the 11/RC figured out how to buy the full backplane as “spare parts” which worked for a while.

Every industry with up-front R&D or capital costs has the problem that the marginal cost of goods is much lower than the average cost.  It happens to airlines, chip companies, system companies and especially commercial software companies.  Trying to introduce product differentiation is one solution. Glue or microcode NOPs or DRM licence unlock codes work, but they tend to damage your reputation.

-L

  reply	other threads:[~2018-06-24 14:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-24  3:14 Norman Wilson
2018-06-24 13:03 ` Paul Winalski
2018-06-24 14:41   ` Lawrence Stewart [this message]
2018-06-24 15:47     ` Arthur Krewat
  -- strict thread matches above, loose matches on Subject: below --
2018-06-24 18:49 Norman Wilson
2018-06-24 18:49 Norman Wilson
     [not found] <mailman.1.1529690481.3725.tuhs@minnie.tuhs.org>
2018-06-23 10:32 ` Johnny Billquist
2018-06-23 11:39   ` Clem cole
2018-06-24  7:50   ` Mutiny
2018-06-27 13:59     ` Clem Cole
2018-06-22 13:11 Noel Chiappa
2018-06-22 17:49 ` Erik E. Fair
2018-06-15 15:25 [TUHS] core Noel Chiappa
2018-06-15 23:05 ` Dave Horsfall
2018-06-15 23:22   ` Lyndon Nerenberg
2018-06-16  6:36     ` Dave Horsfall
2018-06-16 19:07       ` Clem Cole
2018-06-18  9:25         ` Tim Bradshaw
2018-06-19 20:45           ` Peter Jeremy
2018-06-19 22:55             ` David Arnold
2018-06-20  5:04               ` Peter Jeremy
2018-06-20  5:41                 ` Warner Losh
2018-06-20  8:10                   ` [TUHS] Old mainframe I/O speed (was: core) Greg 'groggy' Lehey
2018-06-20 16:33                     ` Paul Winalski
2018-06-21  3:05                       ` Peter Jeremy
2018-06-21 14:00                         ` Paul Winalski
2018-06-21 14:49                           ` Arrigo Triulzi
2018-06-21 20:39                             ` Paul Winalski
2018-06-22  5:32                               ` Erik E. Fair
2018-06-22 13:32                                 ` Clem Cole
2018-06-23  6:08                             ` Dave Horsfall
2018-06-23 17:02                               ` ron minnich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=07BD6DF6-66B3-4EF3-B3B0-F2E2EBB3A209@serissa.com \
    --to=stewart@serissa.com \
    --cc=paul.winalski@gmail.com \
    --cc=tuhs@tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).