I Make Things

Run Script at Mac OS X Login

nospam@example.com (Latcarf) — Wed, 06 May 2009 03:28:12 -0400

I know alot of people want to know how to do this. The solution is usually creating a shell script and naming it with the '.command' extension so it'll launch the Terminal.

The cleaner way is through a simple launchd plist placed in your ~/Library/LaunchAgents folder.

Here's my example:

$ cat ~/Library/LaunchAgents/com.latcarf.loginscript.plist

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>com.latcarf.loginscript</string>
<key>ProgramArguments</key>
<array>
<string>/bin/bash</string>
<string>/Users/latcarf/Documents/script/loginscript.bash</string>
</array>
<key>RunAtLoad</key>
<true/>
</dict>
</plist>

# Start it up
$ launchctl load ~/Library/LaunchAgents/com.latcarf.loginscript.plist
# Or just reboot or logout and back in to kick it off.
# Only runs once at login.

Oakley M-Frames

nospam@example.com (Latcarf) — Sun, 03 May 2009 14:12:00 -0400

I just picked up some new Oakley M-Frames for use as shooting glasses.

I guess this means I need to start shooting again.

Ammo prices are skyrocketing though since we're in a bad economy and folks on the conservative right are afraid Obama's gonna take their guns away. Libertarians know that people only take your guns away if you let them.

Necrography

nospam@example.com (Latcarf) — Tue, 28 Apr 2009 14:04:00 -0400

A new horror fiction magazine is out. It's published biannually and contains fiction, poetry, art, and photos of the horror genre.

It's currently available for sale and has gotten some nice comments from readers. Looks pretty good.

The main web site is at necrography.com and there's a blog at blog.necrography.com.

Check it out and buy a couple copies, I think I will - always good to support independent markets...

It's not MAC!

nospam@example.com (Latcarf) — Mon, 16 Mar 2009 01:43:51 -0400

Just a little pet peeve I need to get off my chest.

I know all you PC folks are coming over to the Mac in droves and that's a great thing. It's great for you and for me. You'll have a much better computing experience (and life in general) on Mac and I'll still have a job making software for you. So win-win all around!

One little behavior we need to correct though, is how you write about your new computer. In the Windows world it's normal to write PC, or DELL, or IBM in all capital letters. Heck, in DOS (all caps there too) it's even proper to write FOLDER NAMES in capital letters as well, isn't it?

In the Mac world however, it's wrong to write Mac in all caps (and generally wrong to write folder names in all caps - it just looks like you're yelling). Yeah, I know it's a hard habit to break; writing Mac vs. MAC. I mean, you're gonna have to hold down the shift key a little less, and that's tough, but you should be getting used to doing things with less effort now that you have a Mac, right? Besides, you don't need to yell about your Mac. We all know how much better they are (we've been using them for years) and Mac users generally appreciate a little more subtly (you'll understand that as you get used to using your new Mac).

Anyway, Mac is the first three letters in the word Macintosh, which is a kind of an apple. Apple makes computers (and other hardware) and a Mac is a kind of Apple computer. See the correlation here, kind of witty huh? Anyway, you never see the word Macintosh with all caps for the first three letters: MACintosh. That just looks weird right? Well, using MAC to talk about Mac computers looks weird too. So, if you could just please not do that, it would be great.

Oh, before you go there is one instance where you'll want to use the all capitals version of the word MAC. That's when you need to talk about the "quasi-unique" identifier that's assigned to your network adapter. It's known as a Media Access Control address. All computers that can connect to a network have these and they're certainly not limited to Mac. Hey, I guess you also might want to use the all capitals version MAC when you're talking about MAC cosmetics as well, but that has nothing to do with computers.

Ok, so just to make sure we're on the same page... Use Mac and not MAC and we'll all get along great. Thanks!

The Cost of Idiocy

nospam@example.com (Latcarf) — Wed, 19 Nov 2008 02:21:11 -0400

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!

mod_rewrite errors on Mac OS X Server

nospam@example.com (Latcarf) — Tue, 27 May 2008 20:14:05 -0400

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:

