The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Michael Kjörling" <michael@kjorling.se>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] PDP-7 UNIX filesystem
Date: Fri, 25 Oct 2019 21:08:04 +0000	[thread overview]
Message-ID: <z3t7qn97mscfnkwgvbrdb9rb@localhost> (raw)
In-Reply-To: <496001dc0ab086a1e2d6d3a5f47dc5f1@bl.org>

On 23 Oct 2019 21:23 -0500, from mparson@bl.org (Michael Parson):
>>>> dd is deprecated?  I'm surprised. I use it all the time.
>>> 
>>> I don't think so. A quick google search doesn't support that.
>> 
>> dd isn't deprecated. There's no heir apparent, it's in POSIX.1 and
>> there's no advantage to changing. There's not even been talk of that,
>> at east in *BSD land.

The only thing resembling "deprecation" of dd that I'm aware of is the
recommendation I saw many years ago to not use it to copy potentially
problematic storage media (for data recovery), but to use ddrescue for
that purpose instead. The reason for this is that with conv=noerror
(without which it'd simply abort if it encounters an I/O error), dd
would simply skip past data in the input that it can't read, but not
adjust any offsets in the output, which wreaks havoc with anything
where offsets matter (such as in file system metadata).


> I'm sure the systemd people are eyeballing it.

That wouldn't surprise me in the slightest.

-- 
Michael Kjörling • https://michael.kjorling.se • michael@kjorling.se
  “The most dangerous thought that you can have as a creative person
              is to think you know what you’re doing.” (Bret Victor)


  reply	other threads:[~2019-10-25 21:08 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 [this message]
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
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=z3t7qn97mscfnkwgvbrdb9rb@localhost \
    --to=michael@kjorling.se \
    --cc=tuhs@minnie.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).