From a distance, you can see the tree. We took this from one of the tee off spots for disc golf at night.
This shot is from standing underneath the tower(tree).
Next, spin around with your camera in the air. Yay!
]]>If you want to learn more about those formative years and how we made do with our meager roster, Matthew Doyle’s What is American Soccer is a must read.
]]>My workstation at work still has Ubuntu on it. And, worse, it has an ATI graphics card. I was so unhappy with Unity that I decided to install gnome shell and use it as my default shell. Gnome Shell was new to me, but I’ve been learning its features and feel comfortable with it now. However, I’d been suffering with the top bar displaying a graphics glitch, as well as some funky icon rendering. It corrupted the font display. So I was unable to read the calendar or the words on any applets in the top bar.
After doing some research, I found the likely culprit was fglrx which is the proprietary ATI graphics driver. Figures. Apparently it didn’t work with Oneiric Ocelot (11.10). The solution was to remove fglrx completely then install the ATI driver. Seems easy enough.
I did so and rebooted. All of the sudden, I couldn’t get a login screen to even display. Nothing. Uh-oh. I walked over to a colleage’s desk and verified through ssh that I could login. Phew.
Later, I found that what had happened was that it was actually working fine. But the removing fglrx doesn’t do anything to the xorg.conf file I had sitting in /etc/X11. That file was instructing the box to load fglrx as a module and crashing. I discovered my folly through a little lucky browsing. I found an Ubuntu wiki article on the Radeon driver (my card is an ATI Radeon). It states:
Recommended configuration for X.org. No configuration is necessary for ATI driver in the modern versions of Ubuntu. You can safely take away your xorg.conf and your computer will run fine. RadeonDriver
Once I renamed/removed xorg.conf and rebooted, I was back in business. And, everything rendered fine now. I was able to use the built-in Gnome display control panel configure my second monitor. Good times.
Today’s lesson: ATI = bad, Unity = bad, RTFM = required.
]]>Here’s the recipe, tracked in a gist.
But you want to use Chrome? It isn’t supported. Ruh-roh. No worries. It’s an easy fix. Open your .gitconfig directory in your user home directory. Add a Chrome section specifying the path to it. Then reference it in the instaweb section.
Happy browsing.
]]>notify-send is one of my favorite shell commands. I use this for other things too. For example, I can have it tell me when my build is done. I’d also like to create one to tail the JBoss log and tell me when JBoss is started. That way I can do other things while JBoss is starting.
I can improve on this. I need to learn how to make my functions more generic (just like my other code). This script assumes 2 symlinks at my root. That’s fine. But, I should define those as variables. And, I should extract them to separate bash files and include them using the source command rather than just hacking my .bashrc file directly. One step at a time.
]]>Unfortunately, my setup is not optimal. I have a bunch of git repo’s, one for each SVN project. My future plans involve cloning at a higher level so I can have few git repo’s. Until I fix that, I find it difficult to determine which repo’s are “dirty”.
Fortunately, I found Matthew McCullough’s great script solves this problem for me. For my setup, that just meant saving this script to the root of my project where all my git repo’s reside. Then make the script executable. Voila!
]]>