The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] why does tar have the tape device hard coded into it and why is it mt1 instead of mt0
Date: Sat, 12 Dec 2015 15:13:33 -0500	[thread overview]
Message-ID: <CAC20D2PexoEe=zuCYZm9Xi_ttLbATzm0XUiaCuY2migPd0FgBw@mail.gmail.com> (raw)
In-Reply-To: <566C6D60.40205@mhorton.net>

Interesting  memories ... IIRC: workstations were really what caused /dev/*mt*
to stop being a standard name, so not screwing it down and using the -f
option made sense. But for a long time, since it was less typing on the 11s
and Vaxen, I would do:
           tar cvb0 20 mumble...
However, once we moved to the world of networking, the -f option became
important to me.
*i.e. *   tar cvf - mumble | rmt hosts ...

Also, the DEC drives had better buffering.  Large buffers became really
important with streaming versions of 9-track and of course for the later
QIC tapes.  So blocking became even more important and I quit doing that
function with tar itself and started to pipe tar through dd to do the
blocking to get really large blocks (like 256K or 1M).   Also, tools
appeared like "double dd" (aka ddd(1)) program that originally used a two
processes and pipe to coordinates the writes so that we could stream a
Cipher drive on a 10Mhz 68K (Masscomp box).

[Note to Will - you might to google for the original ddd or talk to me
offline, I bet I have it somewhere.  Its an interesting program to analyze
if you really want to get some insight on what you could do with UNIX even
on a "slow" computer by today's standards and without a lot of today's
fancy API's].


tjt rewrote dump(1) on RTU to use AST's and may have hacked dd too (I've
lost that version I fear).  In the mid, 80's I rewrote ddd to use threads
once kernel support for threading became available and I still use that
version today when I mess with tapes (which I do less and less, but have
been known to do when trying to recover old tapes).

Clem

On Sat, Dec 12, 2015 at 1:54 PM, Mary Ann Horton <mah at mhorton.net> wrote:

> Yeah, I just can't imagine using tar with the f option.  Even back in the
> day when I was writing 9 track magtapes with tar, it would be something like
>     tar cvfb /dev/rmt0 10 .
> to get tape blocks bigger than 512 bytes.  But we never had dectapes and I
> think they did their own blocking.
>
>     Mary Ann
>
>
> On 12/11/2015 06:09 PM, Doug McIlroy wrote:
>
>> I have no memory of why Ken used mt1 not mt0.   Doug may know.
>>>
>> I don't know either. Come to think of it, I can't remember ever
>> using tar without option -f. Direct machine-to-machine trasfer,
>> e.g. by uucp, took a lot of business away from magtape soon
>> after tar was introduced. Incidentally, I think tar was written
>> by Chuck Haley or Greg Chesson, not Ken.
>>
>> Doug
>> _______________________________________________
>> TUHS mailing list
>> TUHS at minnie.tuhs.org
>> http://minnie.tuhs.org/cgi-bin/mailman/listinfo/tuhs
>>
>
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> http://minnie.tuhs.org/cgi-bin/mailman/listinfo/tuhs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20151212/8d2eebff/attachment.html>


  parent reply	other threads:[~2015-12-12 20:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-12  2:09 Doug McIlroy
2015-12-12 18:54 ` Mary Ann Horton
2015-12-12 19:58   ` Armando Stettner
2015-12-12 20:13   ` Clem Cole [this message]
2015-12-12 22:44     ` Lyndon Nerenberg
2015-12-12 20:57   ` John Cowan
  -- strict thread matches above, loose matches on Subject: below --
2015-12-13  1:41 Norman Wilson
2015-12-13  3:04 ` Lyndon Nerenberg
2015-12-12 17:17 [TUHS] TUHS] " Doug McIlroy
2015-12-12 20:17 ` [TUHS] " Diomidis Spinellis
2015-12-11 22:27 Will Senn
2015-12-11 22:31 ` Clem Cole
2015-12-11 22:52   ` Will Senn
2015-12-11 23:13     ` John Cowan
2015-12-12  0:26       ` Random832

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='CAC20D2PexoEe=zuCYZm9Xi_ttLbATzm0XUiaCuY2migPd0FgBw@mail.gmail.com' \
    --to=clemc@ccc.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 NNTP newsgroup(s).