(Link) A History of Rock Music in 500 Songs

I don't remember exactly how I came across this podcast, but it should have been through somebody in my mastodon circle: https://500songs.com/

Anyways, I've now listened to two episodes (spread over a few sessions) and I'm blown away by the sheer amount of detail that you get to discover about the covered artist or song. And that explains why each episode is rather long, I think the two I listened to are over 2h each.

Music has always been an important part of my life and knowing trivia or facts about a certain artist, album or song has always been meaningful to me, in order to better appreciate the music and augment the listening experience.
If you feel the same you won't regret diving into this podcast.

The two episodes I listened to so far are:

https://500songs.com/podcast/episode-163-sittin-on-the-dock-of-the-bay-by-otis-redding/

I chose this one as incidentally I was listening to Otis Blue at the same time. I was amazed that the whole album was recorded in just 28 hours straight, with only a 4h break so that some musicians could perform their nightly gigs, and then back into studio again at 2AM.
I am again reminded of how much we owe to black musician and the absolutely incredible impact they have had on the music of the last 100 years. There's a book that covers that too, but I cannot recall its title right now.

The other one is https://500songs.com/podcast/episode-171-hey-jude-by-the-beatles/ as some kind of reparation to the Beatles (ironic, huh?). I've never felt a connection to the Beatles and I've never owned any record by them, and, feeling guilty of that, I wanted to give me a chance to better learn about them. Have to say I came out of the listening with a desire to give the white album a full listen, which I am now half-way through. Have to say, I'm really impressed by how clear it sounds on my (modest) system.

Popular posts

A not so short guide to ZFS on Linux

Image
Updated Oct 16 2013: shadow copies, memory settings and links for further learning. Updated Nov 15 2013: shadow copies example, samba tuning. Unless you've been living under a rock you should have by now heard many stories about how awesome ZFS is and the many ways it can help with saving your bacon . The downside is that ZFS is not available (natively) for Linux because the CDDL license under which it is released is incompatible with the GPL. Assuming you are not interested in converting to one of the many Illumos distributions or FreeBSD this guide might serve you as a starting point if you are attracted  by ZFS features but are reluctant to try it out on production systems. Basically in this post I note down both the tought process and the actual commands for implementing a fileserver for a small office. The fileserver will run as a virtual machine in a large ESXi host and use ZFS as the filesystem for shared data.
Read more

Indexing Apache access logs with ELK (Elasticsearch+Logstash+Kibana)

Image
Who said that grepping Apache logs has to be boring? Sample of dashboard that can be created with ELK. Pretty impressive, huh? The truth is that, as Enteprise applications move to the browser too, Apache access logs are a gold mine, it does not matter what your role is: developer, support or sysadmin. If you are not mining them you are most likely missing out a ton of information and, probably, making the wrong decisions. ELK (Elasticsearch, Logstash, Kibana) is a terrific, Open Source stack for visually analyzing Apache (or nginx) logs (but also any other timestamped data).
Read more

Mirth: recover space when mirthdb grows out of control

I was recently asked to recover a mirth instance whose embedded database had grown to fill all available space so this is just a note-to-self kind of post. Btw: the recovery, depending on db size and disk speed, is going to take long. The problem A 1.8 Mirth Connect instance was started, then forgotten (well neglected, actually). The user also forgot to setup pruning so the messages filled the embedded Derby database until it grew to fill all the available space on the disk. The SO is linux. The solution First of all: free some disk space so that the database can be started in embedded mode from the cli. You can also copy the whole mirth install to another server if you cannot free space. Depending on db size you will need a corresponding amount of space: in my case a 5GB db required around 2GB to start, process logs and then store the temp files during shrinking. Then open a shell as the user that mirth runs as (you're not running it as root, are you?) and cd in
Read more