The major result of my past few days in the shop has been the fabrication of drawers for the sewing machine cabinet. Now I feel like this thing is making some real progress! The drawers are constructed of baltic birch plywood for the sides and back, and hardboard for the bottom. The fronts are made of solid cherry with a cutout at the top for a hand hold. The cutouts have a cove profile routed on the backside to provide some additional grip.

After searching the web and trying a number of things with no better results, I tried logging in as the db2inst1 user created during installation. Voila! Everything works beautifully. The thing that I was missing for using DB2 commands from other users was adding DB2 environment variables. The script that does this in a default installation is /home/db2inst1/sqllib/db2profile. Running the following command sets up the DB2 environment:
. /home/db2inst1/sqllib/db2profile

Okay, this is probably a total noob mistake, but if this post helps just one person, it was worth it.  

 sudo port install openldap

Copy slapd.conf.default to slapd.conf

cp /opt/local/etc/openldap/slapd.conf.default /opt/local/etc/openldap/slapd.conf

Customize OpenLDAP configuration for Tomcat sample schema

edit /opt/local/etc/openldap/slapd.conf

Add additional schemas needed to support the Tomcat sample:

include		/opt/local/etc/openldap/schema/cosine.schemainclude		/opt/local/etc/openldap/schema/inetorgperson.schema

Also set suffix and rootdn as shown in this sample. There’s no need to change the database type, however.Notice that the slapd.conf file defines a location that doesn’t exist for a pidfile and argsfile, so we’ll need to create the directory:

sudo mkdir /opt/local/var/run

Start up OpenLDAP:

sudo /opt/local/libexec/slapd

Check that it’s running:

ps -ef|grep slapd

If it’s not, use -d -1 options on the command line to see what’s causing it to fail.Copy the LDIF sample file shown on the Tomcat page into a text file.Import the sample data:

 ldapadd -x -D "cn=Manager,dc=example,dc=com" -W -f tomcatsample.ldif

Backup Tomcat’s server config

cd tomcat_rootcp conf/server.xml conf/server.xml.backup

Edit the realm definition as shown on the Tomcat page – authentication should not be needed to do LDAP lookups with the default configuration

edit conf/server.xml

Perhaps I should expand on that a bit. When you?re in the Maps application, you can search for the location that you want to go to. Once you?ve found it, you click on the pushpin on the map to bring up details. Then, you click on ?Directions to here?, which puts the Maps app into directions mode instead of search mode. By default, the To field is filled with the place that you?re tying to get to, and the from field is filled with the special text ?Current location.? You click on the Route button and Google Maps computes a route to get you where you want to go. Once you?ve done it a couple of times, it?s a very fluid and natural experience.

 The first problem was related to updates. I could run the launchpad application, but when I tried to run the WAS installer, it would crash and core dump. Eventually I found an article on devloperWorks talking about a similar problem installing DB2. The poster said that an update fixed his problem. Although Fedora was offering 140 updates, I didn’t want to spend the time installing them. I decided to go ahead and do that, and afterwards my core dump problem was fixed.

However, now the installer just quit without doing anything (or even showing an UI) rather than core dumping. A post by Kenny Smith suggested that there were some other packages that needed to be installed as documented in the manuals. I decided to read the installation manuals on the InfoCenter, and followed the instructions for RHEL5. Sure enough, there were four or five packages that were documented as being required that were not installed by default, so I went ahead and installed them. Lo and behold, the installer ran and installed WAS!

I guess the moral of the story is two-fold: 1) Install the updates that the system is offering. 2) Read the manual. 

The next step is to make feet, and I’ve started machining the wood for those parts.

The keyboard seems a little low at first, but I haven’t had a real problem with that so far. The big win is that the keys provide much better feedback about when you have pressed the key than the previous design did. I have read some complaints about the keys being too easy to press, but I haven’t noticed that problem so far.