The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: imp@bsdimp.com (M. Warner Losh)
Subject: [Unix-jun72] Early UNIX: papers & Usenix
Date: Fri, 10 Apr 2009 11:21:35 -0600 (MDT)	[thread overview]
Message-ID: <20090410.112135.387193198.imp@bsdimp.com> (raw)
In-Reply-To: <20090410162319.GB12970@mercury.ccil.org>

In message: <20090410162319.GB12970 at mercury.ccil.org>
            John Cowan <cowan at ccil.org> writes:
: Warren Toomey scripsit:
: 
: > Here is a very early draft: http://minnie.tuhs.org/Z/usendraft.pdf.
: > Lots of typos etc.
: 
: Thanks; fascinating!
: 
: Do the Net-2-derived BSDs (including Darwin) really count as Unix-derived?

Yes.

: I thought they were fairly free of AT&T code now, other than headers and
: the like.  Conceptually, of course, they are Unix-derived, but then so
: is Linux.

There's 24 files that have AT&T copyright notice on them that are
still present in the code.  And there's dozens of files in SYS V that
are bsd-derived that now have the proper UCB copyright notice.  The
link to Unix is direct and explicit in the 4.4-lite derived BSDs,
unlike Linux, which has no AT&T code to speak of in it.  Also,
technically speaking, all the BSDs (including Darwin) are 4.4-lite
derived these days, not net-2 derived, since all the projects switched
to 4.4-lite as apart of the ucb/at&t settlement.

See for example from FreeBSD:

 * Copyright (c) 1982, 1986, 1989, 1991, 1992, 1993
 *      The Regents of the University of California.  All rights reserved.
 * (c) UNIX System Laboratories, Inc.
 * All or some portions of this file are derived from material licensed
 * to the University of California by American Telephone and Telegraph
 * Co. or Unix System Laboratories, Inc. and are reproduced herein with
 * the permission of UNIX System Laboratories, Inc.
 *

is found in: init_main.c kern_acct.c kern_clock.c kern_descrip.c
kern_exit.c kern_fork.c kern_prot.c kern_resource.c kern_shutdown.c
kern_sig.c kern_subr.c kern_synch.c kern_timeout.c sched_4bsd.c
subr_param.c subr_prf.c sys_generic.c tty_info.c vfs_export.c
vfs_lookup.c vfs_mount.c vfs_subr.c vfs_syscalls.c vfs_vnops.c

All these files are explicitly OK based on the settlement of the UCB
AT&T lawsuit.

: It would be snazzy to restore the classical typography of Unix as
: U<small>NIX</small> in your paper.

That would be cool.

Warner



  reply	other threads:[~2009-04-10 17:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-09  7:22 Warren Toomey
2009-04-09 13:21 ` John Cowan
2009-04-09 14:47   ` M. Warner Losh
2009-04-10  7:44     ` Warren Toomey
2009-04-10 16:23       ` John Cowan
2009-04-10 17:21         ` M. Warner Losh [this message]
2009-04-10 20:31         ` Brad Parker
2009-04-10 20:38           ` lyricalnanoha
2009-04-10 22:41             ` Warren Toomey
2009-04-10 22:51               ` lyricalnanoha
2009-04-10 22:28         ` Warren Toomey
2009-04-10 16:31       ` John Cowan
2009-04-09 18:43 ` Doug Merritt

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=20090410.112135.387193198.imp@bsdimp.com \
    --to=imp@bsdimp.com \
    /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).