[crit] (2)No such file or directory: mod_rewrite: could not init rewrite log lock in child

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:

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{REQUEST_METHOD} ^TRACE
RewriteRule .* - [F]
</IfModule>

To this:

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{REQUEST_METHOD} ^TRACE
RewriteRule .* - [F]
RewriteLog /var/log/apache2/rewrite.log
RewriteLogLevel 0
</IfModule>

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

Books Don't Die...

nospam@example.com (Latcarf) — Tue, 27 May 2008 14:31:06 -0400

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!

Poor Little IRS...

nospam@example.com (Latcarf) — Tue, 15 Apr 2008 00:54:49 -0400

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!

Fink on Leopard With Blocked CVS Port

nospam@example.com (Latcarf) — Tue, 26 Feb 2008 20:05:47 -0400

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:

# I needed to find where the cvs urls were set so I grepped in /sw
cd /sw
grep -R fink.cvs.sourceforge.net *

# That eventually turned up the following potential places to make changes:
lib/fink/URL/anonymous-cvs:fink.cvs.sourceforge.net:/cvsroot/fink
lib/fink/URL/cvs-repository:fink.cvs.sourceforge.net
lib/fink/URL/developer-cvs:fink.cvs.sourceforge.net:/cvsroot/fink
lib/perl5/Fink/SelfUpdate/CVS.pm: my $cvsrepository = "fink.cvs.sourceforge.net:/cvsroot/fink";

# Since I only needed to get package descriptions I figured /sw/lib/fink/URL/anonymous-cvs
# was the file I wanted change to handle my port-forward solution.
cd /sw/lib/fink/URL/
sudo cp anonymous-cvs anonymous-cvs.orig
nano -wz anonymous-cvs

# Here I changed: fink.cvs.sourceforge.net:/cvsroot/fink to: localhost:/cvsroot/fink

# Then it was a simple matter to create an ssh tunnel to an external server where I have
# the ability to login and its port 2401 is not blocked.
ssh login@domian.example -L 2401:fink.cvs.sourceforge.net:2401

# Finally, I ran the fink update command:
fink selfupdate-cvs

# Hooray. Now everything works as expected and I probaly don't need to use it again unless I need
# to update package descriptions sometime in the future. So, I changed things back:
cd /sw/lib/fink/URL/
sudo mv anonymous-cvs anonymous-cvs.custom
sudo mv anonymous-cvs.orig anonymous-cvs

# Probably I should create a shell alias like: finkselfupdatecvs to handle it all when I
# I find I want to update package descriptions again. But I'm too lazy and besides, that's
# why I've put it in my blog.

Fractal Wrongness

nospam@example.com (Latcarf) — Wed, 20 Feb 2008 13:15:14 -0400

Definition:

fractal wrongness

    The state of being wrong at every conceivable scale of resolution. That is, from a distance, a fractally wrong person's worldview is incorrect; and furthermore, if you zoom in on any small part of that person's worldview, that part is just as wrong as the whole worldview.

    Debating with a person who is fractally wrong leads to infinite regress, as every refutation you make of that person's opinions will lead to a rejoinder, full of half-truths, leaps of logic, and outright lies, that requires just as much refutation to debunk as the first one. It is as impossible to convince a fractally wrong person of anything as it is to walk around the edge of the Mandelbrot set in finite time.

    If you ever get embroiled in a discussion with a fractally wrong person on the Internet--in mailing lists, newsgroups, or website forums--your best bet is to say your piece once and ignore any replies, thus saving yourself time.

Taken from Keunwoo Lee : Lexicon 2

Idiot's Guide

nospam@example.com (Latcarf) — Wed, 06 Feb 2008 16:00:23 -0400

I saw this in the grocery store checkout line the other day... It struck me funny.

Infotrip

nospam@example.com (Latcarf) — Sun, 20 Jan 2008 00:44:41 -0400

I coined a new term the other day to describe what happens while browsing the internet and following links to various places. Sometimes, you set out to look for some information on something and end up learning about something entirely different than what you set out to research.

