When the Thinkpad arrived, it had a special “empkernel” which made all the hardware run. When I upgraded, the empkernel was left behind. Ubuntu mostly kept the hardware running fine though.
Some exceptions . . . . This month, when I upgraded to Jaunty, the Atheros wireless card stopped talking to the OS. Horrors! I need that card. On the other hand, I had a new excuse to play with the bash shell. I dug out an old ethernet cable to get back on the net and began googling for solutions. Not much luck at first. . . .

Then I found Ubuntu Geek. Problems over. The wireless card problem?

Fixed here: http://www.ubuntugeek.com/new-madwifi-now-supports-ar2425-in-madwifi-trunk-branch.html

But wait! My wpa encryption support still isn’t fixed! No. Ubuntu Geek had that covered too . . .

http://www.ubuntugeek.com/enable-wpa-wireless-access-point-in-ubuntu.html

So. If you’re sort of a newbie like me to Ubuntu and spend waaayyy too much time googling around and not finding stuff, and you like using the command line, then my suggestion is to start with Ubuntu Geek next time.

When I started practicing law, it was still relatively common for older lawyers to use dictation to create documents. These lawyers often did not know how to type let alone know how to use a word processor.

My grandmother was a lawyer who knew how to type, but her peers often mistook her for someone who was merely there to do the typing. She nevertheless recalled the skill as an advantage in the days of manual typewriters and carbon copies.

My mother forced me to take an introduction to typing class when I was in high school. I learned to use word processors when the first ones arrived so the transition was easy. Today I am able to do my own word processing. An assistant generally slows me down when I’m drafting and editing a legal document. As I’ve migrated to FOSS, my need for an assistant has continued to decrease.

That said, I’ve also realized I’m missing an entire set of skills that later generations of lawyers will likely take for granted. I interact with computers, software and networks like a consumer. Those skills aren’t enough. I need developer skills. All lawyers do. Like lawyers today know how to type. Lawyers tomorrow will need to know how to code.

In order to unlock the power of the computer and of networks, lawyers need to understand what the computer essentially is and what it can do. Its critical to have some notion of the computer as a logic machine and to understand its power to manipulate and organize datatypes. Apart from a deeper understanding of what it means to write and compile code, database literacy is probably the most obvious missing skill I can identify.

At a more general level, its a stunning irony that lawyers use logic as a professional tool but often lack any concept of how to use free code to unlock the logic engine inside every PC.

So its trite to conclude a project with the discovery that the journey is less complete at its end than it was at the beginning. But that’s where I find myself today.

True. There is no proprietary code left which is needed to run my law practice. The code in my office will already do more than the proprietary code I used in the past.

But I’ve exhausted a ridiculous amount of time and money to get where I am. And I’ve barely scratched the surface of what can be done. The limit I encountered is not the code. Its my own skill level.