• ZeroOne@lemmy.world
    3·
    1 day ago

    We seriously need a series of DD-Command 4 Dummies guides<br> Also you guys have USB drives with lights ???

  • debil@lemmy.world
    26·
    2 days ago

    Commands like dd are the best. Good ole greybeard-era spells with arcane syntax and the power to casually wipe out the whole universe (from their perspective ofc) if used haphazardly or not in respectful manner.

  • waigl@lemmy.world
    46·
    3 days ago

    IMHO, it was a mistake to make USB block storage use the same line of names also used for local hard disks. Sure, the block device drivers for USB mass storage internally hook into the SCSI subsystem to provide block level access, and that’s why the drives are called sd[something], but why should I as an end user have to care about that? A USB drive is very much not the same thing for me as a SCSI harddisk. A NVMe drive on the other hand, kinda sorta is, at least from a practical purpose point of view, yet NVMe drives get a completely different naming scheme.

    That aside, suggest you use lsblk before dd.

    • BCsven@lemmy.ca
      13·
      3 days ago

      Yeah lsblk, lsscsi, fdsik -l , go have a coffee, come back later and hit enter on dd

      • Cenzorrll@lemmy.world
        5·
        2 days ago

        Yeah lsblk, lsscsi, fdsik -l , go have a coffee, come back later and hit enter on dd

        Then realize you typed the command wrong and panic when you don’t get an error.

    • grue@lemmy.worldEnglish
      5·
      3 days ago

      While we’re at it, can we also rename the hard drive block devices back to hd instead of sd again? SATA might use the SCSI subsystem, but SATA ain’t SCSI.

  • muhyb@programming.dev
    33·
    3 days ago

    Always lsblk before dd. The order of /sdX might change from boot to boot. Only /nvme doesn’t change.

    • ReginaPhalange@lemmy.world
      1·
      7 hours ago

      First thing I do after loading the liveusb is write the “mylsblk” which does the much more sane thing of:

      lsblk -o NAME,LABEL,PARTLABEL,UUID,SIZE,MOUNTPOINTS
      • muhyb@programming.dev
        9·
        2 days ago

        It’s a design thing. BIOS can know NVMe disks’ location because they’re directly mounted to PCIe. SATA isn’t like this. Similar logic with the RAM slots.

  • SaltyIceteaMaker@lemmy.ml
    5·
    3 days ago

    worst case for me would be ereasing my ventoy drive.

    cause i for sure wont be partitioning any of my nvme drives. so the only mistake i can make is like type sda instead of sdb which would just be another usb drive🤷

    • Possibly linux@lemmy.zipEnglish
      2·
      3 days ago

      I want a immutible Linux that restricts access to critical components. I wouldn’t mind running my desktop in a container.

      • iopq@lemmy.world
        2·
        3 days ago

        NixOS store (app folder) is read only. You literally can’t mess with it. It doesn’t really need a container, most things are locked down already. Of course you could mess up your home folder, but that’s on you then

  • philluminati@lemmy.ml
    4·
    3 days ago

    ls /dev > /tmp/before

    <insert usb>

    ls /dev > /tmp/after

    <repeat two more times>

    diff /tmp/before /tmp/after

    <sweating>