From: "Bill Walker" <bw@student.ecok.edu>
To: egcs@cygnus.com
Subject: cpio vs. tar
Date: Tue, 04 Nov 1997 07:38:00 -0000 [thread overview]
Message-ID: <m0xSkoa-0000NmC@student.ecok.edu> (raw)
Forwarded message:
> Is it really worth the bother? Isn't cpio one of those utilities
> that's been around since UNIX was distributed on clay tablets? Even
> though X/open has marked it "to be withdrawn" and SUSv2 tags it as
> "legacy" suggesting that "Applications should migrate to the pax
> utility.", would any OS vendor not ship cpio?
>
>
>
> Alternately, we can continue to patch this one system at a time until
> we all die. Here's one that should fix the system this was reported
> on.
>
Hmm. At the risk of generating a lot of flying pieces, how about
just including GNU cpio (or GNU tar) with the compiler in the first place ?
If that is a political/technical atrocity, perhaps a "minimal" utility
could be created and shipped. Something like a "shar" which might
run under any boat-anchor with a shell. (Duck! Duck!)
BW
--
Bill Walker Ph.D.
Chairman, Dept. of Computer Science
East Central University
Ada, Oklahoma 74820-6899
e-mail: bw@cs.ecok.edu
phone: 580 332 8000 ext. 594
FAX: 580 332 4616
next reply other threads:[~1997-11-04 7:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-04 7:38 Bill Walker [this message]
1997-11-04 11:52 ` Jeffrey A Law
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=m0xSkoa-0000NmC@student.ecok.edu \
--to=bw@student.ecok.edu \
--cc=egcs@cygnus.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 read-only IMAP folder(s) and NNTP newsgroup(s).