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.

  • tomenzgg@midwest.social
    link
    fedilink
    English
    arrow-up
    30
    ·
    8 hours ago

    New Linux util.

    looks inside

    Non-copyleft license

    I appreciate that it’s not trying to replace cp but the lack of copyleft is always disconcerting.

    • Badabinski@kbin.earth
      link
      fedilink
      arrow-up
      6
      ·
      6 hours ago

      yeah, like, supposedly it can be hard to use GPL with some rust dependencies, but the MPL is right there as a decent compromise.

    • macniel@feddit.org
      link
      fedilink
      arrow-up
      1
      ·
      3 hours ago

      Welcome to rust where MIT is just recommended yet everyone does use it for licensing.

    • sin_free_for_00_days@sopuli.xyz
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 hours 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.

    • onlinepersona@programming.dev
      link
      fedilink
      arrow-up
      10
      arrow-down
      2
      ·
      8 hours 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.