From: doug@cs.dartmouth.edu (Doug McIlroy)
Subject: [TUHS] IP in v8-v10
Date: Wed, 29 Mar 2017 22:36:02 -0400 [thread overview]
Message-ID: <201703300236.v2U2a2oF018229@coolidge.cs.Dartmouth.EDU> (raw)
> > Can you characterize what the 3rd-party material might be?
>
> Me personally, no. But there are others on the list who can help do this.
> Hopefully they will chime in!
Here's a list, gathered from the manuals, of stuff that Bell Labs
may not have the right to redistribute, with some (uncertain)
attributions of origin. I did not check to see which of them appear in
the TUHS archives; I doubt that /usr/src fully covered /bin and /usr/bin.
This list is at best a first draft. Please weigh in with corrections.
Doug
Kernel internet code. BSD
Imported commands
esterel INRIA
lisp, liszt, lxref MIT
icont, iconc Arizona
macsyma MIT
maple Maplesoft
Mail BSD
matlab Mathworks
more BSD (From the manpage: "More, a paginator that lives up to its name, has
too many features to describe." Its prodigality has been eclipsed by "less".)
netnews Duke
ops5 CMU
pascal, pc BSD
pxp BSD
readnews, checknews, postnews Duke
sdb BSD
smp Wolfram
spitbol IIT
telnet BSD
tex Stanford
tset BSD
vi, ex, edit BSD
Commands I'm not sure about, could be from Bell Labs
cyntax
news
ropy
strings
Library functions
termcap BSD
Imported games
adventure, zork, aarvark, rogue
atc
doctor MIT
mars
trek, ogre, sol, warp, sail
Games I'm not sure about
back
boggle, hangman
cribbage, fish
ching
gebam
imp
mille
pacman
pengo
swar
tso
next reply other threads:[~2017-03-30 2:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 2:36 Doug McIlroy [this message]
2017-03-30 5:02 ` Warner Losh
2017-03-30 11:06 ` Derek Fawcus
2017-03-30 19:29 ` Steve Johnson
2017-03-30 21:38 ` John Floren
2017-03-30 19:44 ` [TUHS] UUNET Steve Johnson
2017-04-03 1:58 ` John S Quarterman
2017-04-05 3:28 ` [TUHS] IP in v8-v10 Lyndon Nerenberg
2017-04-05 12:48 ` Clem Cole
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=201703300236.v2U2a2oF018229@coolidge.cs.Dartmouth.EDU \
--to=doug@cs.dartmouth.edu \
/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).