From: migieger@bawue.de (Michael Giegerich)
Subject: [pups] Re: Condition of 2BSD
Date: Thu, 20 Mar 2003 07:57:51 +0530 [thread overview]
Message-ID: <20030320022751.GA212@luva.home> (raw)
In-Reply-To: <20030320000803.GD47194@wantadilla.lemis.com>
On Thu, Mar 20, 2003 at 10:38:03AM +1030, Greg 'groggy' Lehey wrote:
> On Wednesday, 19 March 2003 at 9:40:30 -0800, Steven M. Schultz wrote:
...
> > But is 2BSD free? That I don't know. It is more free than it was
> > a long time ago but
>
> After Caldera released the Ancient UNIX license last January, 2BSD
> must be free, unless I'm missing something.
IMHO Caldera/SCO could only release the AT&T part
of xBSD. To release xBSD completely the UCB would
have to do this formally...
Caveats: haven't Caldera/SCO pulled back this re-
lease (IIRC I saw something like that when I vi-
sited their web site; reason whatever "abuse").
Also these releases from them used to be for per-
sonal, education/research use and thus would re-
strict the scope of their release. At least this
was the case when you had still to apply in wri-
ting to SCO.
I guess UCB wouldn't like again to test the current
status quo at court...
...
> > Does the current state of the Caldera/SCO/whatever license override
> > any existing licenses? THAT I do not know.
>
> My understanding (and I'm pretty sure it's correct) is that it
> replaces the old AT&T license for the specified products, including
> all AT&T precursors of [1-4]BSD.
prev parent reply other threads:[~2003-03-20 2:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 17:40 Steven M. Schultz
2003-03-20 0:08 ` Greg 'groggy' Lehey
2003-03-20 2:27 ` Michael Giegerich [this message]
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=20030320022751.GA212@luva.home \
--to=migieger@bawue.de \
/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).