From: tuhs@superglobalmegacorp.com (Jason Stevens)
Subject: [TUHS] 386BSD & NetBSD 0.8
Date: Tue, 8 Jun 2004 10:35:54 -0400 [thread overview]
Message-ID: <004401c44d65$e7aff2c0$8300a8c0@equitrac.com> (raw)
Hi, I have one question about 386BSD & NetBSD 0.8... If I'm right the reason that they were 'pulled' was because of infringing AT&T code. However didn't you need a 32v license to get access to 4.X BSD? So in that case since 32v is now public wouldn't that allow these early self hosting BSD's to be 'free' again???
Just wondering...
Jason
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20040608/e51bb25f/attachment.html>
next reply other threads:[~2004-06-08 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 14:35 Jason Stevens [this message]
2004-06-09 1:09 ` Warren Toomey
2004-06-12 5:37 ` 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='004401c44d65$e7aff2c0$8300a8c0@equitrac.com' \
--to=tuhs@superglobalmegacorp.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).