The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: pepe@naleco.com (Pepe)
Subject: [TUHS] IANAL. Kimball has ruled
Date: Fri, 18 Jul 2008 00:30:02 +0200	[thread overview]
Message-ID: <20080717223001.GA28983@d600.naleco.com> (raw)
In-Reply-To: <20080717202215.GE7790@eng.sun.com>

On Thu, Jul 17, 2008 at 01:22:15PM -0700, Bryan Cantrill wrote:
> 
> > Sun needed desperately to find a way to stop losing money, and that
> > meant making themselves again desirable to the IT market. Sun mayor [sic]
> > rivals were (and are) Microsoft and Linux. Specially Linux, since more
> > Sun machines are being replaced by Linux than by Windows. So the Sun
> > strategy was two-fold: release an "opensource" Unix to "steal" the
> > grassroots support away from Linux, and give money to The SCO Group
> > so they could keep afloat their FUD campaign against Linux in the
> > Enterprise. If they could achieve these two goals with one swift move,
> > much better; and they did: the gave money to The SCO Group to buy a
> > bogus license to opensource Solaris.
> 
> Can we keep this kind of invective to a minimum?  As it happens, you're
> wrong in this particular case, but more generally it would be nice if
> we could try to stick to the history of Unix as code, and not Unix as
> endless trench warfare...

The history is made by people and their actions, people are not isolated
beings but they are social. Therefore, history is always about politics.

The code of Unix did evolve because of the politics they
creators/vendors were engaged with (I'm talking about political
economy). The actions which created and evolved Unix had political
goals, sometimes for academic gain, sometimes for commercial gain.

I don't think Unix as a phenomenon can be understood without
understanding it's politics.

You happen to have a different view on the political angle of Unix.
That's fine. You also don't hold a totally impartial stance on Unix
politics, as you are affiliated to one of the Unix parties. But I don't
think it is fair to try to suppress the political views one doesn't like,
or to try to suppress the political expression of history altogether..

It is as much "historical Unix" the political history of Unix, as it is
the code history of it.

-- 
Pepe
pepe at naleco.com




  reply	other threads:[~2008-07-17 22:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1871.1216314893.89381.tuhs@minnie.tuhs.org>
2008-07-17 19:55 ` Pepe
2008-07-17 20:22   ` Bryan Cantrill
2008-07-17 22:30     ` Pepe [this message]
2008-07-17 20:40   ` Boyd Lynn Gerber
2008-07-18 14:10   ` Jose R. Valverde
2008-07-18 17:03 Michael Davidson
  -- strict thread matches above, loose matches on Subject: below --
2008-07-17  8:18 Jose R. Valverde
2008-07-17 15:55 ` Gregg C Levine
2008-07-17 15:58   ` Larry McVoy
2008-07-17 16:18   ` Bryan Cantrill
2008-07-17 17:12     ` John Cowan
2008-07-17 17:27       ` Larry McVoy
2008-07-17 17:32         ` Michael Kerpan
2008-07-17 16:33 ` Boyd Lynn Gerber
2008-07-17 17:04   ` Wilko Bulte
2008-07-17 20:51   ` Michael Davidson

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=20080717223001.GA28983@d600.naleco.com \
    --to=pepe@naleco.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).