Computer Old Farts Forum
 help / color / mirror / Atom feed
From: clemc at ccc.com (Clem Cole)
Subject: [COFF] 21st Century Equivalent to 'learn'?
Date: Sat, 7 Mar 2020 17:05:52 -0500	[thread overview]
Message-ID: <CAC20D2Oj1DWd8kDBaBpkL=N7uRGTKJCtb4=NLPBTCr4SA+hN2w@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2003080842510.64345@aneurin.horsfall.org>

Dave -- please, let's not re-live 'tar-wars'   -- it's why the POSIX
command is called 'pax' - God Bless USENIX for funding the original
implementation and putting it in the public domain.

- tar was research/BSD and worked best when you chdir to some directory and
were working interactively and was the logic follow on to the earlier stp
and tp. It was ASCII and after the binary issues of tp was a welcome
relief. The format was also extensible (thanks to bug in the original
implementation).
- cpio was USG and worked best with a find(1) script/automation - which was
good for controlled distributions but poor for interactive use. It was also
binary originally (with PDP-11isms builtin)

The real issue in the end was cpio being part of System III many/most
universities did not have it originally, so the tp/stp was what we used,
which was replaced by tar.

pax has a user interface that work either ways, and the USENIX public
implementation can read both tape formats..

Clem

PS At Masscomp, I once wrote "car" but no one ever wrote "tpio".

On Sat, Mar 7, 2020 at 4:50 PM Dave Horsfall <dave at horsfall.org> wrote:

> On Fri, 6 Mar 2020, Andy Kosela wrote:
>
> [ List elided ]
>
> What do you have against "cpio"?  Admittedly it's harder to use than "tar"
> but I still come across it from time to time; also, "tar" had a bug at one
> time whereby it did not handle an empty directory, and I think there was a
> problem with devices/sockets as well.
>
> Heck, I still have "cpio -adplumv" burned into my retinas.
>
> -- Dave
> _______________________________________________
> COFF mailing list
> COFF at minnie.tuhs.org
> https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200307/ed640139/attachment.html>


  reply	other threads:[~2020-03-07 22:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-04  3:49 wkt
2020-03-04  6:23 ` spedraja
2020-03-04  6:55   ` thomas.paulsen
2020-03-04  9:53   ` wkt
2020-03-04 19:31 ` dave
2020-03-05  1:00 ` wkt
2020-03-05 12:43   ` jpl.jpl
2020-03-05 21:23     ` arrigo
2020-03-06  3:14       ` grog
2020-03-06  9:10     ` akosela
2020-03-07 21:50       ` dave
2020-03-07 22:05         ` clemc [this message]
2020-03-07 23:02           ` dfawcus+lists-coff
2020-03-08  0:02             ` clemc
2020-03-06  3:39   ` bakul
2020-03-12 20:53 ` rtomek
2020-03-08  3:39 rudi.j.blom

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='CAC20D2Oj1DWd8kDBaBpkL=N7uRGTKJCtb4=NLPBTCr4SA+hN2w@mail.gmail.com' \
    --to=coff@minnie.tuhs.org \
    /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).