From: arnold@skeeve.com
To: usotsuki@buric.co, arnold@skeeve.com
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Copyright on 4.2BSD?
Date: Sun, 13 Oct 2024 02:31:14 -0600 [thread overview]
Message-ID: <202410130831.49D8VENj1581180@freefriends.org> (raw)
In-Reply-To: <alpine.DEB.2.21.2410130419140.31516@sd-119843.dedibox.fr>
Steve Nickolas <usotsuki@buric.co> wrote:
> On Sat, 12 Oct 2024, arnold@skeeve.com wrote:
>
> > Hi All.
> >
> > I'm working on revising my book on basic *nix programming, and for
> > the new chapter on sockets, I want to include some code from 4.2 BSD.
> >
> > Is there a copyright file somewhere for that code? I'm sure it's
> > copyright the Regents of the University of California, but I'd like
> > to include the text of the copyright in the book, so that everything's
> > clear.
> >
> > Thanks!
> >
> > Arnold
> >
>
> From what I would ascertain it would, logically, fall under a copyright to
> UCB if it comes from UCB, and under 32V's (questionable) copyright if not.
>
> Oldest BSD I have any sort of code for is 4.3 and at least by that point
> most of the Berkeley stuff is marked with this copyright string:
>
> /*
> * Copyright (c) 198x Regents of the University of California.
> * All rights reserved. The Berkeley software License Agreement
> * specifies the terms and conditions for redistribution.
> */
>
> Some earlier stuff only has the first line.
>
> -uso.
Thanks. But, ... is there some sort of copying permissions to
include also? Or is it the same as 32V and covered by Caldera license?
Arnold
next prev parent reply other threads:[~2024-10-13 8:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-13 5:46 [TUHS] " arnold
2024-10-13 7:40 ` [TUHS] " Matt Day
2024-10-13 8:22 ` Steve Nickolas
2024-10-13 8:31 ` arnold [this message]
2024-10-13 14:51 ` Warner Losh
2024-10-13 15:03 ` Al Kossow
2024-10-14 7:01 ` Arno Griffioen via TUHS
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=202410130831.49D8VENj1581180@freefriends.org \
--to=arnold@skeeve.com \
--cc=tuhs@tuhs.org \
--cc=usotsuki@buric.co \
/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).