The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: pechter@gmail.com (William Pechter)
Subject: [TUHS] System Economics (was is Linux "officially branded UNIX")
Date: Wed, 15 Mar 2017 20:05:38 -0400	[thread overview]
Message-ID: <cb872a98-9cb9-699e-037e-bcccaf8d350e@gmail.com> (raw)
In-Reply-To: <20170315235525.GC15120@naleco.com>

Josh Good wrote:
> On 2017 Mar 15, 15:45, Clem Cole wrote:
>> SVR4 (aka UnixWare) was available for source  - the problem is many people
>> did like the price to see it.   It was $100K.  But the source was available
>> it was open and many, many of people with PC and had access to it, wrote
>> drivers for it etc.  There were books published about it.  It was hardly
>> secret.
> Nobody says UNIX source code was "secret". It just was not open after
> UNIX began to be directly sold by AT&T post Bell-breakage.
>
> If UNIX source codeHa was "open" at $100K, then Windows NT source code can
> also be seen as open if you have enough money to buy Microsoft.
Having worked at a minicomputer company (Concurrent Computer
Corporation) back in the 87 days... I can say that
there was no way I could access the SysV sources without being an
approved developer or support engineer.
I was the IT Systems Administrator with the company managing their Xelos
SysVR2 systems in the MIS department
and I had no access.

When I found a serious bug they looked at it.  Reproduced it.  Reported
it to AT&T who checked the will not fix box on
their ticket and closed the bug.  The problem was that cron would malloc
memory until it couldn't get any more and core
dump.  This  stopped automatic backups and jobs from being scheduled
reliably and was critical to my operations.

The fix was I had to write a script to kill -0 cron with a sleep... and
if the job was no longer there  -- restart cron.

AT&T support basically said "Get a machine that implements demand paged
virtual memory and it won't happen."

Pretty sad.  I had worked for DEC and other places that would've fixed
the code for a customer.  Especially an OEM.

Concurrent had pretty much put Unix on the back burner until they bought
Masscomp.   Their only OS they were pushing
at the time was OS/32.  Xelos was a pretty decent SVR5.2 port -- the
next version even had ksh in it.

I wanted to get a 3280 and see how Xelos on it compared with something
equivalent on a VAX 8650.

Bill
Pechter at gmail.com



  reply	other threads:[~2017-03-16  0:05 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-14 14:43 Clem Cole
2017-03-14 15:38 ` Larry McVoy
2017-03-14 15:51   ` Arthur Krewat
2017-03-14 15:56     ` Larry McVoy
2017-03-14 15:57     ` Michael Kjörling
2017-03-14 16:20       ` Arthur Krewat
2017-03-14 18:06         ` Jason Stevens
2017-03-14 18:31           ` Clem Cole
2017-03-14 18:59             ` Jason Stevens
2017-03-14 18:20         ` Clem Cole
2017-03-14 19:48           ` Arthur Krewat
2017-03-15 14:32             ` Michael Kjörling
2017-03-15 15:36               ` Arthur Krewat
     [not found]                 ` <58c9623b.law1Aw2ufj3DFNA1%schily@schily.net>
2017-03-15 15:54                   ` Arthur Krewat
2017-03-15 15:59                 ` Larry McVoy
2017-03-15 17:43                   ` Warner Losh
2017-03-15 19:02                     ` Larry McVoy
2017-03-15 19:14                       ` Warner Losh
2017-03-14 18:41         ` Warner Losh
2017-03-17 18:16           ` [TUHS] GNU vs BSD before the lawsuit and before Linux Tony Finch
2017-03-17 18:52             ` Jeremy C. Reed
2017-03-19  7:18               ` arnold
2017-03-19  9:05                 ` Wesley Parish
2017-03-19 18:37                 ` Warner Losh
2017-03-17 19:54             ` Ron Natalie
2017-03-14 18:18   ` [TUHS] System Economics (was is Linux "officially branded UNIX") Clem Cole
2017-03-14 16:20 ` tfb
2017-03-14 22:45 ` Josh Good
2017-03-15  1:11   ` Clem Cole
2017-03-15  7:55     ` arnold
2017-03-15 19:28     ` Josh Good
2017-03-15 19:35       ` Clem Cole
2017-03-15 20:26         ` Ron Natalie
2017-03-15 23:22           ` 'Josh Good'
2017-03-15 19:45       ` Clem Cole
2017-03-15 20:27         ` Larry McVoy
2017-03-15 20:48           ` Clem Cole
2017-03-15 23:46           ` Arthur Krewat
2017-03-16  0:45             ` Clem Cole
2017-03-16  1:27               ` Steve Nickolas
2017-03-16  3:09                 ` Ron Natalie
2017-03-16  3:18                   ` Charles Anthony
2017-03-16  3:36               ` Dan Cross
2017-03-16  4:08                 ` arnold
2017-03-16 12:51               ` Arthur Krewat
2017-03-16 13:18                 ` William Pechter
2017-03-17 21:20               ` Josh Good
2017-03-16 15:42           ` Chet Ramey
2017-03-16 17:29             ` William Pechter
2017-03-15 23:55         ` Josh Good
2017-03-16  0:05           ` William Pechter [this message]
2017-03-15 20:08       ` Clem Cole
2017-03-16  0:46         ` Wesley Parish
2017-03-16  0:52           ` Clem Cole
2017-03-16 19:47       ` Dave Horsfall
2017-03-17  2:16         ` Jason Stevens
2017-03-17 15:55           ` Warner Losh
2017-03-17 21:11           ` Dave Horsfall
2017-03-14 19:01 Noel Chiappa
2017-03-14 20:05 Clem Cole
2017-03-14 20:16 ` Arthur Krewat
2017-03-14 20:54 ` Dan Cross
2017-03-14 21:19   ` Clem Cole
2017-03-16 15:40 Norman Wilson
2017-03-16 17:26 ` William Pechter
2017-03-16 18:45   ` Clem Cole
2017-03-16 22:17 ` Dave Horsfall

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=cb872a98-9cb9-699e-037e-bcccaf8d350e@gmail.com \
    --to=pechter@gmail.com \
    /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).