From: lyndon@orthanc.ca (Lyndon Nerenberg)
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 14:44:35 -0800 [thread overview]
Message-ID: <22F1828F-F9D6-4AEA-850F-E14FF919B114@orthanc.ca> (raw)
In-Reply-To: <CAC20D2PexoEe=zuCYZm9Xi_ttLbATzm0XUiaCuY2migPd0FgBw@mail.gmail.com>
On Dec 12, 2015, at 12:13 PM, Clem Cole <clemc at ccc.com> wrote:
> 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).
Anyone recall when pump came into play? What that a Plan9 thing?, or did it originate in Research UNIX.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20151212/ac1e027e/attachment.sig>
next prev parent reply other threads:[~2015-12-12 22:44 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
2015-12-12 22:44 ` Lyndon Nerenberg [this message]
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=22F1828F-F9D6-4AEA-850F-E14FF919B114@orthanc.ca \
--to=lyndon@orthanc.ca \
/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).