Recently in Grumblings Category

So Ubuntu 11.04 was release a few weeks ago and I decided to upgrade this weekend.  In prep for the upgrade, I backed up my laptop onto my external portable hard drive that I may need (my home dir, and a few other things in /etc, some cronjobs, etc.).  I then did a clean re-install from CD.  In the past the ugrade-in-place has taken a long time, and was not completely problem free.  Whereas the last time I did a clean re-install it was pretty much problem free- except getting all my personal files/configuration/settings the way I like them all back took some time.  So that is the same approach I decided to take with this upgrade.

Recently, I got a normal update popup from my Ubuntu Update manager.  The update included a new kernel as well as other items.  I usually wait a few days on kernel updates because they can make some things break (like virtual box) and I'll need to do some manual fix-up work afterwards.

So I did the upgrade and after I noticed something new and very annoying.  I use an HP laptop- Compaq 8510w, which has two led indicators for wi-fi.  They have always simply been on when my wireless is on, or off when it is off.  Never more than that.  Well, after the upgrade those leds started blinking according to my wireless usage.  At first I was like, "what the heck?  What did I do to make that happen?"  What ever it was, I was not pleased.  It was so distracting that I was thinking of covering up those leds with black tape.

I then searched on google for any one else with a similar problem and I found one.  Unfortunately I can't find it again right now, but the post I found mentioned the same latop and a similar problem but on Fedora.

I've been using Ubuntu for a few years now and quite like it. And when I saw they had released 10.04 I was excited to upgrade. The last two releases I did an upgrade-in-place with their upgrade tool and I didn't run into any major problems. So I did the same thing for this release. But that's where this story begins.

First I noticed that I was getting warnings and errors related to my X.org config. This was very alarming since I've never seen that before and I don't run any thing unusual in my x.org config. I tried a few different things to address it but could never really solve the problem. Then I noticed that rhythmbox was always crashing on me. Like all the time. Oh and my startup applications would never start up as they were supposed to. And compiz wouldn't work due to complaints about in correct driver even though I did install the correct one.

So after complaining about it for a week to my coworkers they suggested that I back up all my important stuff and then do a fresh install. Complety wipe it and install from scratch with 10.04. So I bought an external hard drive (500G) and did that. The fresh install was soooo easy and quick. I then carefully restored data back to my home folder. If you are doing this be careful not to copy back .gnome2 or .gvfs or anything .g* or at least be very cautious in doing so. Those could break things on an upgrade like this.

Conclusion- the fresh install worked beatifully. Ubuntu 10.04 works great and i'm not seeing any of the problems I had earlier. In fact it also fixed a completely separate issue I was having with my wireless card. So I'm definately still an Ubuntu fan.

I've found that is it hard to keep up your blog if you don't keep up your blog.  Sounds silly when I write it out like that, but it's true.  If you don't make time for something, then it probably won't happen on its own.  Enough said. 

It has been far too long since my last post, so... here's one now.  I recently had a new baby boy.  That has  been really cool, but my 2 year old daughter has been more difficult, at least when it comes to sleeping.

Sleep is an interesting thing.  For some people it is an absolute necessity for basic functioning from day to day.  For others it is just a nice-to-have optional sort of thing.  However, when you go for long periods of little-to-no sleep, anyone will feel the effects.

I'm trying my best to keep my lack of sleep from affecting my day to day behavior and general happiness, but it's hard.  One of the main things that helps is good food and a good shower.

So this will probably be a first in a series of posts related to software design patterns and all my inner strugglings regarding what is hype and what is real.  There are probably lot of other people out there that may have similar strugglings, and more than likely there are some out there that are blissfully unaware of the concerns.  So what am I talking about?  Well let's start where I started a while ago, with ORMs.

ORMs (Object Relational Mappers) are a basically a way to have a OO layer between your application code and your RMDBS.  There are some basic "features" of an ORM, but not all ORMs support all of these.  In any case here is a list of common features:

1. OO interface to tables, rows, functions, etc, in your database.  So you can use native application code and OOP to interact with your data.
2. A more elegant/simpler API to interact with your database.  Many ORMs use some other database API under the hood, but add routines and interfaces (or simplifies calls) that the normal API lacks.
3. Object (data object) persistence.  So that you can create an instance of some data you are modeling and then be able to store that object and revive it later with state preserved.
4. Abstract the interaction between your application code and your database such that in the future if/when you need to move to a different database you application code will require as little change as possible.  Ultimately, changing databases should be a matter of configuration files, or perhaps even less work.  And your app code wouldn't even know the difference between Postgres, MySQL, SQLite, or something else.