This article is excerpted from chapter 4 of
  • macniel@feddit.org
    5·
    12 days ago

    Huh…

    First the site isn’t optimised for mobile, those codeblocks are cut off.

    Second in the last example why does the author rely on pv when dd has a status flag to display its progress already?

  • stoy@lemmy.zip
    3·
    12 days ago

    I have used dd a few times without destroying my disk, here is my simple recommendation to stay safe:

    DON’T TYPE THE COMMAND DIRECTLY INTO THE TERMINAL!

    What I mean is that you should open a text editor, type the dd command you want to run in the editor, let it sit for 5 min, go back to the text editor, find the OF path, doublecheck and verify that it is safe.

    Correct misstakes, wait another 5 min and do the check again.

    Once you are confident that the command is accurate, copy paste it into a terminal and run it.

    • seaQueue@lemmy.world
      7·
      12 days ago

      I use dd regularly to back up and restore disk images. It’s not particularly hard to use but like sudo rm -rf it absolutely will eat whatever you point it at so you need to understand what the command does and pay attention.

    • ulterno@programming.devEnglish
      1·
      11 days ago

      Once, while typing a dd command, I realised I was sleepy.
      I deferred until next day.

      Usually I keep partitionmanager open alongside, to cross-check my device selection.
      Unlike having to use other CLI tools to determine if I have it right, I get some handy icons (like the USB drive symbol). Still, make sure to check the contents just in case it got bugged and set the icon to the wrong type of drive.