If you are running Redhat/CentOS and want to rename your network interface, this is how I get it done. It doesn’t come up too often, but when it does it can be frustrating if you don’t cover your bases.

Down each interface you want to rename. You may need to do it from the console (Since you may lose your network connection):

Edit the NIC names to be sure it doesn’t add duplicates when UDEV on the next reboot

Open each ifcfg-em* file and edit the “DEVICE” name to match the new interface name.

Rename the /etc/sysconfig/network-scripts/ifcfg-* file to match the new interface name

Credit for this goes to https://kernelpanik.net/rename-a-linux-network-interface-without-udev/ for the initial rename method, but i experienced some issues with UDEV duplicating the NICs, and for hard coded configurations, the network either failed to start on reboot or the NIC was reverted back to the old name after a reboot.


I just started using Atom as my primary editor (I absolutely love it), and i went package crazy. I was reading an article and decided to try git-time-machine which is a neat way to look at the commit history in a visual plot style.

Image was borrowed from the project page: https://github.com/littlebee/git-time-machine

I was excited, but I ran into an error where git-time-machine was reporting:

Welp, I figured it was because git was not in my path (windows) so i checked by opening a command prompt, typing git and the command worked without a problem. So i went to the git-time-machine page, but it only mentions that the: “git command line utility needs to be in your path”, which it was. So i added it to my Windows path variable again, but that still didn’t help. Well, like most things the fix was simple, just tell Atom where your git projects are stored and it will work!

The Fix:

The error is misleading, since git is actually a working command. To fix it in Atom go to settings, and set the “Project Home” option to the place where you keep your Git projects. Then you will have beautiful visually plotted git history that you can fly through faster than you would believe!



Quick and easy way to change your Sublime folder theme to something a little more visually pleasing and easier to click. There are probably a bunch of themes out there, but i like the “Flatland” theme. Here’s how to install it.

Flatland example

Install Package Control for Sublime

ctrl+shift+p (Win, Linux) or cmd+shift+p (OS X) and type “Package Control: Install Package”. (Or just go to Preferences > Package Control: > Install Package.)

In the box that pops up just type “Flatland” and click it.

Once that finishes successfully, just open your user settings (Prefernces> User – Settings) and replace the theme line with this


Last thing to do is go to Preferences > Color Scheme > Theme – Flatland  and choose the theme you want.

If you reached this page you probably already know that PiAware is a Raspberry Pi based ADS-B ground station that enables you to track and plot aircraft within range. If you setup this up and have it working, awesome. I ran into an issue where i needed to change the port number that the web interface listens on.


image credit: flightaware.com
image credit: www.flightaware.com

1) ssh to your piaware (raspberry pi) with either the pi user or your user account you created. If you didnt create an account, the default username is “pi” and the password is “raspberry”

2) modify the init script that starts dump1090

3) on line 13 in the PROG_ARGS variable add this to the end:

So it should look something like this when you are done:

4) Thats it! Restart dump1090 by either rebooting the pi or:


RIAK is an easy to use, fault tolerant decentralized database architecture that’s great for many different storage applications. Once you get it going its virtually maintenance free and its rock solid. Its easy to expand and has a pretty good looking admin interface as well!

Sometimes in testing, building or rebuilding RIAK nodes, the RIAK daemon just doesn’t want to start. This issue has come up numerous times while dealing with RIAK setups so i wanted to get something out there and hopefully help someone else that deals with some of the same issues. At the moment I’m running RIAK version 1.4 on Centos 6.3, and although it seems Basho fixes a lot of these issues over time, there are still some lingering ones that I still bump into pretty often.

And… you get an error similar to the following:

If you followed the instructions to setup RIAK step by step, the first thing you should do is run:

  1. Make sure that output has nothing obvious that you can check. After that here are a few more things you can check:
  2. Ensure all log directories are writable by the RIAK user. I’m not sure why, but RIAK seems to want write access to /var/log/riak as well as platform_log_dir in app.config but wont tell you this in the console output when it has problems writing to the directory. It really should, but it doesn’t.
  3. Ensure any certificates you have specified in app.config exist where they should and are readable by the RIAK user
  4. Clear out the /tmp/riak folder and ensure the RIAK user has write access to /tmp to create the directory. If its able to create the directory it should be OK, but sometimes removing this will delete any locks causing RIAK not to start. (Thanks to Nathan Evans) To fix this just run:

Some additional stuff:

Check permissions on the data directories as well, if these have incorrect permissions you should probably either delete them if its a new installation or just:

Make sure there are no other processes being run by RIAK, if there are kill them:

Then restart riak

To verify things are up to snuff, consider [installing and] running Riaknostic to detect more errors and find suggestions for improvement:


Feel free to comment with what may have worked for you and i will gladly add it to this post and give credit!