From: Rob Pike <robpike@gmail.com>
To: Henry Bent <henry.r.bent@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: On computerese
Date: Mon, 16 Sep 2024 16:11:03 +1000 [thread overview]
Message-ID: <CAKzdPgxuErhhZvnfNF8u4KjL-p5nfmU-HztxyWUmLrE1dqs=UQ@mail.gmail.com> (raw)
In-Reply-To: <CAEdTPBeaS=41qi4H4rZnqFMjAw_deeb_K2i_wFNxPsxKDCQGsQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1778 bytes --]
James Gosling used this idiomatic JCL command (see loop body) in something
or other, and Brian and I borrowed it (with attribution) for the bundle
command in our book.
% cat /usr/local/plan9/bin/bundle
#!/bin/sh
echo '# To unbundle, run this file'
for i
do
echo "echo $i"
echo "sed 's/.//' >$i <<'//GO.SYSIN DD $i'"
sed "s/^/-/" $i
echo "//GO.SYSIN DD $i"
done
%
-rob
On Mon, Sep 16, 2024 at 3:31 PM Henry Bent <henry.r.bent@gmail.com> wrote:
> On Mon, 16 Sept 2024 at 00:11, Adam Thornton <athornton@gmail.com> wrote:
>
>> You know, this is a place that might actually be able to provide a
>> definitive answer to me. A brief web search found me asking the same
>> question in 1995.
>>
>> When I were a wee lad, I was told `dd` was short for `do DEBE`, which,
>> while obviously referencing a well-known movie about a Northern Texas
>> sports team and their most enthusiastic fan, also referred to the mainframe
>> software whose name was an acronym for `Does Everything But Eat` and whose
>> function was to copy data across sources with very different blocking and
>> representation conventions...which is kinda what `dd` does.
>>
>> Can anyone here confirm or deny that origin for the utility's name?
>>
>>
> I looked through a broad swath of dd source files and man pages from v5 to
> System III and SVR4, the BSD SCCS tree, various commercial UNIXes, modern
> BSDs, and modern Linux but none of them have any sort of explanation of the
> name. I figured I'd at least find something!
>
> It is the case that many places refer to the command's function as
> "convert and copy," so I wonder if it's some sort of play on the fact that
> the expected name of the command might be "cc".
>
> -Henry
>
[-- Attachment #2: Type: text/html, Size: 8003 bytes --]
next prev parent reply other threads:[~2024-09-16 6:11 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-15 21:48 Noel Chiappa
2024-09-15 22:01 ` Peter Weinberger (温博格) via TUHS
2024-09-15 22:15 ` Rob Pike
2024-09-15 22:29 ` Larry McVoy
2024-09-16 3:55 ` Adam Thornton
2024-09-16 4:17 ` Rob Pike
2024-09-16 5:15 ` Dave Horsfall
2024-09-16 5:26 ` Tom Lyon
2024-09-16 10:30 ` Rob Pike
2024-09-16 5:06 ` Henry Bent
2024-09-16 6:11 ` Rob Pike [this message]
2024-09-16 22:50 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2024-09-16 23:14 ` Bakul Shah via TUHS
2024-09-17 2:19 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2024-09-16 23:16 ` Dave Horsfall
2024-09-16 23:24 ` Larry McVoy
2024-09-17 0:00 ` segaloco via TUHS
2024-09-17 0:17 ` Rob Pike
2024-09-17 5:54 ` arnold
2024-09-18 1:40 ` Dave Horsfall
2024-09-18 2:04 ` Rich Salz
2024-09-18 5:09 ` arnold
2024-09-18 5:12 ` arnold
2024-09-18 13:08 ` Chet Ramey via TUHS
2024-09-30 1:01 ` Russ Cox
2024-09-30 8:16 ` arnold
2024-09-30 12:10 ` Russ Cox
2024-09-30 15:00 ` Jacob Moody
2024-09-17 6:00 ` arnold
2024-09-17 6:25 ` Henry Bent
2024-09-17 20:25 ` Alexander Schreiber
2024-09-17 20:50 ` Larry McVoy
2024-09-16 3:02 ` arnold
-- strict thread matches above, loose matches on Subject: below --
2024-09-17 1:27 Norman Wilson
2024-09-17 1:29 ` Rob Pike
2024-09-17 3:44 ` Adam Thornton
2024-09-17 12:08 ` Dan Cross
2024-09-17 1:17 Norman Wilson
2024-09-17 1:28 ` Henry Bent
2024-09-16 12:07 Douglas McIlroy
2024-09-16 14:36 ` Clem Cole
2024-09-15 19:25 John Dow via TUHS
2024-09-15 19:52 ` Dan Halbert
2024-09-15 14:37 Douglas McIlroy
2024-09-15 19:21 ` Rik Farrow
2024-09-15 20:43 ` sjenkin
2024-09-15 20:48 ` Dave Horsfall
2024-09-15 21:08 ` Marc Donner
2024-09-15 21:41 ` Dave Horsfall
2024-09-16 0:49 ` Marc Donner
2024-09-29 0:49 ` Aron Insinga
2024-09-29 1:09 ` Warner Losh
2024-09-30 16:05 ` Paul Winalski
2024-09-30 18:07 ` Dan Cross
2024-09-30 19:15 ` Henry Bent
2024-09-30 20:00 ` Dan Halbert
2024-09-30 20:11 ` Henry Bent
2024-09-30 20:39 ` Clem Cole
2024-10-01 4:31 ` Lars Brinkhoff
2024-10-01 13:36 ` Dan Halbert
2024-09-30 20:51 ` Steffen Nurpmeso
2024-09-30 21:25 ` Henry Bent
2024-09-30 22:38 ` Steffen Nurpmeso
2024-09-30 22:46 ` Bakul Shah via TUHS
2024-09-29 0:57 ` Aron Insinga
2024-09-15 19:36 ` Ron Natalie
2024-09-16 5:36 ` Wesley Parish
2024-09-16 3:10 ` arnold
2024-09-16 3:30 ` George Michaelson
2024-09-16 10:41 ` Andy Kosela
2024-09-16 10:59 ` Edouard Klein
2024-09-16 20:55 ` Dan Cross
2024-09-16 21:05 ` Chet Ramey via TUHS
2024-09-13 0:26 Douglas McIlroy
2024-09-13 1:01 ` Luther Johnson
2024-09-13 2:20 ` segaloco via TUHS
2024-09-13 4:03 ` Eric E. Bowles via TUHS
2024-09-13 16:05 ` Åke Nordin
2024-09-13 7:13 ` G. Branden Robinson
2024-09-13 13:57 ` Will Senn
2024-09-13 16:12 ` Adam Thornton
2024-09-13 22:56 ` Will Senn
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='CAKzdPgxuErhhZvnfNF8u4KjL-p5nfmU-HztxyWUmLrE1dqs=UQ@mail.gmail.com' \
--to=robpike@gmail.com \
--cc=henry.r.bent@gmail.com \
--cc=tuhs@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).