The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] System Economics (was is Linux "officially branded UNIX")
Date: Wed, 15 Mar 2017 16:08:04 -0400	[thread overview]
Message-ID: <CAC20D2PjPSgwUOiDHS3msSx5sjb2YU4JJ-H1WmtpYr3bzAzrTQ@mail.gmail.com> (raw)
In-Reply-To: <20170315192815.GA15120@naleco.com>

BTW Josh, I am trying to be respectful here.  I suspect you are tad younger
I am and your early introduction into UNIX was on the WINTEL platform, not
on the DEC systems like mine.  So, if I'm going to make a guess you were
not in a position when you were introduced to be able to get access to the
sources.

So in your experience the UNIX source were closed to you personally (and
many others).  I get that.   But it does not change the fact it, there were
available and there open and were not a secret.   Which was very different
from many of "closed" systems (says Cisco, or much of the other
infrastructure) of the day.  They always have been.  Even System V.

It was quite easy to get source if you were willing (and could pay).   I'm
not suggesting that it was easy for you could and I understand that
frustration.  I personally would not have been able to pay for the
licenses, but I was being employed by firms that could and valued my
abilities, so they did.  This was also true for many educational
institutions.

Sun and DEC actually were quite liberal with their source licenses, because
AT&T had been.  They had to be also - because their customer required it.

The point is there is a difference between "open" and "free."   There are a
lot of things that are open and we can look at but not touch or have the
wearwithall to modify.  But that does not change their openness - we can
still (and do) learn from them.

Linus and many of us learned because UNIX (the ideas) and the basic
implementations were open.  We talked about them, they were well specified.
  We wrote application that relied on those ideas, APIs etc.   And Linus,
Andy Tannenbaum and Plaguer before them reimplemented those ideas and
created clones.   *Unix was and is "open" and the implementations were and
are available.*   The problem for many is the price to look at the
implementations - that I grant. And for many, for some of those
implementations, can be high.  But it does not make them "closed."

The effect may seem that way to you, but it was not and is not the same.
All, I'm asking you to say, is that traditional UNIX implementations such
as System V were not "Free and Open," unlike Linux some of the other Unix
clones.  And that make all the difference.

They were and still are open.

On Wed, Mar 15, 2017 at 3:28 PM, Josh Good <pepe at naleco.com> wrote:

> On 2017 Mar 14, 21:11, Clem Cole wrote:
> >
> > My point is that you (and many others)  equate "open" and "free" - I ask
> > you to please not make that error.   Open means we can talk about it and
> > share it, see it.  Which is exactly what we did "back in the day".  But
> as
> > people pointed out you had to pay AT&T to be a member of the UNIX club if
> > you were commercial, although any University type could be apart for
> free.
>
> What UNIX for PC in the '90s had the option to buy a source code license
> for that specific version, so that PC hackers could write drivers for
> their hardware and tune the kernel internals to their liking, or be able
> to fix themselves a bug in the serial port driver, etc.?
>
> Certainly not OpenServer, not UnixWare nor SCO Xenix. Did DELL Unix
> offered a payware source code license for their product? I'm not aware
> of such.
>
> From System V onwards, UNIX became closed source in what matters, that
> is, the version running on your hardware and the version with the drivers
> you are using (unless you were an employee at IBM, DEC, HP or SUN running
> propietary hardware and happened to be in the right group).
>
> It is obvious to me that RMS's GNU movement was aimed at solving that
> very problem. And if that was a problem, then the "UNIX openness" you
> talk about does not seem to have been very practical at all. At least,
> it was totally useless to PC hackers, like Linus Torvalds - he had to
> write his own UNIX, because he was not able to get any UNIX source code
> he could readily compile and run on his i386.
>
> --
> Josh Good
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170315/32eff3db/attachment.html>


  parent reply	other threads:[~2017-03-15 20:08 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
2017-03-15 20:08       ` Clem Cole [this message]
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=CAC20D2PjPSgwUOiDHS3msSx5sjb2YU4JJ-H1WmtpYr3bzAzrTQ@mail.gmail.com \
    --to=clemc@ccc.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).