Latcarf's Locution

So yeah, it's been a loooong time since I posted in this blog but I found something that gets my goat enough to write about it... It's this damned bailout business. I'll post more on my feelings about this when it's not so close to my bedtime but for now, I'll just leave with a link to a high-level analysis of the cost thanks to CNBC.

Yes, you as a tax payer are indentured to your share of this. Yes, you are now solidly a slave of the state. Yes, your unborn children already owe. Get working friends, it's gonna take alot of your sweat to pay this off. If you consider there's 300 million people in the US (from age 1 day to very old) and the cost of the bailout is roughly $4.3 trillion (that will go up), then you owe (right this minute - not counting inflation) just over $14,000! Remember, this amount is on top of your share of the national debt (and I won't even get into that).

Get cracking people, freedom is not free!

I was a little concerned with the web service on my new Intel Xserve running Mac OS X Server 10.5 (Leopard) when I started seeing the following log entry in my Apache error log:



I wasn't so much concerned that there was a critical error. I could see my Apache 2 based Subversion server (DAV svn) was performing just fine. My larger concern was that there was an error about mod_rewrite when I wasn't the one that turned it on in the first place. You see, I could believe it was my human error that might have caused the problem but I'd have a harder time believing it was a problem with the default install.

So, I looked at my config file: /etc/apache2/sites/0000_any_80_.conf and compared it to the default config file: /etc/apache2/sites/0000_any_80_.conf.default and found the <IfModule mod_rewrite.c> containers to be exactly the same. Annoying.

Iquickly gave up trying to point the finger and lay blame and decided to take the initiative to fix the problem. I fixed it by giving mod_rewrite an actual log to write to (make it happy - if for only a moment) and then told it to not to log anything to the file (mwahahaha). The change was simple.

From this:

To this:


Problem solved it seems. Now why did I have to do this!?

The Guardian had a great article about why eBooks and other reading "gizmos" (devices) won't beat printed books anytime soon.

The article was well written and pointed out some interesting facts about the longevity of books. This is exactly something I've been framing in my mind as to why I'd rather be writing books than writing software. If I could support myself as well doing the formers as I do doing the latter, I'd change my line of work in an instant!

Every once in a while you hear something that is so dumb it will give you an aneurysm. Fans of Lewis Black will know this as an "If it weren't for my horse..." situation. Well, I had a similar experience this morning. I was waking up to the radio as I am wont to do (the buzzer just isn't as appealing as I get older), and the news was on.

The anchor woman was talking about TurboTax. She spoke about how last year, Intuit had a bandwidth problem that brought down the TurboTax servers near tax day and caused a few thousand people a real headache. The newscaster asked an Intuit spokesperson about what had done this year to help keep that from happening. After talking with the Intuit PR woman, the newscaster talked to an IRS representative. The IRS agent explained how last year they were able to offer an extension of 48 hours to the people who were affected and how the IRS really appreciates e-filers.

Now, none of this talk could make blood shoot out of my nose. This is all very simple, straight forward, and reasonable. It's what the IRS guy went on to say next that got me. Actually, it wasn't just what he said... but how he said it that twisted a vein in my noodle.

As my memory surely can't recall a direct quote from this morning, I will do my best to paraphrase accurately. He (the IRS guy) said something to the effect of: E-filing is such a great thing. It used to be that we literally had trucks pull up to the office (IRS office that is), unload tons of forms, and we had to go through each one (whine, whine). It was sooo hard and there was sooo much to deal with!

That's the one that blew my gasket! I thought to myself: WTF!? Did he really expect me to think: "Poor IRS, they used to have so many forms to deal with. I mean it was literally tons of paper they were swimming in. Can you imagine the potential for papercuts!? I feel sorry for those guys. It must be so much easier for them if we e-file. We really do need to make their lives easier."

Ok... Look asshole, I'm sorry you had to work with all those forms, but seriously, you're the assholes who're telling us we have to do this crap. There isn't even a god damned law stipulating that we have to. It'll be a cold day in hell when I feel sorry for all the work you have to do when I file my taxes. I shouldn't have to do this crap work in the first place. As a matter of fact I shouldn't have to pay any taxes in the first place considering I don't a agree with a single thing my tax money is spent on (inflating the dollar - for instance).

So my brain nearly burst when I thought about how this IRS agent had hoped his comment would spark pity in me for what he has to go through. The only thing that got me calmed down what when I thought about the slim chance that the TurboTax servers might go down again this year. Oh goodness, I really hope it doesn't happen again. I couldn't bear the thought of the IRS having more heartache and headache on tax. Those poor guys!

Recently I wanted to use Fink on my Leopard machine at work. This sounds simple but there are a few complicating factors. First, there are no Fink binaries for Leopard as of this writing. Ok, so that's not a big deal, I can compile it easy enough, Fink made an easy to use bootstrap script for that purpose. Secondly, as far as I know, as of this writing, we can't use rsync mode during Fink's self update on Leopard. So, the solution is to use fink selfupdate-cvs. This leads to the third problem which comes from the fact that my company is strict about blocking ports. Unfortunately the cvs port 2401 is blocked. Fortunately however, SSH (port 22) is not. So my solution is to temporarily port-forward cvs through ssh to my home server so I can run fink selfupdate-cvs to pull down all the great package descriptions I need for my fink install.

Here's are my notes on what I did: