But some Republicans framed the UAW as the villain, criticizing what they called lavish wages and benefits that they said had driven General Motors, Chrysler and, to a lesser extent, Ford to their knees.

“I’m sure that I’m going to be asked, ‘Congressman, I work at Honda’ or ‘I work at Mercedes. I get $40 an hour. Why are you going to take my tax dollars and pay it to a company that’s paying their employees $75 an hour?’ ” Rep. Spencer Bachus (R-Ala.) said last month.

That wage figure — widely used by opponents of the auto industry bailout — is not in fact the wage paid to current workers. It is an approximation of the costs of salaries and benefits for current and retired workers. After wage concessions in recent contracts, the UAW says its workers at GM, Ford and Chrysler plants range from $33 an hour for skilled trades to $14 an hour for new hires.

Precise wages and extrapolated benefits costs for U.S. workers at nonunionized foreign companies, such as Honda and Toyota, are difficult to ascertain, but Block estimated salaries for current workers are approximately the same.

Unions aren’t perfect, but they shouldn’t take the all the blame for the decline of the American automotive industry. There’s plenty of blame to go around.

I thought that giving each session a dedicated thread and using fgets(3) to read lines would be easy. However, it is also very wasteful. The stack space required for 1000 threads (at 2MB per thread) would be 2GB. Plus, fgets(3) doesn’t tell you how many bytes were read, so you would have to call strlen(3) after each line of input was read.

The good news is, I wrote a pretty good thread pool implementation and will use thread pools for certain phases of the session that require blocking I/O, such as the fsync(3) and gethostbyname(3) calls. It’s also not too hard to revert the code changes and go back to an event-driven model.

It detected all of my hardware, and everything worked out of the box. The device driver utility is very nice, and gives you detailed information about which drivers are used to support each piece of hardware.

The installer doesn’t allow you to install into an extended partition; you must use a primary partition. I like to have multiple OS’s on my boot disk, so I would prefer to install it in an extended partition.

The installer allowed me to proceed without setting a root password or creating a normal user account. When I booted the system, the GUI wouldn’t let me login using an empty root password. I had to Alt-Control-Backspace to kill the GUI, then frantically login to the text console and set a password. Every 10 seconds, the GUI would automatically restart. I feel like the installer should require a root password.

The system feels very responsive, the graphics are crisp and quick, and the default theme is pleasing albeit a bit too much like Windows XP. There is a network monitor applet in the system tray that blinks when a network packet is sent or received, which I found to be very distracting.

The package manager is good, but very slow. Unfortunately, there is no vpnc client available, and I was unable to build the program from source.
By default, the system is installed into a ZFS root pool, but I don’t really like how it was setup. The name of the root pool is ‘rpool’, and the base of the filesystem is mounted at rpool/ROOT. This is aesthetically unpleasant.

For some reason, OpenSolaris still uses /export/home and the automounter, instead of just /home. Now that ZFS and NFS are integrated, I fail to see the need for an /export directory.. any dataset can be exported via NFS, why should it have to be mounted under a specific directory?

The splash screen covers up all the boot messages, and I couldn’t make it go away. The first time it booted, it took a long time (probably importing SMF services) but I couldn’t see what was happening.

The default install is very desktop oriented, and there are no developer tools or headers installed.

I tried to reboot from the GUI, and my X session crashed to display a blank white screen. I could type letters and they would appear on the screen, but there was no shell to interpret the commands.

The biggest problem I had was actually with GRUB. When you install OpenSolaris on a system that already has Linux installed, it wipes out your existing GRUB menu and will only allow you to boot into OpenSolaris. I had to jump through hoops in order to get my old GRUB menu back, so when I got it back, I said goodbye to OpenSolaris.

OpenSolaris is getting a lot better, but still has a way to go before I could even use it in a dual-boot setup.