6 ms·
nope, that would be handling tar balls ffmpeg right after
by jeanlucas 1y ago
nope, that would be handling tar balls
ffmpeg right after
- porridgeraisin 1y agoPersonally I never understood the problem with tar balls. The only options you ever need are tar -x, tar -c (x for extract and c for create). tar -l if you wanna list, l for list. That's really it, -v for verbose just like every other tool if you wish. Examples: tar -c project | gzip > backup.tar.gz cat backup.tar.gz | gunzip | tar -l cat backup.tar.gz | gunzip | tar -x You never need anything else for the 99% case.
- drivers99 1y agoExcept it's tar -t to list, not -l
- porridgeraisin 1y agoWhoops, lol. Well that's unfortunate.
- sdfsdfgsdgg 1y ago> tar -l if you wanna list, l for list. Surely you mean -t if you wanna list, t for lisT. l is for check-Links. -l, --check-links (c and r modes only) Issue a warning message unless all links to each file are archived. And you don't need to uncompress separately. tar will detect the correct compression algorithm and decompress on its own. No need for that gunzip intermediate step.
- porridgeraisin 1y ago> -l Whoops, lol. > on its own Yes.. I'm aware, but that's more options, unnecessary too, just compose tools.
- sdfsdfgsdgg 1y agoThat's the thing. It’s not more options. During extraction it picks the right algorithm automatically, without you needing to pass another option.
- bigstrat2003 1y agoThe problem is it's very non-obvious and thus is unnecessarily hard to learn. Yes, once you learn the incantations they will serve you forever. But sit a newbie down in front of a shell and ask them to extract a file, and they struggle because the interface is unnecessarily hard to learn.
- encom 1y agoIt's very similar to every other CLI program, I really don't understand what kind of usability issue you're implying is unique to tar?
- mrguyorama 1y agoAs has been clearly demonstrated in this very thread, why is "Please list what files are in this archive" the option "-t"? Principle of least surprise and all that.
- encom 1y agoAnd why is -v the short option for --invert-match in grep, when that's usually --verbose or --version in lots of other places. These idiosyncrasies are hardly unique to tar.
- tombert 1y agoYeah I never really understood why people complain about tar; 99% of what you need from it is just `tar -xvf blah.tar.gz`.
- aidenn0 1y agoYou for got the -z (or -a with a recent gnutar).
- adastra22 1y agoIt’s no longer needed. You can leave it out and it auto-detects the file format.
- CamperBob2 1y agoWhat value does tar add over plain old zip? That's what annoys me about .tar files full of .gzs or .zips (or vice versa) -- why do people nest container formats for no reason at all? I don't use tape, so I don't need a tape archive format.
- diggernet 1y agoA tar of gzip or zip files doesn't make sense. But gzipping or zipping a tar does. Gzip only compresses a single file, so .tar.gz lets you bundle multiple files. You can do the same thing with zip, of course, but... Zip compresses individual files separately in the container, ignoring redundancies between files. But .tar.gz (and .tar.zip, though I've rarely seen that combination) bundles the files together and then compresses them, so can get better compression than .zip alone.
- fullstop 1y agozip doesn't retain file ownership or permissions.
- diggernet 1y agoGood point. And if I remember right, tar allows longer paths than zip.
- jeanlucas 1y agoit was just a reference to xkcd#1168 I wasn't expecting the downvotes for an xkcd reference
- BeepInABox 1y agoFor anyone curious, unless you are running a 'tar' binary from the stone ages, just skip the gunzip and cat invocations. Replace .gz with .xz or other well known file ending for different compression. Examples: tar -cf archive.tar.gz foo bar # Create archive.tar.gz from files foo and bar. tar -tvf archive.tar.gz # List all files in archive.tar.gz verbosely. tar -xf archive.tar.gz # Extract all files from archive.tar.gz
- mkl 1y ago> tar -cf archive.tar.gz foo bar This will create an uncompressed .tar with the wrong name. You need a z option to specify gzip.
- Intermernet 1y agoApparently this is now automatically determined by the file name, but I still habitually add the flag. 30 years of muscle memory is hard to break!
- mkl 1y agoI tried it to check before making the comment. In Ubuntu 25.04 it does not automatically enable compression based on the filename. The automatic detection when extracting is based on file contents, not name.
- BenjiWiebe 1y agoIf you add a for auto, it will choose the right compression based on the file name. tar -caf foo.tar.xz foo Will be an xz compressed tarball.
- themafia 1y agogzip -dc backup.tar.gz | tar -x You can skip a step in your pipeline.
- sho_hn 1y agonope, it's using `find`.
- beala 1y agoTough crowd. fwiw, `tar xzf foobar.tgz` = "_x_tract _z_e _f_iles!" has been burned into my brain. It's "extract the files" spoken in a Dr. Strangelove German accent Better still, I recently discovered `dtrx` (https://github.com/dtrx-py/dtrx https://github.com/dtrx-py/dtrx) and it's great if you have the ability to install it on the host. It calls the right commands and also always extracts into a subdir, so no more tar-bombs. If you want to create a tar, I'm sorry but you're on your own.
- diggan 1y agoI used tar/unzip for decades I think, before moving to 7z which handles all formats I throw at it, and have the same switch for when you want to decompress into a specific directory, instead of having to remember which one of tar and unzip uses -d, and which one uses -C. "also always extracts into a subdir" sounds like a nice feature though, thanks for sharing another alternative!
- mkl 1y ago> tar xzf foobar.tgz You don't need the z, as xf will detect which compression was used, if any. Creating is no harder, just use c for create instead, and specify z for gzip compression: tar czf archive.tar.gz [filename(s)] Same with listing contents, with t for tell: tar tf archive.tar.gz
- fullstop 1y agoI have so much of tar memorized. cpio is super funky to me, though.
- fuzztester 1y agocpio is not that hard. A common use case is: $ cpio -pdumv args See: $ man cpio and here is an example from its Wikipedia page, under the "Operation and archive format" section, under the Copy subsection: Copy Cpio supports a third type of operation which copies files. It is initiated with the pass-through option flag (p). This mode combines the copy-out and copy-in steps without actually creating any file archive. In this mode, cpio reads path names on standard input like the copy-out operation, but instead of creating an archive, it recreates the directories and files at a different location in the file system, as specified by the path given as a command line argument. This example copies the directory tree starting at the current directory to another path new-path in the file system, preserving files modification times (flag m), creating directories as needed (d), replacing any existing files unconditionally (u), while producing a progress listing on standard output (v): $ find . -depth -print | cpio -p -dumv new-path
- fullstop 1y agoI think that it's the fact that it requires a pipe to work and that you add files by feeding stdin that throw me for a loop. I also use it very infrequently compared to tar -- mostly in conjunction with swupdate. I've also run into file size limits, but that's not really a function of the command line interface to the tool.