x/l/c - extract/list/create
v - verbose
z/j - some sort of compression
f - file ... the next argument that follows is a tar filename of some sort.
Both of these are the same:
Code:
tar -xjvf somename.tar.bz2
tar xjvf somename.tar.bz
Same for
Code:
tar -xzvf somename.tar.gz
tar xzvf somename.tgz
Tack or without it (dash) don't matter. This is left over from the sysV or BSD differences in options.
I don't think the extensions matter, since in Unix extensions are for humans. The computer doesn't care. It will use the "magic number" to determine the type of file. In user-land, we can use the 'file' command.
Code:
$ file somename.tar.bz2
will show what a file is.
Code:
$ file The_Linux_Command_Line-William_Shotts.pdf
The_Linux_Command_Line-William_Shotts.pdf: PDF document, version 1.5
Simple, handy and correct.
Not that there's anything wrong with getting the source code, but why not just use the APT repo version?
Looks like there are a few packages. To find the package for your system, use
Code:
sudo apt search dvdcs
restricted-extras and perhaps libdvdread4 and libdvdread8 are showing in the list returned here.
Update: I used "dvdcs" because it was short, contained enough of the library. There is a special feel for how many characters to use when searching anything, including google.
"dvd" would not have been sufficiently specific. Too general.
"libdvdcss-1.4.3" would have been too specific and wouldn't likely find much on different OSes.
Somewhere between those guesses, dvdcs, is easy for human to see, quickly review and decide what is likely the best choice in the results.
Nothing magical about that. Just needs to be part of the package description, somewhere.
Bookmarks