The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Christopher Browne <cbbrowne@gmail.com>
To: Abhinav Rajagopalan <abhinavrajagopalan@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] PDP-7 UNIX filesystem
Date: Wed, 23 Oct 2019 22:29:42 -0400	[thread overview]
Message-ID: <CAFNqd5WWCpiDodVxVJ-pEWDcLcgThckFuSUKORJiNX+JuJX7Zw@mail.gmail.com> (raw)
In-Reply-To: <CANOZ5riWWibJ4OY8SnZ7q_o1VaMRFq_-1yXedq2PMXupc1ckMA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2350 bytes --]

On Mon, 21 Oct 2019 at 06:45, Abhinav Rajagopalan <
abhinavrajagopalan@gmail.com> wrote:

>
>>
> Since you mentioned the word dd, the utility which serves me like none
> other for my frequent rewrites of images, it too has an interesting past,
> it seems like 'dd' was non-unixy in it's design approach, if I'm to believe
> the lores around, which leads me to think that this might have been another
> one of the many idiosyncratic naming conventions used back then. More on
> the dd stuff: http://www.catb.org/jargon/html/D/dd.html
>
> Personally, I just like to think of it in my head as disk-disk.
>

I am pretty sure that "dd" derives from  the "DD" statement in IBM JCL that
stands for "Data Definition"

Here's a link to practical-ish documentation about that:
https://www.ibm.com/support/knowledgecenter/zosbasics/com.ibm.zos.zjcl/zjclc_jclDDstmt.htm

On MVS, TSO, and such systems, compiled programs would be written in
languages like COBOL, PL/1, FORTRAN, and such, and the programs would
commonly reference input and output devices.  The programs are controlled
(we could say, "scripted") by JCL code that indicate the files (possibly
other devices) to be connected up.  Each file that is accessed gets its own
DD line in the JCL script that indicates the various metadata about the
file, such as its name, block size, storage class, how much space is
allocated, literally dozens of options.

Back in the '90s my "Y2K remediation" involvement was at American Airlines;
I was one of the Unix guys working alongside mainframe guys; as soon as I
started seeing the JCL for their TSO batch jobs, it was pretty obvious that
this was from whence derived the dd command on Unix.  The mainframe guys
enthused a lot about a sorting tool with similar syntax called SyncSort
that they'd use to do many of the things we'd do with cut and grep.

The Jargon File claim that dd is deprecated makes little sense; dd is THE
good tool for grabbing exact chunks of data out of binary files, and I
haven't seen a would-be successor.  It would be interesting to see some
alternative constructed; given that it's all about dealing with pretty
messy sorts of I/O work, an alternative is liable to have its messiness in
different places.
-- 
When confronted by a difficult problem, solve it by reducing it to the
question, "How would the Lone Ranger handle this?"

[-- Attachment #2: Type: text/html, Size: 3591 bytes --]

  parent reply	other threads:[~2019-10-24  2:30 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21  6:22 Angelo Papenhoff
2019-10-21 10:43 ` Abhinav Rajagopalan
2019-10-21 11:38   ` Abhinav Rajagopalan
2019-10-21 12:00     ` Thomas Paulsen
2019-10-21 13:31       ` Abhinav Rajagopalan
2019-10-22 18:07   ` Peter Jeremy
2019-10-23  0:07     ` Mary Ann Horton
2019-10-23  2:02       ` Kurt H Maier
2019-10-23  2:19         ` Larry McVoy
2019-10-23  8:34       ` Thomas Paulsen
2019-10-24  0:06         ` Warner Losh
2019-10-24  2:23           ` Michael Parson
2019-10-25 21:08             ` Michael Kjörling
2019-10-25 21:34               ` Arthur Krewat
2019-10-25 21:50                 ` reed
2019-10-25 22:54                 ` Warner Losh
2019-10-24  2:29   ` Christopher Browne [this message]
2019-10-24  8:25     ` Thomas Paulsen
2019-10-21 16:54 ` Angelo Papenhoff
2019-10-23  5:48 ` Lars Brinkhoff
2019-10-21 11:58 Noel Chiappa
2019-10-21 15:44 ` Abhinav Rajagopalan
2019-10-22  2:09 ` Jaap Akkerhuis
2019-10-23  2:00   ` Christopher Browne

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=CAFNqd5WWCpiDodVxVJ-pEWDcLcgThckFuSUKORJiNX+JuJX7Zw@mail.gmail.com \
    --to=cbbrowne@gmail.com \
    --cc=abhinavrajagopalan@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).