Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 alpha 4/15/85; site cbosgd.UUCP
Path: utzoo!watmath!clyde!cbosgd!mark
From: mark@cbosgd.UUCP (Mark Horton)
Newsgroups: net.wanted.sources,net.bugs.4bsd,net.followup
Subject: Re: Need cpio.c source
Message-ID: <1098@cbosgd.UUCP>
Date: Sat, 27-Apr-85 23:14:37 EDT
Article-I.D.: cbosgd.1098
Posted: Sat Apr 27 23:14:37 1985
Date-Received: Sun, 28-Apr-85 08:58:24 EDT
References: <55@ecrcvax.UUCP>
Organization: AT&T Bell Laboratories, Columbus, Oh
Lines: 30
Xref: watmath net.wanted.sources:760 net.bugs.4bsd:1478 net.followup:4816

In article <55@ecrcvax.UUCP> pete@ecrcvax.UUCP (Pete Delaney) writes:
>
>	Sigh.  For some strange reason Berkely 4.2 doesn't come with
>SCCS or cpio.  These turkeys makeing releases should get their sh*t
>together!  Would someone out there in net land please send a copy of
>the new System V cpio so we can read our release tape so that we can
>get the source of SCCS, so that we can use the latest kernel.

I feel obligated to point out the reason why 4.2BSD does not include
cpio or SCCS.  If they did, AT&T would be justified in legal action
to stop them from distributing 4.2BSD at all.  Contrary to a comment
I just read here, 4.2BSD requires a UNIX/32V license, NOT a System V
license.  This means that Berkeley can include AT&T code that was
in UNIX/32V, but they do not have permission from AT&T to include
code from other AT&T versions of UNIX.

In particular, cpio and SCCS were both in PWB/UNIX 1.0, in System III,
and in System V, but not in V7 or 32V.  So it would be illegal for
Berkeley to include them in their system unless they required one
of these licenses from everyone they distribute UNIX to.

Before anyone sends a copy to ecrcvax, you'd best verify that ecrcvax
has a System V license.  Otherwise you'll be violating your license.

Incidently, while the V7/nBSD family does not have cpio, they do have
tar, a similar program.  Since System III and System V have tar (except
for the 3B2, which for some reason left it out) it has emerged that
the only universal complete file packaging format for UNIX is tar format,
for tapes and for UUCP images.  Apparently for this reason, /usr/group
has adopted tar format as part of the UNIX standard.