The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: tfb@tfeb.org (Tim Bradshaw)
Subject: [TUHS] Bell Labs Holmdel site coming down
Date: Thu, 18 May 2006 09:36:08 +0100 (BST)	[thread overview]
Message-ID: <5980.80.75.66.29.1147941368.squirrel@www.gradwell.com> (raw)
In-Reply-To: <1147916526.446bd0ee65cc6@www.paradise.net.nz>

On Thu, May 18, 2006 2:42 am, Wesley Parish wrote:

>
> I'm wondering if it wouldn't be possible to talk Novell into releasing
> the Unix SysVr* source code under some form of BSD/MIT X license following
> the coming evaporation of Societe Commerciel du Ondit - the SCOGroup
> Rumourmonging Machine.
>
>
> Then get OSF1-"lite" released following that.  Eating an elephant - one
> bite at a time.

I think the problem with all these `just open source it' schemes is that
they're simpler in theory than in practice.  In particular, in practice
someone has to go through the source of the system checking for everything
that might have been licensed from someone else and whose license
agreements might prohibit its release.  Few of those things will
(probably) have been kept track of, and the penalty for failure is that
some nasty residual company which now owns the stuff you licensed comes
down your throat.

For orphaned systems this is a lot of work for no obvious gain (it
wouldn't be orphaned if the organization that created it thought it had
much value to them).

A good example would probably be SunOS 4 - we already know that Sun are
quite interested in open sourcing stuff given OpenSolaris, but SunOS 4
hasn't been, presumably because it is full of stuff-they-don't-own and has
no commercial value at all.

--tim




  reply	other threads:[~2006-05-18  8:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-17 22:30 Stuart, Jon
2006-05-17 23:13 ` John Cowan
2006-05-18  1:42   ` Wesley Parish
2006-05-18  8:36     ` Tim Bradshaw [this message]
2006-05-19  8:16       ` Wesley Parish
2006-05-19 20:41         ` Tim Bradshaw
2006-05-18  8:50 ` Peter Jeremy
2006-05-18  9:42   ` Wilko Bulte
  -- strict thread matches above, loose matches on Subject: below --
2006-05-18 14:34 Michael Sokolov
2006-05-18  2:48 Norman Wilson
2006-05-17 22:40 Michael Sokolov
2006-05-17 21:39 patv
2006-05-17 23:27 ` Lyrical Nanoha
2006-05-17 19:56 patv
2006-05-17 20:48 ` Lyrical Nanoha
2006-05-17 15:29 tuhs

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=5980.80.75.66.29.1147941368.squirrel@www.gradwell.com \
    --to=tfb@tfeb.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).