Too much ADVrider.com (a.k.a. Why take an SV down that road)

21, Nov, 2007

Monday night I had to do some work on a server after hours so I logged on over the VPN from home around 8:00. I add a new server and Windows Network Load Balancing decides to bind the IP address to the wrong interface and takes the server offline. I hop on the bike and head in to work since it was a nice evening. I end up redoing the entire cluster and leaving work around midnight. The night was still pretty good and it was quiet on the streets at that time. Everything is up and running smooth at work by 2:00pm on Tuesday. I tell my boss that it’s too nice to stay any longer and I’m taking the rest of the afternoon off.

My wife was getting her hair done so I knew I had to be back to pick up my son so I couldn’t get too far away. I decided highway 80 would be a good destination for today. It’s a bit rough but I wasn’t planning on pushing too hard. I’m just out enjoying the nice day.

Image

I was a little tired so I thought I’d pull over and drink my caffeine that I picked up when I topped off in Coweta. I noticed that this pull off was really a trail so I decided to head down it a bit.

Image

Image

It’s a little rocky but fairly decent trail overall. The SV is definitely geared too high for this but it’s handling it fine. I really miss having a dirtbike around about now.

Image

Image

Image

A small creek running through with plenty of rocks. I wanted to check some other spots out so I decided to turn around here.

Image

Looks like I’m not going this way either. :rolleyes

Image

I decided to get back on the pavement so I can save some time for more wandering later in the trip. Heading down 51 toward Wagoner.
Image

This is where the batteries gave out and the spares are on the kitchen counter. :rolleyes

I see a sign “Porter 7 miles” between Wagoner and Coweta. I decide to take it so I can take 51B, 104 (back way into Haskell), 72 and Indian Road (161st). It starts out paved and quickly starts alternating sections of rock and rough asphalt. It turns completely to rock before the overpass for the turnpike and T’s right after the overpass. No sign at the T so I choose right since it’s going west. I figured I could adjust if it wasn’t the right way. Turns out it wasn’t the right way. The road gets worse and there’s grass growing in the middle of it. There’s rocks in a couple of the hills that weren’t cut out. It just drops and you get light going over it. It dumps into someone’s drive so I backtrack to the last intersection and jog north a mile before turning west again. This road does go through and I catch 51B heading north/south instead of catching it east/west like I had originally intended.

It’s fairly smooth sailing from here. Highway 104 goes along some sod farms, has a couple 25mph 90 degree turns and a 35mph sweeper before it crosses the Arkansas and heads into Haskell. Head up 72 toward Coweta and cross the river again. Turn on Indian Road (161st)and follow it until it turns north at county line road and on into BA. I get back to the house about the time I normally get home on a weekday. Jump in the Jeep and go pick up my son at daycare at the regular time.

Seeing how today and the next few days are turning out, I’m really glad I went out for a while yesterday. Might not have been really far or really exciting but I enjoyed myself. I have to take the opportunities as they come. Now I’m going go back to drooling over a Husqvarna TE610. :up

Update PEM FVWM2 theme for OpenBSD

1, Nov, 2007

So an email comes in the other day asking about PEM’s theme that I tweaked for FreeBSD. He was asking about running it on OpenBSD and wasn’t having much success. The problem is OpenBSD is using an older version (another oldish version in ports) and the theme requires some things from the “unstable” 2.5 series. OpenBSD has integrated the last version (2.2.5) before the license change so it hasn’t been updated. There’s a 2.4.x port since that’s the “stable” branch. OpenBSD doesn’t import beta software into ports/packages. This is a great idea but unfortunately some things are in perpetual beta. FVWM 2.5.0 was released in Jan ‘02 so it’s only a month or so younger than my son and he started school this year. heheh

The first obstacle to overcome is getting 2.5.x on the machine. I found an an unofficial 2.5.21 port but it was giving me some errors on my OpenBSD 4.1 laptop. I look around some more but didn’t find a more recent port. I did find directions for compiling 2.5.16 on OpenBSD 3.8/3.9 so I pulled some configure options and hacked together a rough port of my own using version 2.5.23 since it’s current. My build errors went away but I had some errors on install while it was building the package. It was basically some man pages that existed but were in a different directory than it was looking for and a defaults file. I copied the man pages to the right working directory and created an empty defaults file. It installed fine and created a package. I used this package on a clean install since this laptop has been upgraded a couple times to be sure it was working cleanly. I upgraded both machines to OpenBSD 4.2 today and FVWM is still working fine. I’m going to do a fresh install of 4.2 on the test machine and give the port another look to see if I can get it to compile and install cleanly.

Download and install the theme and it looks like it’s supposed to but the scripts for wifi, battery and volume aren’t working since it’s trying to pull values from FreeBSD’s sysctls. This was to be expected since the original scripts were on linux and pulling stuff from /proc. A little fiddling with wicontrol, apm and mixerctl using awk, cut, etc. and I had working scripts again. I just added the FreeBSD portions of the scripts back in and used uname and some if statements to determine which to run. I guess I could add the linux version back in for completeness.

I did notice I was missing a couple things on the fresh install since it was pretty minimal. I needed to add ImageMagick, imlib and Esetroot (from eterm port) to get everything working. If you already have a fairly complete desktop then you likely already have it all but just double check before you decide it’s not working. You’ll also need to edit ~/.fvwm/config to set the path to your icons and set your preferred apps. I’m using aterm for the terminal and aumix for the volume but you can change it easily enough in the config file.

Here’s the FreeBSD screenshot and the OpenBSD is very similar (sorry lost the original screenshot):

Downloads:

fvwm2-devel-port.tar.gz
fvwm2-devel-2.5.23.tgz
fvwm2 configs ver 1.1

The port file is hackish but I’ll add checksums if/when I clean it up. The pkg was compiled on a 4.1 box but it’s working on a couple of upgraded 4.2 boxes now. You are welcome to it but use at your own risk. :^)