From: msokolov@ivan.Harhan.ORG (Michael Sokolov)
Subject: [TUHS] license
Date: Sun, 3 Nov 02 22:05:23 PST [thread overview]
Message-ID: <0211040605.AA08946@ivan.Harhan.ORG> (raw)
"Greg 'groggy' Lehey" <grog at lemis.com> wrote:
> I'll leave it to others to describe the early days. The Berkeley
> Software License Agreement, generally called the BSD license, is
> pretty straightforward, though.
Wrong. The Berkeley Software License Agreement and what is known today as the
"BSD license" are two different things. The latter is the liberal header
Berkeley started prepending around 1988 to files that were totally theirs
without any Bell Labs code. The former was the paper license that went with the
4.3BSD and earlier tapes where Bell, Bell/Berkeley, and pure Berkeley parts
were not distinguished and the entire system could be used only by holders of
UNIX source licenses from AT&T. Although I've never seen it myself, the
Berkeley Software License Agreement could not have been like the liberal
header, it surely had stuff in it telling you that if you share it with anyone,
you must first verify that the recipient has a UNIX source license from AT&T,
etc.
MS
next reply other threads:[~2002-11-04 6:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-04 6:05 Michael Sokolov [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-04 5:49 Michael Sokolov
2002-11-04 5:02 Marco Robado
2002-11-04 5:43 ` Greg 'groggy' Lehey
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=0211040605.AA08946@ivan.Harhan.ORG \
--to=msokolov@ivan.harhan.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).