From: Steve Nickolas <usotsuki@buric.co>
To: Warner Losh <imp@bsdimp.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] 386BSD released
Date: Wed, 14 Jul 2021 11:37:08 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.21.2107141136250.2430@sd-119843.dedibox.fr> (raw)
In-Reply-To: <CANCZdfp-ZtijojnTk3ORgG=Ko-aGNGQtkxAVozKUZtyqmzhCCw@mail.gmail.com>
On Wed, 14 Jul 2021, Warner Losh wrote:
> The X10R3 license sure looks like a standard MIT license. The other license
> statements that were included also read very much like open source, or
> at least a strong intention of being open source, absent any drafting flaws.
>
> Copyright 1985 by the Massachusetts Institute of Technology
>
> Permission to use, copy, modify, and distribute this
> software and its documentation for any purpose and without
> fee is hereby granted, provided that the above copyright
> notice appear in all copies and that both that copyright
> notice and this permission notice appear in supporting
> documentation, and that the name of M.I.T. not be used in
> advertising or publicity pertaining to distribution of the
> software without specific, written prior permission.
> M.I.T. makes no representations about the suitability of
> this software for any purpose. It is provided "as is"
> without express or implied warranty.
>
> This software is not subject to any license of the American
> Telephone and Telegraph Company or of the Regents of the
> University of California.
Ironically...that's closer to a "3-clause BSD" license.
-uso.
next prev parent reply other threads:[~2021-07-14 15:37 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 22:28 Dave Horsfall
2021-07-14 7:54 ` Michael Kjörling
2021-07-14 8:19 ` Angus Robinson
2021-07-14 8:32 ` Michael Kjörling
2021-07-14 9:07 ` Lars Brinkhoff
2021-07-14 14:09 ` Larry McVoy
2021-07-14 14:54 ` Warner Losh
2021-07-14 15:06 ` Richard Salz
2021-07-14 15:37 ` Steve Nickolas [this message]
2021-07-14 10:09 ` Tom Ivar Helbekkmo via TUHS
2021-07-14 10:39 ` arnold
2021-07-14 17:21 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2021-07-14 17:32 ` Richard Salz
2021-07-14 15:01 ` Clem Cole
2021-07-14 17:40 ` [TUHS] [COFF] " Theodore Y. Ts'o
2021-07-14 17:50 ` Larry McVoy
2021-07-14 18:28 ` Clem Cole
2021-07-14 11:49 ` [TUHS] " Andy Kosela
2021-07-14 15:48 ` Theodore Y. Ts'o
2021-07-16 1:35 ` Dave Horsfall
2021-07-16 2:33 ` risner
2021-07-16 4:25 ` Theodore Y. Ts'o
2021-07-16 5:51 ` Bakul Shah
2021-07-16 13:00 ` Theodore Y. Ts'o
2021-07-16 13:56 ` Larry McVoy
2021-07-16 14:40 ` Clem Cole
2021-07-16 15:44 ` Theodore Y. Ts'o
2021-07-16 16:11 ` Bakul Shah
2021-07-16 19:07 ` Kevin Bowling
2021-07-16 20:17 ` Clem Cole
2021-07-16 20:24 ` Richard Salz
2021-07-18 13:13 ` arnold
2021-07-18 13:23 ` Richard Salz
2021-07-18 13:43 ` [TUHS] MtXinu calendar (was Re: 386BSD released) Al Kossow
2021-07-18 13:51 ` Al Kossow
2021-07-18 16:44 ` Al Kossow
2021-07-18 17:38 ` John Cowan
2021-07-18 18:35 ` Bakul Shah
2021-07-19 3:06 ` Dan Stromberg
2021-07-18 19:00 ` arnold
2021-07-18 21:48 ` Deborah Scherrer
2021-07-18 20:06 ` Lyle Bickley
2021-07-14 21:37 ` [TUHS] 386BSD released Bakul Shah
2021-07-16 21:22 ` Dave Horsfall
2021-07-15 2:21 Douglas McIlroy
2021-07-15 2:41 ` Adam Thornton
2021-07-15 15:07 ` Clem Cole
2021-07-16 17:30 Nelson H. F. Beebe
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=alpine.DEB.2.21.2107141136250.2430@sd-119843.dedibox.fr \
--to=usotsuki@buric.co \
--cc=imp@bsdimp.com \
--cc=tuhs@tuhs.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).