<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Aaron Hastings</title><link>https://blog.aaronhastings.me/</link><description>Recent content on Aaron Hastings</description><generator>Hugo</generator><language>en-ie</language><lastBuildDate>Wed, 12 Aug 2015 12:00:09 +0000</lastBuildDate><atom:link href="https://blog.aaronhastings.me/index.xml" rel="self" type="application/rss+xml"/><item><title>Installing New Relic Servers on openSUSE</title><link>https://blog.aaronhastings.me/installing-new-relic-servers-on-opensuse/</link><pubDate>Wed, 12 Aug 2015 12:00:09 +0000</pubDate><guid>https://blog.aaronhastings.me/installing-new-relic-servers-on-opensuse/</guid><description>New Relic Servers is an excellent cloud-based server monitoring platform. I maintain a set of servers, both physical and virtual, running a range of operating systems, namely: Debian 7/8, Ubuntu 14.04, CentOS 6/7 and openSUSE 13.2. I work with configuration management (particularly Salt), so maintaining multiple configurations is important in understanding complex environments.
New Relic already provides packages for Debian/Ubuntu, Red Hat, Joyent SmartOS and Windows. For some reason, openSUSE doesn&amp;rsquo;t get the royal treatment, but they do provide the requisite package files in a tar.</description></item><item><title>Scroll wheel functionality in GNU Screen</title><link>https://blog.aaronhastings.me/scroll-wheel-functionality-in-gnu-screen/</link><pubDate>Thu, 16 Apr 2015 19:00:30 +0000</pubDate><guid>https://blog.aaronhastings.me/scroll-wheel-functionality-in-gnu-screen/</guid><description>GNU Screen is one of my biggest time savers in work. It allows me to handle multiple shell and SSH sessions in one virtual terminal, and ensures those sessions stay alive even when I lose network connection due to switching access points, plugging in to a wired network or just general network issues, uh-ohs and whoopsies.
Screen works pretty well &amp;ldquo;out of the box&amp;rdquo;, as long as you learn a handful of essential commands/key bindings, like Ctrl+A+D (detach from session), screen -r session-name (re-attach to existing session) and Ctrl+A+numkey, where numkey represents a particular session.</description></item><item><title>Completely recovering from a "bricked" Buffalo LinkStation LS200-series NAS (and opening the firmware too!)</title><link>https://blog.aaronhastings.me/completely-recovering-from-a-bricked-buffalo-linkstation-ls200-series-nas-and-opening-the-firmware-too/</link><pubDate>Tue, 17 Mar 2015 17:03:43 +0000</pubDate><guid>https://blog.aaronhastings.me/completely-recovering-from-a-bricked-buffalo-linkstation-ls200-series-nas-and-opening-the-firmware-too/</guid><description>I recently bought a Buffalo LinkStation LS220 NAS (network-attached storage) device. The device itself is a good quality piece of hardware, but the software leaves a lot to be desired. I bought this NAS purely as a redundant (i.e. RAID1) backup solution and intended to use it as an SSH server for my rsync backup scripts.
Much to my disappointment, however, the firmware came far more locked-down than I had hoped, and provided no means to (easily) enable SSH.</description></item><item><title>Updating to Android 5.1.0/5.1.1 on rooted Nexus 5</title><link>https://blog.aaronhastings.me/updating-to-android-5-1-0-on-rooted-nexus-5/</link><pubDate>Wed, 11 Mar 2015 17:45:21 +0000</pubDate><guid>https://blog.aaronhastings.me/updating-to-android-5-1-0-on-rooted-nexus-5/</guid><description>Updated (2015-05-29) - I have tested this method successfully with Android 5.1.1 and have updated the post title/content to reflect this.
Does this post look familiar?
I wrote a post back in December 2014 solving this same problem for Android 5.0.1, whereby a rooted Nexus device will not update via over-the-air (OTA). Rather than go over everything again, I&amp;rsquo;ll cut straight to the chase of how to update your rooted Nexus 5 to Android 5.</description></item><item><title>Updating to Android 5.0.1 on rooted Nexus 5</title><link>https://blog.aaronhastings.me/updating-to-android-5-0-1-on-rooted-nexus-5/</link><pubDate>Fri, 19 Dec 2014 17:53:45 +0000</pubDate><guid>https://blog.aaronhastings.me/updating-to-android-5-0-1-on-rooted-nexus-5/</guid><description>OTA (over-the-air) updating in rooted Nexus land has never been the most elegant process. But, prior to Android 5.0 Lollipop, at least it worked as expected, with the main irk being that you&amp;rsquo;d need to re-root your device afterwards.
While trying to update to Android 5.0.1 on my rooted Nexus 5 via OTA today, I discovered that things are now even less clear-cut and that the update itself will now fail during the recovery phase.</description></item><item><title>Who's trying to break in to your Linux box?</title><link>https://blog.aaronhastings.me/whos-trying-to-break-in-to-your-linux-box/</link><pubDate>Tue, 16 Dec 2014 00:08:10 +0000</pubDate><guid>https://blog.aaronhastings.me/whos-trying-to-break-in-to-your-linux-box/</guid><description>Fun with pipes! Just a quick Bash snippet for getting a good look at who&amp;rsquo;s attempting to log in to your Linux or other standard GNU system:
#shell&amp;gt; lastb -w | sort | awk '{print $1, &amp;quot;\t&amp;quot;, $3}' | uniq | less Here&amp;rsquo;s a quick summary of what&amp;rsquo;s going on here:
lastb reads and echoes the contents of the failed login database, generally located at /var/log/btmp. The -w flag just ensures it doesn&amp;rsquo;t ellipse or otherwise cut-off the username field.</description></item><item><title>uLuas - Developing a real-time Luas app for Ubuntu</title><link>https://blog.aaronhastings.me/uluas-developing-a-real-time-luas-app-for-ubuntu/</link><pubDate>Tue, 21 Jan 2014 19:32:11 +0000</pubDate><guid>https://blog.aaronhastings.me/uluas-developing-a-real-time-luas-app-for-ubuntu/</guid><description>Over the last few weeks I&amp;rsquo;ve been working on a project called uLuas. uLuas is an open source smartphone app developed using the Ubuntu SDK. It provides real-time tram stop information for Dublin&amp;rsquo;s Luas light rail service. In this post I&amp;rsquo;d like to talk about my reasons for developing this application and why I chose the Ubuntu platform.
First - and most importantly - I live and work in Dublin and commute daily using Luas.</description></item><item><title>Getting Ubuntu notifications to appear on the correct monitor</title><link>https://blog.aaronhastings.me/getting-ubuntus-notifications-to-appear-on-the-correct-monitor/</link><pubDate>Thu, 25 Jul 2013 18:23:50 +0000</pubDate><guid>https://blog.aaronhastings.me/getting-ubuntus-notifications-to-appear-on-the-correct-monitor/</guid><description>Like many of you, I use Ubuntu at work with a dual-monitor setup. One of the most frustrating things I&amp;rsquo;ve always found is its behavior regarding pop-up notifications. I regularly miss new emails or chat messages due to the notification popping up on my secondary monitor, right on my eye&amp;rsquo;s blind spot.
I&amp;rsquo;ve been putting up with this up until now, deeming it to be a bug in either Unity or notify-osd itself.</description></item><item><title>Django (not the movie)</title><link>https://blog.aaronhastings.me/django-not-the-movie-part-1/</link><pubDate>Tue, 19 Feb 2013 14:23:48 +0000</pubDate><guid>https://blog.aaronhastings.me/django-not-the-movie-part-1/</guid><description>For added ambience, listen to this song while reading.
Django is a web framework. I only vaguely knew what that meant when I declared I was using it for my project. In a nutshell, it&amp;rsquo;s a way of plugging everything about a web application together in a coherent, structured way. That includes HTML, CSS, images, data stores and middleware. Anyone can write a CGI script in their favorite language that does nothing but spit out HTML to a browser, but that&amp;rsquo;s unnecessary with Django.</description></item><item><title>Final Year Project: Introduction</title><link>https://blog.aaronhastings.me/final-year-project-introduction/</link><pubDate>Fri, 02 Nov 2012 20:33:12 +0000</pubDate><guid>https://blog.aaronhastings.me/final-year-project-introduction/</guid><description>I have to admit that I wrote the Raspberry Pi off at first. I mean, my initial description of it as a &amp;ldquo;slow Linux computer&amp;rdquo; are technically correct, but I never really thought of looking at it for what it really is - a cheap, small and, least importantly, slow Linux computer.
Top-down view of Raspberry Pi
I&amp;rsquo;ve been actively using Linux since 2009, with Ubuntu eventually becoming my primary OS in early 2010.</description></item></channel></rss>