Skip to main content


Finally, here it is! (to those people who kept insisting on me to write a blog)

Honestly, I haven't a clue as to why I'm putting my time aside to write a blog. I've always wanted to have one, but never really fancied writing diary style entries.

Maybe I'll have another go at it. The first time I started writing for this blog, it was over half a decade ago. The posts I had were exactly the kind of personal diary like boring stuff that most people might not want to read. So I had to take it down.

Along with those personal tidbits, I had tons of crossposted content that I left in, thinking it would spice up things a bit. (Courtesy: Digg social spam tools; I still miss the old Digg). That turned out to be a breeding ground for spam comments.

verbose = 0;

I'm using this blog as a place to put in some amount of brain dump. Since this sub-domain is the primarily shared URL connected to "me", I'll also be using this a place to consolidate all my other links.


Popular posts from this blog

Docker CE on openSUSE tumbleweed

Getting the docker community edition installed and running on openSUSE can be difficult because there are no official docs on how to do it for openSUSE, specifically the tumbleweed version of it.
Here's what I did to make it work:
Add the Virtualization:containers repo of openSUSE Tumbleweed and install docker as shown below. (This should install Docker CE) sudo zypper addrepo sudo zypper refresh && sudo zypper install dockerDisable the docker daemon that was started from systemd if any. sudo sysctl stop docker Starting docker service using the bundled systemd config seems to be causing issues with some docker functions. I wasn't able to get to the root of the problem, but I found out that running the daemon manually seemed to fix the errors I had from having the docker started via systemd.Start containerd (and keep it running): sudo containerd /run/…

Adding Nextbit Robin to udev rules

If you ever had to use adb or fastboot for your android devices on linux, you may have noticed that devices show up only when you add 'sudo' to these tools. This isn't good. Here's a way to remedy it. Instructions tested on openSUSE tumbleweed.

* Update your adb and fastboot from Android Studio SDK manager (platform-tools) or wherever you got it from.
* Make sure your user is added to the "plugdev".  Create a plugdev group if it doesn't exist "sudo groupadd plugdev"
* Add your user to plugdev "sudo usermod -a -G plugdev $(whoami)"
* Edit /etc/udev/rules.d/51-android.rules (create file if it doesn't exist) and add the following line for nextbit robin:
SUBSYSTEM=="usb", ATTR{idVendor}=="2c3f", MODE="0666", GROUP="plugdev" Replace the ATTR{idVendor}'s value with your device's value. For all nextbit robin devices, these are the same "2c3f". You can find them by typing "lsus…

Installing fonts and using it in Xresources

Drop the .otf/.ttf font file in ~/.local/share/fonts (or the deprecated ~/.fonts/)

Rehash fonts db using: fc-cache -f -v (or reboot)

Find the font family name by grepping for it like: fc-list -v | grep "Nerd font" | grep "family:"

My result was "DroidSansMono Nerd Font"

In ~/.Xresources, put in this line: xterm*faceName: xterm*faceName: DroidSansMono Nerd Font:size=16:antialias=true

And finally: xrdb ~/.Xresources