In an effort to completely break my first promise to myself, I have been searching for every possible alternative to writing.
Amateur procrastinators have very few tools in their arsenals, but us professionals have two basic types of activity to choose between: constructive and frivolous. The best 'crastinators amongst us are able to weave the two into a fantastic matrix of avoidance. Here's a few gems from my last two weeks...
Constructive: I did more exercise, pushing my stairs routine up to 100 flights (that's 100 up, 100 down, buns of steel) and carving a full minute off of my 6-mile jogging time.
Frivolous: I played some of my video game of choice. And then played some more.
Constructive: I poured myself into my job, even going so far as to ask my boss if there's anything more I could do. gasp.
Frivolous: I played another video game. And then yet a third one. The third one has become my new game of choice. I went back and tried a round or two of my first game of choice and it came up flat. Games are flavor of the month 'round here.
Constructive: I spent quality time with the soul mate, including a romantic weekend out of town. Ok, so this one can't be considered procrastination, because I'll gladly break my writing promise to keep the relationship passionate and connected.
Frivolous: I opened my life up to a fourth hour-long tv series. I generally keep my committed TV watching to no more than three hour-long shows at any given point in time. Since this repeats every week, it'll be the procrastination gift that keeps on giving.
Constructive: I spent quality time with the kid, including a day off from work to share the civic responsibilities of election day with the next generation. As with the soul mate's quality time, this should be considered mandatory time and not a procrastination enabler, but it helps the constructive/frivolous pattern so I'm going with it.
Frivolous: I listed a giant pile of old paperback books on swap.com to hopefully land me some of my "wants" list. Categorized as frivolous because I've already got a queue of 15 books, adding more to that cannot be considered anything but.
Constructive: I raked the leaves from the yard. Then it rained and brought down more leaves. I raked again. The wind blew and I raked again.
Frivolous: Hell, I even chose writing as an alternative to writing. Specifically writing two unpublished articles. Long ones. Subject matter was a video game, in lieu of sitting down and writing a fiction piece aimed at submitting for possible publishing.
And the last bit of constructive frivolity...
I reminded myself of the key feature I like about my custom blogging system: all the content is stored in simple text files.
/begin technical mumbo jumbo
Continue only if you want to read about nerd computer stuff.
Wondering why I hadn't seen any apt-get update notices on my server for a while, I looked into the matter. I discovered that my Linux distribution Ubuntu 9.10 was out of support since May. The latest Ubuntu is 11.10, released just recently. There are two ways to fix: incremental upgrades and fresh install.
Following the recommendation of a friend, I set upon the task of incremental upgrade. To get from 9.10 to 11.10, you need to jump through
Seems like a pain in the butt, so I decided to go with the fresh install and downloaded the Live CD ISO for 11.10. I keep my data and my OS on separate disc partitions, so should be a slice of pie. Like a good little boy scout, I backup /home just in case. As I scan my situation, I see that mysql is sitting in /var/lib rather than /home. You'd think it would be as straight forward as moving the folder, updating the config file and that's all you gotta do. No, hours of wrestling and Googling turn up apparmor which will become the bane of my existance over the next few days. For the record, I did get mysql properly functioning under the /home datadir before I began this process.
With my database and other files happily living in /home, I hook up the external CD drive and load the Live CD. Only the thing totally ignores the CD and boots off harddrive. Reboot holding key to get into BIOS. WTF, its already configured to boot off of CD before HD. Whatever, exit and proceed. This time it boots off of CD.
Since I'm playing with fire and generally apt to get burned, the Live CD install for 11.10 freezes up early on in the process. Another thousand Googles later, it still won't work and the agony of four incremental upgrades seems less intimidating than it did only hours ago.
Using the X Windows GUI for software updates, I begin my first of many tries at upgrading from 9.10 to 10.04. Seems every error I can come up with, I came up with. The best of which is the installer freezing on Mysql. Another Kilo-Googles later and I've successfully got 10.04 running AND mysql. The beauty is that the in-place upgrade leaves all your stuff like network setups, Apache server, PHP, SSH, and my-hated-sql all working as you had them before the upgrade.
On to the 10.04->10.10 upgrade. Armed with my learnings from the previous mysql pain, this one goes a bit better. Another hicup on Mysql, but I'm getting good at that by now. Then it gets to the very end of the process when it creates your boot image kernel. It would seem that my /boot partition is too small. It needs 2 more MB to house the previous kernel and the new one. I could delete the old one, but that'd leave me with no parachute, so I begin the next part of the journey.
I need to resize my partitions with the hopes of avoiding a reformat. Yes, I've got my data backed up, but No, I don't want to have to prove that my backup was (a) thorough and (b) effective. I'd really like to resize and keep the data intact, please and thank you.
GParted seems like the ticket. A quick 100MB download from their sourceforge site and some wrestling with my burner (why the fck won't the drawer open without rebooting?), and I've got a Live CD with which to run GParted. The sour taste of the failed Ubuntu 11.10 Live CD still fresh in my mouth, I boot up GParted.
Cute GUI showing me a linear depiction of my disc. Click /boot partition and discover that I cannot enlarge it because it butts up against swap, /, and /home. Solution: shrink /home, then shrink /, then shrink swap, thus creating some space for /boot to grow into. Major pucker factor as you click the "sure, i understand that this action is highly likely to fry my data" button, but each command executes and reports success. Time to boot and see if I can get back into a functioning 10.04.
Sure enough, she's golden. Never so happy to see that X Windows splash screen.
Run the updater and now it has enough space for the new kernel in /boot. And I'm running successfully in 10.10.
Fire up the Software Updates tool. "Partial Upgrade Only" available. WTF? This one only took a baker's dozen Googles to solve. Seems that the botched Mysql part of the previous upgrade left things somewhat broken. A few commands and the full upgrade to 11.04 is available.
Run run run. Who would have guessed, it barfs on mysql again. Seems like the same fix should get things working again like the last two upgrades. Things continue and now I'm booting 11.04 for the very first time. I health check everything and its looking fine until I hit my old blog. I've got a site running on the server with Wordpress installed, with mysql on the backend. Can't connect to the db. ps -ef | grep mysql comes up empty. She's not running.
Back to the Google. Endless bug reports, log file dumps, forum threads. Lots of people have my exact problem. Lots of people offer solutions. None of them work. My 11.04 is alive and well, but no functioning mysql. One forum post did say that 11.10 solved their problem, so I'm off to the updater.
Along comes the familiar mysql fails during the update. Along comes the familiar /boot full message. Luckily this time I've got some kernels to delete from the long and winding upgrade path I've been on during the past few days. Kernel complete, 11.10 up and running.
No mysql. The bitch won't start.
My favorite is the recommendations to run a database table integrity checker as a solution. Only problem is that the integrity checker needs to connect to the database in order to check the integrity. Chicken and egg, anybody? I cant run the check if the database wont start until a check has been run :-(
So this morning I wiped mysql, and reinstalled. Hey, works like a charm. Only my data isn't there. So my old blog posts aren't showing. Sure, my content is burried in a backup of the original mysql data directory, but how the hell do I get at it?
Makes me happy my new blog system keeps the content in plain text.