This phenomenon happens alot on Wikipedia but it spans the cyberspace in general just by it's very nature of "hyperlinked" information.

So my new word is "infotrip." This the perfect name for the birdwalk that so often accompanies internet research.

So, have fun "infotripping!"

New Xserve Build Machines

nospam@example.com (Latcarf) — Thu, 13 Dec 2007 18:47:30 -0400

I just got two brand new Xserve build machines and the first thing I did was wipe out the default Tiger OSX Server install and install Leopard OSX Server instead. That wasn't too bad except for the fact that I had to go through the setup assistant first in Tiger before being able to boot off the Leopard disk, wipe the drive and install.

After I got Leopard OS X Server up and running on the Xserve, I tried to ssh out from a user account to another machine (my source repository server) that's running 10.4. While establishing communication, ssh had this huge delay (more than a minute - I think). I had to figure out what was going on so I ran ssh -v to get the verbose output from ssh while it was connecting.

The verbose output showed this.

debug1: Unspecified GSS failure.  Minor code may provide more information
Server not found in Kerberos database

debug1: Unspecified GSS failure.  Minor code may provide more information
Server not found in Kerberos database

debug1: Unspecified GSS failure.  Minor code may provide more information

So, I went spelunking in and ended up comparing the /etc/sshd_config files on both the local (Leopard Xserve) and remote (Tiger source repository) machines. I found on the remote machine (Tiger source repos) that Kerberos authentication was turned off by default but commented out.

So, I changed this:

# Kerberos options

# GSSAPI options
#GSSAPIAuthentication no

to this:

# Kerberos options
KerberosAuthentication no

# GSSAPI options
GSSAPIAuthentication no

in the /etc/sshd_config file on the remote (Tiger OS X server) and reconnected via ssh without a problem. Then it was on to more work setting up my new xserve build systems.

Real Change

nospam@example.com (Latcarf) — Mon, 03 Dec 2007 16:42:38 -0400

Fix for Tor on Leopard

nospam@example.com (Latcarf) — Mon, 03 Dec 2007 04:07:44 -0400

After installing Mac OS X 10.5 (Leopard) fresh (I won't go into details ), I needed to reinstall Tor. I found the Tor expert installer didn't quite do what it was supposed to as far as creating the _tor user the daemon runs as (the user ends up a little mangled - check it out after install with dscl . -read /Users/tor) Since Leopard doesn't use NetInfo (niutil) anymore, I had to manually create the user with DirectoryServices (dscl). Here's the quick-and-dirty on what I did...

# Create Tor Group and User:
sudo dscl . -create /Groups/_tor
sudo dscl . -create /Groups/_tor PrimaryGroupID 100
sudo dscl . -create /Groups/_tor RealName "Tor Group"
sudo dscl . -create /Groups/_tor Password '*'

sudo dscl . -create /Users/_tor
sudo dscl . -create /Users/_tor UserShell /usr/bin/false
sudo dscl . -create /Users/_tor RealName "Tor Server"
sudo dscl . -create /Users/_tor UniqueID 100
sudo dscl . -create /Users/_tor PrimaryGroupID 100
sudo dscl . -create /Users/_tor NFSHomeDirectory /Library/Tor/var/lib/tor
sudo dscl . -create /Users/_tor Password '*'
sudo dscl . -append /Groups/_tor GroupMembership _tor

After that, there was still a little more to do to get Tor to run. I needed to create a place for the logs and fix the StartupItems script. Here's what I did for that...

# Create the logs directory
cd /var/log
sudo mkdir tor
sudo touch tor/tor.log
sudo chown -R _tor:_tor tor

# Fix perms on the "home" directory
cd /Library/Tor/var/lib
sudo chown -R _tor:_tor tor

# In /Library/StartupItems/Tor/Tor change TORGROUP from TORGROUP=daemon to:
TORGROUP=_tor

# Start the Tor server
sudo /Library/StartupItems/Tor/Tor start

Cool. That fixed it. Still not sure whether I want logging in /var/log/tor or /Library/Tor/var/log/tor though... Also, I guess I probably should submit all this to the Tor folks too. I'm so damn lazy.