From: mah@mhorton.net (Mary Ann Horton)
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 10:54:24 -0800 [thread overview]
Message-ID: <566C6D60.40205@mhorton.net> (raw)
In-Reply-To: <201512120209.tBC2930f007838@coolidge.cs.Dartmouth.EDU>
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
next prev parent reply other threads:[~2015-12-12 18:54 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 [this message]
2015-12-12 19:58 ` Armando Stettner
2015-12-12 20:13 ` Clem Cole
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=566C6D60.40205@mhorton.net \
--to=mah@mhorton.net \
/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).