From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] 2.11BSD license question: porting software to NetBSD
Date: Sat, 19 Apr 2003 13:25:37 +0930 [thread overview]
Message-ID: <20030419035537.GJ61510@wantadilla.lemis.com> (raw)
In-Reply-To: <200304181656.h3IGuGfC028575@string1.ciencias.uniovi.es>
On Friday, 18 April 2003 at 18:56:16 +0200, Igor Sobrado wrote:
> Hello.
>
> I have just finished porting diction(1) and style(1) from 2.11BSD
> to the NetBSD operating system. Those utilities are a part of the
> AT&T Documenter's Workbench (DWB), and are not available on the v7
> and 32V UNIX releases.
>
> I asked to the people of the NetBSD Foundation about the possibility
> of adding those commands to the base system (as a part of the tarball
> with documentation tools) but they think that it is not possible,
> as a consequence of a licensing issue. I supposed that all the
> software provided in the 2.11BSD was under a BSD license, but it
> looks like 2.11BSD is a closed source release.
That's not correct any more. Who were you talking to at the NetBSD
project?
> Can someone, please, helping me on this matter? What should I do?
> Should I just drop this software?
We discussed the Caldera release of "ancient UNIX" on this mailing
list recently. Caldera (now SCO again) was supposed to make some kind
of official statement, but it's taking its time.
Greg
--
Finger grog at lemis.com for PGP public key
See complete headers for address and phone numbers
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20030419/aa7955d9/attachment.sig>
next prev parent reply other threads:[~2003-04-19 3:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-18 16:56 Igor Sobrado
2003-04-19 3:55 ` Greg 'groggy' Lehey [this message]
2003-04-19 6:33 ` Derrik Walker v2.0
2003-04-19 7:23 ` Igor Sobrado
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=20030419035537.GJ61510@wantadilla.lemis.com \
--to=grog@lemis.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).