RIAA Radar has a website that will let you search for artists, albums, keywords, etc and it will give you information as to whether or not an album was released under the RIAA.

So I did a view-source on their search page and determined that there are only three variables that you need to POST in order to search: searchtype, keyword, and submit.

I can use wget to grab the file, like so:
wget http://www.riaaradar.com/search.asp --post-data "searchtype=ArtistSearch&keyword=Audioslave&submit=Go\!" -O Audioslave

This saves the file as Audioslave. Audioslave IS represented by the RIAA, by the way.

Now, how do I take my ripped albums and compare them to the RIAA Radar site?

In my album collection, all of the albums are formatted the same: Artist – Album Name
This little bit of effort a long time ago makes it easy for me to separate these now.
I simply cd into my albums directory and do the following:
ls|awk '{FS="-"};{ print $1}'|uniq >> artists

I now have a file called artists in my album collection that contains unique artist names for every album in the collection.

Now, to find out if they’re represented by the RIAA:

cat artists|tr " " "+"|xargs -i wget http://www.riaaradar.com/search.asp --post-data "searchtype=ArtistSearch&keyword={}&submit=Go\!" -O radarresults{}.html

This will pull down the search result for every artist in my album list, and save it in a file formatted the way I want.
For instance, Jimi Hendrix would be saved as radarresultsJimi+Hendrix.html

I browse this with lynx and see that the text “Warning!” would be pretty good to search on.

grep Warning! radarresults*|sed -e 's/<[^<>]*>//g'|tr "+" " "|cut -c 13-|uniq|awk '{FS=".html"};{print $1}' >> riaapunks.txt

Explanation: grep searches the files for Warning!, then sed strips out the html. tr converts those + signs to spaces, cut trims off the radarresults portion of the output, uniq filters out duplicates, awk cuts off everything after and including .html, then it all gets dumped to a file.

Now I’ve got a nice list of everyone who is represented by the RIAA, in a file called riaapunks.txt

Now I get to have fun with it!
cat riaapunks.txt|xargs --verbose -i find ./ -name *{}*

Output looks good. Now for the coup de grace:
cat riaapunks.txt|xargs --verbose -i find ./ -name *{}* -delete

Buh-bye RIAA music!

xargs is a command of the Unix and most Unix-like operating systems which eases passing command output to another command as command line arguments.

It splits its often piped input at whitespaces (or the null character) and calls the command given as an argument with each element of the split input as parameter. If the parameter list is too long, it calls the program as often as necessary. It often covers the same functionality as the backquote feature of many shells, but is more flexible and often also safer, especially if there are blanks or special characters in the input.

This is often used in conjunction with the Unix commands find, locate and grep.

So, what can you do with xargs?

Well, let’s say you want to put up a torrent on a tracker, but you want to include a file with the MD5 checksums of every file. We’ll assume that the files you want to put on bittorrent are in /home/me/mytorrent/
To generate an MD5 sum of every file in the directory and dump it to a file, you can do the following:
find /home/me/mytorrent/ -type f|xargs md5sum >> /home/me/mytorrent/md5sums.txt

Now you’ve got a list of the MD5 sums for every file in the torrent you want to publish.

You can also use xargs to call grep to look inside files. For instance, if you’re editing a web page and you want to find all instances of a PHP class, you can execute the following:

find /home/me/mywebpage -name '*.php'|xargs grep -Hn adminClass

This will return a list of each file ending in php, and then for each item in the list, grep will check for the string adminClass. The -H flag will make sure that grep prints the filename in each match, and the -n flag will make grep print the line number as well.

xargs is an invaluable tool in command-line work because it prevents you from having to write a for or while loop in a shell script. xargs will run the command you specify on every line of output. Granted, find has an -exec capability, but xargs has its utility. Being slightly paranoid, you might like to check the output of a command before you pipe it to xargs or run an -exec in find. For instance, if you were removing everything in a cache directory, it would probably be better to pipe the find output to more first, and then after you have verified the output, you can pipe it to xargs rm -f -r

For usenet users, you can also use xargs to PAR check all of your files.

ls *.par2|xargs par -r

Windows users take heart, there is an xargs for windows in the Findutils package for Windows .

Have any other xargs tricks? Leave yours in the comments.