From d2df2d5f64de0859c4f91ef44997bce3c3700401 Mon Sep 17 00:00:00 2001
From: Rob Landley <rob@landley.net>
Date: Sat, 18 May 2019 17:15:33 -0500
Subject: Fix a dead link, add link to OpenBSD suggested template license, and
 record Kirk McKusick's email for posterity. (I posted it to the mailing list
 when it happened, but this is more obvious...)

---
 www/license.html | 15 ++++++++++-----
 1 file changed, 10 insertions(+), 5 deletions(-)

(limited to 'www/license.html')

diff --git a/www/license.html b/www/license.html
index f250410f..55521e73 100755
--- a/www/license.html
+++ b/www/license.html
@@ -28,17 +28,18 @@ OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.</p>
 <a href=http://unlicense.org>unlicense</a>, and <a href=http://wtfpl.net/>wtfpl</a>,
 the intent is to effectively place the licensed material into the public domain,
 which after decades of FUD (such as the time OSI's ex-lawyer compared
-<a href=http://www.cod5.org/archive/>placing code into the public domain</a> to
+<a href=https://web.archive.org/web/20160530090006/http://www.cod5.org/archive/>placing code into the public domain</a> to
 <a href=http://www.linuxjournal.com/article/6225>abandoning trash by the
 side of a highway</a>) is considered somehow unsafe. But if some random third
 party
 <a href=https://github.com/mkj/dropbear/blob/master/libtomcrypt/LICENSE>takes
 public domain code</a> and slaps <a href=http://www.opensource.apple.com/source/gnuzip/gnuzip-25/gzip/gzip.c>some other license on it</a>, then it's fine.</p>
 
-<p>To work around this perception, the above license is a standard 2-clause BSD
-license <a href=https://github.com/landley/toybox/commit/ee86b1d8e25cb0ca9d418b33eb0dc5e7716ddc1e>minus the half sentence</a>
-requiring text copied verbatim into derived works. If 2BSD is
-ok, the 0BSD should be ok, despite being equivalent to placing code in the
+<p>To work around this perception, the above license is the
+<a href=https://www.openbsd.org/policy.html>OpenBSD suggested template
+license</a>, <a href=https://github.com/landley/toybox/commit/ee86b1d8e25cb0ca9d418b33eb0dc5e7716ddc1e>minus the half sentence</a>
+requiring the license text be copied verbatim into derived works. If 2BSD is
+ok, then 0BSD should be ok, despite being equivalent to placing code in the
 public domain.</p>
 
 <p>Modifying the license in this way avoids the hole android toolbox fell into where
@@ -49,4 +50,8 @@ additional restrictions" and BSD's "you must include this large hunk of text"
 by sticking the two licenses at
 <a href=http://git.busybox.net/busybox/tree/networking/ping.c?id=887a1ad57fe978cd320be358effbe66df8a068bf>opposite ends of the file</a> and hoping nobody
 noticed.</a>
+
+<p>Note: I asked <a href=https://www.oreilly.com/openbook/opensources/book/kirkmck.html>Kirk McKusick</a> for permission to call this a BSD license at
+a conference shortly before I started using the name,
+and <a href=0bsd-mckusick.txt>again in 2018</a>.</p>
 <!--#include file="footer.html" -->
-- 
cgit v1.2.3