The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: imp@bsdimp.com (M. Warner Losh)
Subject: [TUHS] SunOS 4.1.1?
Date: Fri, 21 Sep 2007 12:24:19 -0600 (MDT)	[thread overview]
Message-ID: <20070921.122419.1159135324.imp@bsdimp.com> (raw)
In-Reply-To: <9552c7c8500326acee33a5cbe54df693@coraid.com>

In message: <9552c7c8500326acee33a5cbe54df693 at coraid.com>
            Brantley Coile <brantley at coraid.com> writes:
: BSD never used anything that would have been covered by the System III
: or System V license.  The ancient Unix license would be fine for that.
: Howver, I'm pretty sure there is a lot of stuff in SunOS 4 that was from
: System III and System V.
: 
: To restate, BSD *.* is legal under the Ancient Unix license,
: which covers 32V and earlier.  Berkeley never had a liscense
: for anything later than 32V.

True.  When Sun took BSD 4.2, it had to buy a license from AT&T to
distribute.  With that license came the System V streams stuff, which
Sun included in SunOS 4.  There was much other technology from other
third parties in SunOS.  Just doing an audit of what came from where
would be expensive and time consuming...

It is unclear to me if Sun could retroactively apply the Ancient Unix
license or not given the code's derivation history.  I don't know what
their specific agreements with AT&T stipulate.  Again, another topic
for research, unless Novell is willing to grant a waver.

Warner


: > In message: <102AD3A8-168F-4407-9FA1-86CB2B97A198 at tfeb.org>
: >             Tim Bradshaw <tfb at tfeb.org> writes:
: > : On 21 Sep 2007, at 15:58, John Cowan wrote:
: > : 
: > : >
: > : > The best available story for the Sun3 code is that Sun doesn't
: > : > object to non-commercial use (which certainly is not the same
: > : > as an open source license).
: > : 
: > : I'm assuming that the source isn't available at all (I wonder if Sun  
: > : still have it?)
: > 
: > SunOS for the Sun3 machines was derived from BSD 4.2 with a lot of
: > code from other places.  BSD 4.2 requires an AT&T license because
: > there is still AT&T code in it.  As such, open sourcing it would be
: > difficult at best.
: > 
: > Based on what friends that work at sun tell me, the source can still
: > be obtained internally if necessary...  I never pressed them for
: > details on the rather curious way they put it (like I did just now).
: > 
: > Warner
: > _______________________________________________
: > TUHS mailing list
: > TUHS at minnie.tuhs.org
: > https://minnie.tuhs.org/mailman/listinfo/tuhs
: 
: _______________________________________________
: TUHS mailing list
: TUHS at minnie.tuhs.org
: https://minnie.tuhs.org/mailman/listinfo/tuhs
: 
: 



  reply	other threads:[~2007-09-21 18:24 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3367693331-1097@e4ward.com>
2007-09-20 13:48 ` Andrew Warkentin
2007-09-20 17:22   ` asbesto
2007-09-21 14:44     ` Tim Bradshaw
2007-09-21 14:58       ` John Cowan
2007-09-21 16:41         ` asbesto
2007-09-21 16:46           ` John Cowan
2007-09-21 17:22             ` asbesto
2007-09-21 17:29               ` M. Warner Losh
2007-09-21 19:11                 ` asbesto
2007-09-21 17:23           ` Seth Morabito
2007-09-21 17:47             ` Brantley Coile
2007-09-21 16:48         ` Tim Bradshaw
2007-09-21 17:12           ` John Cowan
2007-09-21 17:14           ` M. Warner Losh
2007-09-21 17:30             ` Brantley Coile
2007-09-21 18:24               ` M. Warner Losh [this message]
2007-09-21 20:58                 ` Bill Pechter
2007-09-22  9:32                   ` Wesley Parish
2007-09-25  1:52           ` John Cowan
2007-09-25 14:06             ` Jose R. Valverde
2007-09-25 14:38               ` M. Warner Losh
2007-09-25 15:37                 ` John Cowan
2007-09-25 15:41 Jose R. Valverde
  -- strict thread matches above, loose matches on Subject: below --
2007-09-20  2:20 Larry McVoy
2007-09-20  7:58 ` asbesto

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=20070921.122419.1159135324.imp@bsdimp.com \
    --to=imp@bsdimp.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).