A new Rust-based tool called cpx offers a modern alternative to the traditional cp command on Linux, adding parallel copying, progress bars, resume support, and configurable defaults.

As we all know, file copying on Linux has long relied on the classic cp command, which remains reliable but offers little feedback and limited control over long or complex operations.

To address this, a promising new Rust-based command-line tool called cpx emerge, designed as an alternative rather than a replacement, that approaches the same task with a focus on performance, visibility, and configurability.

It targets scenarios where large directory trees, interrupted transfers, or the need for detailed progress reporting make standard tools less convenient to use. The project is currently Linux-only and leverages modern kernel features to improve copy throughput and reliability.

    • onlinepersona@programming.dev
      182·
      2 days ago

      It’s a damn pain to remember all the flags. How many flags can a program friggin have? I’m always afraid that some flag I enter will reverse the sync and delete everything in the source folder because the target is empty.

      I use rsync only when all params have been reseasrched and tested. cpx presumably just requires cpx - r source target instead of 5 rsync flags.

      • pinball_wizard@lemmy.zip
        2·
        21 hours ago

        I’m always afraid that some flag I enter will reverse the sync and delete everything in the source folder because the target is empty.

        A version of rsync without this risk would be a killer app. Haha.

      • frongt@lemmy.zip
        121·
        1 day ago

        The only one you need is -a. -avz if you want verbose and compression.

        • onlinepersona@programming.dev
          2·
          2 days ago

          I just looked it up and - x means one filesystem. But does - v give you a progress bar or just a lost of stuff copied?

          IIRC rsync also treats the trailing slash in a special manner that I always have to look up.

          • cyrl@lemmy.world
            3·
            1 day ago

            The trailing slash is just following cp’s own special treatment

            
# before
dir/
    file1
target/
    orig.txt



# no trailing slash - copy *dir* to target
cp -r /path/to/some/dir /my/target

# after
target/
    orig.txt
    dir/            # dir copied to target
        file1



# with trailing slash - copy *contents* of dir to target
cp -r /path/to/some/dir/ /my/target

# after
target/
    orig.txt
    file1            # contents of dir
          • frongt@lemmy.zip
            21·
            1 day ago

            Ha. I meant z. I guess I was getting mixed up with tar.

            No slash means the directory. Slash means the items in the directory.

      • Victor@lemmy.world
        7·
        2 days ago

        What 5 flags did rsync need? I always just do -av and go about my day. And the -v is kinda optional.

    • sin_free_for_00_days@sopuli.xyzEnglish
      4·
      2 days ago

      I’ve had cp aliased to rsync with my flags for years. It seems like a lot of newcomers try to “fix” stuff before they really understand what’s available. Or they just like to play around with different programming languages. Which is fine, but usually it’s not really interesting to me.

      • brian@programming.dev
        1·
        4 hours ago

        you seem to have added a condescending comment before you understood the goals. 2-5x speedup over rsync (their benchmarks, but still) seems significant on its own, and an interface that doesn’t require aliasing to be useful is also nice