I played a bit with dh_make and dpkg-buildpackage - and thanks to the helpful crew in #linux and my own lil noggin, I figured out how to make .debs out of plain upstream tarballs! Yay for me! (Yes, intrepid reader, I greatly enjoy re-inventing the wheel. All flames are directed to /dev/null. Nyah.)

So, for those who care; here’s my first .deb - Drivel! I took the latest 2.0.2 version and built it for Ubuntu Hoary. I think I may have gotten the dependencies right, but at least on my machine this pkg works. :) I’m posting to my blog from it right now.

This is surprisingly easy to do for simple packages - I may start doing this more often. It’s only a step or two more than the ./configure && make && make install dance I am used to, and then I can use that .deb elsewhere, and I can make the .deb available to others. Yeah, I know, welcome to 1994. Nyah.

Thanks to Adam, who reminded me that I’d never posted the followup to my X Windows woes on the Crusoe-equipped P2110. There was a two part fix…

Part one, which probably applies to everyone running a .deb-based distro, is to recompile the X packages with different optimizations. The problem and actual workaround is well documented by this fellow, and he culminates his page in a patch and some documentation on the issue. This will fix anyone’s issue on standard X11 .deb packages. Also keep in mind that the debian/ubuntu xorg packages suffer from the same issue (I tried them), so you’d have to build the .debs yourself with -O0 optimization. This fix took care of the “app randomly dying from time to time, slowly taking X with it” problem.

Part 2 of my fix was solely due to my stupidity. I wanted the tvout and X acceleration from the retinalburn drivers, so I’d installed those. Those, of course, were compiled with -O2 optimization. They also stuck thru .deb removals as I’d put them in outside of the .deb process, and that’s what caused my X to just up and say “fuck it” and die, without writing anything to the logs.

At any rate; I’ve had a couple of months of trouble-free service (finally!), so I’m going to call this done. Yay!

I present my latest screenshot.

Wallpaper is available here. Widescreen only, sorry.

I picked up a unit that integrates my iPod to my car stereo the other day, and installed it last night. Pretty cool stuff… rather than the craptacular iTrip I was using (well, it’s not THAT bad, but it can never get any better than broadcast FM, which… sucks.) - I picked up an iPod2Car interface to my Dodge Nav Deck. This thing is SWEET.

It was a super easy installation. You’ve got to buy the iPod2Car box (which is a little smaller than the iPod itself) - to the tune of $190 - and the corresponding iPod2Car -> OEM deck cable ($20). Pull the iPod2Car out of its blister pack, set the dipswitches on it for your application, plug in the OEM harness, plug the OEM harness to your deck, and then plug in yer iPod (of course, you need to remove your deck and run the cables nicely, your mileage may vary). That’s it. I did the entire install top to bottom in less than a half hour. The iPod2Car wound up in a little niche behind the deck, and I ran the iPod cable back thru the dash, under the center console, and had it pop up near the drivers-side forward cupholder. I then picked up a Belkin TuneDok, slapped that in the cupholder, and put the iPod in it. It fit like a glove!

Operationally, the iPod2Car “fakes” the deck into thinking there’s a CD changer hooked up when in reality you’ve got your iPod there. This is great – not only do you get a super-clean audio interface, but you also get the ability to charge the iPod and control what’s playing using the deck’s native controls. To listen to the iPod, I simply hit the “CD” button on the deck, and hit Seek Up/Down to switch tracks. Works like a charm. The only time I need to actually use the iPod’s controls is to switch playlists. This is a design compromise - there are two schools of thought on iPod interconnects. The iPod2Car lets you completely utilize the iPod’s controls as well as the OEM deck’s controls, whereas interconnects like Dension’s ice::Link and Monster’s iCruze limit you to five custom-predefined playlists and totally lock you out of the iPod’s controls. I think that the iPod2Car’s method is more flexible; if I really want to get lazy I could add an AirClick and have the whole thing be remote-controlled. :)
Since this post is worthless without pix, here’s a quick shot of the installed setup:

See Kelly? Several months of research DOES pay off. I can’t wait for my next commute or roadtrip. :)

Those fuckwits just sent me a revised W-2 for 2004. AFTER I’VE FILED MY TAXES. Thanks a lot, dickweeds, for making me file a 1040X and 540X. Oh, and guess what? I owe the Feds $7. But it’s OK, cause the State of Cali owes me $8 according to the revised forms and TurboTax. All this over a buck. <sigh>