Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ut-sally!std-unix
From: hedrick@topaz.rutgers.edu (Charles Hedrick)
Newsgroups: comp.std.unix
Subject: Re: tar or cpio?
Message-ID: <8007@ut-sally.UUCP>
Date: Sun, 10-May-87 21:44:29 EDT
Article-I.D.: ut-sally.8007
Posted: Sun May 10 21:44:29 1987
Date-Received: Mon, 11-May-87 04:49:33 EDT
References: <8001@ut-sally.UUCP>
Sender: std-unix@ut-sally.UUCP
Reply-To: hedrick@topaz.rutgers.edu (Charles Hedrick)
Lines: 28
Approved: jsq@sally.utexas.edu (Moderator, John Quarterman)

From: hedrick@topaz.rutgers.edu (Charles Hedrick)

Since tar exists (as far as I know) on all Unix systems, and cpio only
on ATT ones, tar seems like the best choice for portable use.
Obviously any real POSIX will have both tar and cpio, but why not
leave the standard at tar?  (Note that I haven't read the POSIX
standard, so all I know about the question is what you mentioned in
your note.  I'm responding as if the choice is between the existing
tar or cpio programs.  If this is a new facility that will require a
new program to be written, then I have no comment.)

[ The format in POSIX is upwardly compatible with existing tar programs.
The format proposed for cpio is that of the current cpio program.  -mod ]

By the way, what ever happened about job control?  I recall some
discussion, but not the final resolution.  I had hoped that POSIX
would manage to get a few BSD features into general circulation.
Clearly from the end user's point of view, job control is the one most
important thing missing from System V.  (Actually networking is more
important, but it's not clear whether that is the sort of thing POSIX
should be concerned about.)

[ Job control (the HP proposal) is in the current draft.  Networking
is outside the scope of P1003.1, but there is a /usr/group Technical
Committee addressing the subject with the intention of eventually
providing input to an appropriate IEEE Working Group.  -mod ]

Volume-Number: Volume 11, Number 10