The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: reed@reedmedia.net (Jeremy C. Reed)
Subject: [TUHS] default license, old CSRG RCS history? and BSD share/mk/*mk files?
Date: Mon, 31 Aug 2009 08:52:20 -0500 (CDT)	[thread overview]
Message-ID: <alpine.NEB.2.00.0908310839510.375@t1.m.reedmedia.net> (raw)

For 4.4BSD files, if no copyright and license is listed for specific 
files, does the standard UCB license apply? Is there any file or statement 
that says the license covers all files which don't have a specific license 
in 4.4BSD-Lite ?

Any RCS commit history for old CSRG code?

I am looking for the authors/history/copyrights for BSD 
share/mk/files.

I see that 4.4BSD-Alpha has:
r--r--r--  3/7    792 Aug 26 05:00 1992 usr/share/mk/bsd.doc.mk
r--r--r--  3/7   3761 Aug 26 05:00 1992 usr/share/mk/bsd.lib.mk
r--r--r--  3/7   1574 Aug 26 05:00 1992 usr/share/mk/bsd.man.mk
r--r--r--  3/7   4140 Aug 26 05:00 1992 usr/share/mk/bsd.prog.mk
r--r--r--  3/7   1244 Aug 26 05:00 1992 usr/share/mk/bsd.subdir.mk
r--r--r--  3/7   1387 Aug 26 05:00 1992 usr/share/mk/sys.mk
but missing the bsd.README

I couldn't find these in the other old 4 and 3BSDs (via the tuhs 
archive).

The share/mk/bsd.README from NetBSD import in 1993 has:

#	@(#)bsd.README	5.1 (Berkeley) 5/11/90

And sys.mk has:

#	@(#)sys.mk	5.11 (Berkeley) 3/13/91

And bsd.doc.mk:

#	@(#)bsd.doc.mk	5.3 (Berkeley) 1/2/91

_______________________________________________
TUHS mailing list
TUHS at minnie.tuhs.org
https://minnie.tuhs.org/mailman/listinfo/tuhs



             reply	other threads:[~2009-08-31 13:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-31 13:52 Jeremy C. Reed [this message]
2009-08-31 15:59 ` Larry McVoy
2009-09-01  5:55   ` Greg 'groggy' Lehey
2009-09-01  1:59 ` Wesley Parish

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.NEB.2.00.0908310839510.375@t1.m.reedmedia.net \
    --to=reed@reedmedia.net \
    /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).