Friday, April 17, 2009

Debian!

I got fed up trying to figure out why Xubuntu 9.04 beta couldn't connect to the wireless network at work, so I installed Debian 5.0.1 (which is the latest stable release).

The installation went smoothly. (I had to put the firmware blob for the wireless adapter on a USB drive at one point, but that was no big deal.) The default desktop environment is a very plain and boring version of Gnome (2.22.3 according to the "About Gnome" menu item.) I love it! No fancy effects, no stretchy or wobbly windows, no plasmoids, just plain vanilla buttons, menus, and windows. Ahhhhh.... :-)

After a few minutes of fiddling with /etc/apt/sources.list, I was able to install the wicd network connection manager (over ethernet), and a few minutes after that, I was back on the wireless network!

So, Ubuntu, thanks for the memories, and fare thee well. I salute your attempt to become both feature- and bug-compatible with Windows. In the meantime, I'll be getting some work done.

Ubuntu, the Linux desktop, and the second system effect

I'm depressed.

I've been a Linux user since 1994, and the Unix philosophy is an essential part of my lifestyle. The main reason I've used Linux is that it is simply the most productive way for me to get things done.

Since 2005, I've been an enthusiastic user of Ubuntu. At the time, and for several years thereafter, it was (IMO) the best Linux distribution, combining the careful design and usability of Debian with up-to-date hardware drivers and frequent high-quality releases.

However, for the past two years, using Ubuntu has been an increasingly frustrating experience.

The problem began with Ubuntu 7.10, which added Compiz. The precedent that was established by this release was that the addition of useless "eye candy" was considered an adequate justification for major regressions in functionality and usability.

At this point, I abandoned the default Gnome-based Ubuntu in favor of the KDE-based Kubuntu. Version 8.04, based on KDE 3.5, was outstanding. Yes, there were no fancy desktop effects. But everything worked.

Then came Kubuntu version 8.10, with KDE 4.1 as the default desktop environment. In terms of the sheer number of regressions in functionality and gratuitous interface differences, this release eclipsed even Ubuntu 7.10. The backport of KDE 4.2 helped somewhat. But I still spent considerable effort finding work arounds for software that was simply broken. For example, the very nice kpdf program for viewing PDF files was replaced by something called "Okular", which I suppose works OK unless you want to print, in which case you're pretty much screwed. Drag and drop between Linux and Windows XP (running in VMware player) stopped working. The mechanism for configuring panels changed drastically. I could go on and on.

I'm now pinning my hopes on Xubuntu, the version of Ubuntu based on Xfce. I'm now running the beta version of 9.04 on my laptop, and I'm cautiously optimistic, although I have not had any success connecting to the wireless network I use at work. (There appears to be a bug in scanning for wireless networks, and the dreadful Gnome network manager appears to be as buggy as it was the last time I looked at it.) I'm hoping that the release version of 9.04 will prove to be a stable platform. It's simple and configurable, and seems designed with usability in mind.

The evolution of Gnome and KDE, and hence Ubuntu, recalls the Second System Effect. Somehow maintaining a working, stable system is not sufficient, even though that has been the strength of Linux (and Unix in general) for many years. The developers responsible for creating the Linux desktop experience feel that it is necessary to make lots of crazy, unintuitive changes. To put it another way, both Gnome and KDE are beginning to feel a lot like a certain desktop OS from a corporation in the northwest US. And that's not a good thing.

Monday, March 30, 2009

Using git push

I'm starting to use git for some actual work, and am making tentative steps towards not totally sucking at it.

Right now, I'm trying to get a handle on working with remote repositories. In theory, because git is fully distributed, you don't need a central repository. However, I want to use remote repositories to (1) ensure my data is backed up (I have access to a Solaris server with a RAID and regular disk backups), and (2) allow easy synchronization of my work between the various machines I use (office PC, laptop, etc.)

The main idea with git is that repositories and working directories should be inseparable; all work should be versioned. Being a distributed VCS, git gives you lots of ways to synchronize changes between repositories. All well and good.

However, weirdness ensues when you consider what git should do when you push (commit) changes from a local repository to a remote repository. If you push into a remote repository that has a working directory checked out from the branch that you are pushing into, git does weird things. I won't even attempt to describe what happens, since I don't understand it. Suffice it to say that it's not a useful behavior.

One solution, as helpfully pointed out by the git cvs migration help file, is to create the remote repository as a "bare" repository, meaning that it does not have an associated working directory. So, the series of steps is something like:
server$ cd /some/directory && git --bare init

client$ git clone username@server:/some/directory
[ add some files ]
client$ git add files...
client$ git commit -m"Added some files..."
client$ git push origin
The "origin" in git push origin evidently refers to the remote repository from which the local repository was cloned.

Sunday, March 29, 2009

Good book on git

I found a good book on the git distributed version control system:

Pragmatic Version Control Using Git

This is the first good introduction to git (and to distributed version control in general) that I've seen.

Thursday, March 26, 2009

An addictive game

Beware: this is a potential time sink.
MiniGolf.zip [for Windows systems]
See the included README.txt for details.

Screenshot:

Monday, February 16, 2009

Q&A: How to use the command line to create a new top-level Opera window

When I click the "quick launch" button (or whatever KDE calls them) to open a web browser, I like to have a new top-level window, not a tab of an existing browser window.

Opera, by default, creates a new tab in an existing window.  So, I hunted for a command line option to force it to create a new window.  Here are the command line options:

http://www.opera.com/docs/switches/

Sure enough, there's a -newwindow option to create a new window.  I try it, and what does it do?

It creates a new tab in an existing window.

Thanks, Opera.

Thursday, February 12, 2009

Firefox working again

A reboot seems to have cleared up yesterday's firefox issue. Weird.

I guess I should probably quit out of firefox when a package update is being installed.