source

img title=“I don’t know what’s worse–the fact that after 15 years of using tar I still can’t keep the flags straight, or that after 15 years of technological advancement I’m still mucking with tar flags that were 15 years old when I started.”

  • Krafty Kactus@sopuli.xyz
    link
    fedilink
    English
    arrow-up
    3
    ·
    7 months ago

    A little trick I learned on here was to imagine yourself as a little evil man saying “Extract ze files!” in a German accent. Extract ze files >>> xzf.

    • Tb0n3@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      1
      ·
      7 months ago

      Only works for tar.gz. Remember there’s also tar.xz, tar.bz, tar.bz2 and half have their own extractor flag. FUN. It’s usually J.

  • fubo@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    7 months ago

    If you can’t tar to a pipe into ssh to a remote host and untar into an arbitrary location there, are you really using Unix?

    • LostXOR@fedia.io
      link
      fedilink
      arrow-up
      2
      ·
      7 months ago

      I had to pipe dd through gzip over SSH recently to locally image a disk on a cloud server. That was fun.

  • csm10495@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    7 months ago

    Normally I would say view the man page (as a command). Though for some reason when making the thinnest distro possible, the OS team at my job got rid of man.

    Wtf man.

    • chellomere@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      7 months ago

      Then comes a .tar.bz2 file along and you’re screwed. xtract je vucking file?

      Pro tip: -z, -j are not needed by tar anymore since many years, tar will autodetect what compression was used if your distro is anything remotely modern.

      • allywilson@sopuli.xyz
        link
        fedilink
        arrow-up
        1
        ·
        7 months ago

        Pro tip: -z, -j are not needed by tar anymore since many years, tar will autodetect what compression was used if your distro is anything remotely modern.

        😵

      • aard@kyu.de
        link
        fedilink
        arrow-up
        1
        ·
        7 months ago

        You still might want to do something like alias pbtar='tar --use-compress-prog=pbzip2 to easily use pbzip2 - unless you have an ancient system that’ll speed things up significantly. And even if you don’t it’d be nice to use it for creation - to utilize more than one core the archive needs to be created for parallel extraction.

  • kevincox@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    7 months ago

    I know this is a meme, but I actually find tar fairly easy to remember.

    tar -xf $archive is extract file

    tar -czf $archive dir/ is create zipped (compressed) file and the positional arguments are the files to add to the archive.

    And this is 99% of my usage. You can skip -f $archive to use stdin/stdout or use -C to change directory (weird name but logically tar always extracts to the current directory). There is also a flag to list which I always forget and lookup each time, but I list much less often. -v is useful for verbose.

    Overall there are much harder commands to remember. find always gets me if I go beyond -name. ps, tree and ls (beyond -Al) always get me to open the man page.

    • Russ@bitforged.space
      link
      fedilink
      English
      arrow-up
      1
      ·
      7 months ago

      There is also a flag to list which I always forget and lookup each time

      That would be -t, which I tend to remember as “test”, as in testing to see what is inside the archive!

      tealdeer is a great program to have installed for easily getting a breakdown of the flags of pretty much any CLI app that at least I can ever think of!