Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!husc6!ut-sally!std-unix
From: std-unix@ut-sally.UUCP
Newsgroups: mod.std.unix
Subject: Re: 1003.2 Command Groups
Message-ID: <6979@ut-sally.UUCP>
Date: Wed, 28-Jan-87 12:48:55 EST
Article-I.D.: ut-sally.6979
Posted: Wed Jan 28 12:48:55 1987
Date-Received: Thu, 29-Jan-87 06:28:39 EST
References: <6710@ut-sally.UUCP>, <6783@ut-sally.UUCP> <6863@ut-sally.UUCP>
Organization: IEEE P1003 Portable Operating System for Computer Environments Committee
Lines: 15
Approved: jsq@sally.utexas.edu
Summary: cpio has more than just one use

From: akgua!mtgzz!bds@seismo.css.gov (b.d.szablak)
Date: 16 Jan 87 13:44:21 GMT
Organization: AT&T, Middletown NJ

> > I suggest that "cpio" be excluded.  Maybe they'll stop distributing
> > System V on byte-order-dependent cpio tapes if it becomes non-standard.
> 
> Agreed.  P1003.1 has already defined a standard interchange format, and it's
> not cpio (it is, in fact, a somewhat extended tar).

I rarely use cpio to create tapes, but I often use cpio... Principally
for transmitting via uucp et. al. multiple files (a cpio file is more
manageable), and for moving and copying files in directory hierarchies.

Volume-Number: Volume 9, Number 32