The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@iitbombay.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Early BSD license thread
Date: Wed, 21 Sep 2022 15:06:00 -0700	[thread overview]
Message-ID: <F1DCAB52-F6ED-4F89-892E-694213E2F8B0@iitbombay.org> (raw)
In-Reply-To: <CANCZdfq1SFZwg25dOj+BrXab1-nhQkE_=XXsx=pDc=wPXAeUDw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1442 bytes --]

On Sep 21, 2022, at 8:25 AM, Warner Losh <imp@bsdimp.com <mailto:imp@bsdimp.com>> wrote:
> 
> That makes a lot of sense. When there was a name, it was preserved, but a huge amount of the sources had nothing at all in the source files to identify it. One big area of contribution was into the kernel where the options sometimes contained the name of where the code came from. In the 2BSD kernels we see eg TEXAS_AUTOBAUD, MENLO_OVLY, MENLO_KOV, MENLO_JCL, MPX_FILS, CGL_RTP and a bunch of UCB_ names. It's clear the non UCB ones came from elsewhere, but there's no info on where they came from (they are documented in setup.5 at least so I know what they are). So given the sparseness of the early marking for provenance, the coments make more sense and give a better timeframe to it.

Recall that the US joined the Berne Convention in 1988. As I recall prior to that you had to stick to some copyright formalities such as putting your copyright & year in the source code. As I recall the US law didn't protect your copyright if you didn't do this in sources. This may have played a part in UCB adding a copyright source files that didn't have anything? I could be wrong but these are just some random bits picked up at the time. I did get in the habit of putting at least a one line copyright notice by default starting in 1981 (either for whatever company I worked for at the time or my own copyright for code I wrote on my own at home).

[-- Attachment #2: Type: text/html, Size: 2369 bytes --]

  reply	other threads:[~2022-09-21 22:07 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-21 10:10 [TUHS] " Warner Losh
2022-09-21 12:36 ` [TUHS] " Rob Pike
2022-09-21 13:33   ` Marc Donner
2022-09-21 13:46   ` Warner Losh
2022-09-21 14:50     ` Rich Salz
2022-09-21 14:58       ` Warner Losh
2022-09-21 15:06         ` Miod Vallat
2022-09-21 14:57     ` [TUHS] Fwd: " Clem Cole
2022-09-21 15:09       ` [TUHS] " Larry McVoy
2022-09-21 15:25       ` Warner Losh
2022-09-21 22:06         ` Bakul Shah [this message]
2022-09-21 22:20           ` [TUHS] " Warner Losh
2022-09-21 21:14       ` [TUHS] Re: Fwd: " Theodore Ts'o
2022-09-21 21:46         ` Clem Cole
2022-09-21 21:49   ` [TUHS] " Phil Budne
2022-09-21 22:07     ` Rich Salz
2022-09-21 22:24       ` Warner Losh
2022-09-21 22:09     ` Dan Cross
2022-09-21 22:19       ` Steve Nickolas
2022-09-21 22:44         ` Joseph Holsten
2022-09-21 23:53           ` Chet Ramey
2022-09-22  0:32             ` Rob Pike
2022-09-22  7:08       ` [TUHS] " Andy Kosela
2022-09-22 17:44         ` [TUHS] " Dan Cross
2022-09-22 18:44           ` Bakul Shah

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=F1DCAB52-F6ED-4F89-892E-694213E2F8B0@iitbombay.org \
    --to=bakul@iitbombay.org \
    --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).