My companion on the commute home is almost always Dave Ramsey -- he's the man on personal finance and to a certain extent, personal responsibility. Since I listen to him everyday, I was curious to browse his book, The Total Money Makeover.

It was what I expected: a concise, easy to understand plan for getting one's financial house in order. Dave is an anti-debt guy through and through. He lays out simple and effective steps to get your financial life under control and moving in the right direction. I'm already going that way, so a lot was review. I will however keep this book tucked away and ready for anyone who's in trouble and doesn't know where to start. It's not technical, just a plan. There's no doubt that doing his proverbial Baby Steps will get things done.

So, read it. It's not exciting since it's so practical. But it you don't know how or where to start spending less than you earn, this is the book.

Plopped my self down to check email and there's a weird one: "Hi Paul from Google". Of course, my first thought was 'Spam!' The subject is odd, a bit awkward, and spammers are known to put names in subject lines to sneak past the filters.

But, my filters are pretty tight. Why'd this one make it through I wonder?

Well, after checking the headers, I found out it was really from Google. Wow! So, I called the guy. He was really friendly and very clued in. Right off the bat, in the very first call, he asked me some very difficult questions. I could answer them, but trust me, they were difficult.

Two more really, really thorough technical interviews came next. Not much to say about them, but I can't over-emphasize that they are looking for quality engineers and are not going to waste time asking easy questions.

Wow! Got invited to NYC for a interview. I did say all along that this was my goal. I knew that thousands of people apply to Google ( I hadn't ) and that they only take the best of the best. What I did want, and eventually got, was a chance to visit the office, and run the gauntlet myself.

Took Amtrak up to the city, what a great way to travel. Found my way to the offices, and they're just like you read about. There's a central rec-room of sorts with air hockey, pool tables, massage chairs, etc. That day's TechTalk speaker was Seth MacFarlane, from the Family Guy. There was a electronic drum set with headphones for a little venting. There was a major Lego center with thousands of bricks and completed and in-progress projects laying around. There were also sweet little common areas stocked with snacks, drinks, coffee, the works. In all reality, it's neater than I thought it would be. It's the Wonka's of the IT world.

I was intellectually beaten and abused during the interviews. Let's put it this way: I know more than the average bear about Linux, UNIX and networking. The questions I had to deal with were masterfully devious. I got the distinct feeling that they were being good engineers and testing to failure. The only question was, did the test material fail before or after the requirement?

Well, I didn't make the cut. ( I did however get the shirt! ) Not sure how I feel about it. The good news is that I no longer have to face the decision on whether to move away from our families or not. I do love most parts about my current job too, so that's good.

The real benefit to this, other than a good story is that I'm re-inspired. I got the puddin' kicked out of me by intellectual big-leaguers. I've been working hard, but I haven't been really stretching myself to grow to a an entirely new place. That needs to happen now.

Thanks Google.

Lone Survivor

I have no idea how to write a review compelling enough for a book like this. It's the eyewitness account of Operation Redwing, a SEAL team insertion of four men into the mountains of Afghanistan. Marcus Luttrell was the sole survivor of the absolutely unbelievable battle against a smart, well-armed force operating in familiar terrain. In particular, it details the actions of Lieutenant Michael Murphy, the nations most recent Medal of Honor recipient.

Sometimes, when you look around, and see stuff falling apart, and you wonder what happened to all the heroes. Well, they're out there now, dealing with the cold, the heat, the rain and the danger. There's hope after all..

Read this book -- I mean it. I don't care if you're into military history or not, it's the least you could do.

Ugh.. This fix sucked up enough of my time, that I decided to post on it. Maybe it will save someone else...

Ebay's HTML editor just would not show up in IceWeasel ( Firefox ) browser on a Debian Etch system. Killin' me for over an hour... Javascript, Java, Flash, then back to the Javascript console.

Then, finally, I stumble on Bug #408864, which tells me to change my User Agent string to Firefox.

It worked.

Just so you know...

For reasons I won't get into (and am not particularly happy about), I wanted to put up a windows partition on my workstation.

Windows doesn't want to install anywhere but your primary master, so I unplugged my hda (Debian) stuck the to-be windows drive in and installed Win2K.

Cool.

Get in, add a stanza to grub that looks like this:

title=Win2K
root (hd1,0)
makeactive
chainloader +1

Well, the passover to the windows bootloader chokes. I keep getting "Filesystem type unknown, partition type 0x7".

After a lot of pain and googleing, I figure out that the general problem is that when the windows install happened, it was the primary disk. Now that I put my linux disk back in everthing's not where it's' supposed to be (according to the windows bootloader.)

Solution: Right as grub kicks off on hda, switch the two drives so windows boot loader doesn't get confused:

title=Win2K
root (hd1,0)
map (hd1) (hd0)
map (hd0) (hd1)
makeactive
chainloader +1

Over the years, I've used a variety of bootable tools. Very handy stuff to have for building and repairing machines.

My tried and true for a long time was Tom's Root Boot, which was originally for a floppy. For a while, I was even burning that image to bootable CDs.

Time progressed though... The floppy is dead, and USB media and CD are fairly easy to boot. That brought about a whole series of really neat bootable projects. I moved on to the Ubuntu Live project. It has the tools I need (chown, grub/lilo, cfdisk), but it isn't exactly geared towards emergency work.

For some reason lately, I've stumbled across the Ultimate Boot CD. Wow. Reminds me of the old Norton Disk Doctor days. There are a boatload of utilities available here. All of the vanilla partitioning stuff you'd expect, but also:

• NTFS analysis and password recovery
  
• Hard drive utils for the various manufacturers
  
• Wiping utilities
  
• Burn-In applications
  
• Memory tests and identification
  
• Benchmarks
  
• BIOS Stuff
  

Overall, a real must-have. Too bad it doesn't fit on one of the smaller shirt-pocket size CDs... But beggars can't be choosers and this is one fine tool to have in the old emergency kit.

Someone asked for my brisket recipie -- may as well stick it up here so that everyone can have a shot at it...

------

Well, I don't exactly have a recipe, but here goes:

1) Get a nice brisket. A whole brisket has two parts, 'point' and 'flat'.
You'll have to go to a butcher to get a whole one, which has more fat/flavor
and is pretty big (20 lbs or so.) The one I sent over was just a flat, which
is what you'll get at Klein's, etc.

2) Get it out the night before and give it a good dry rub, then cover it and
let that soak in overnight. I'm always experimenting, and used leftovers
from another project that particular day. I'm pretty sure it was this
recipe, but w/o the MSG.

There are a million rub recipes on the web, this just happens to be the one I
think I used. Feel free to substitute one that looks good to you. Don't
feel like you have to get it all on there -- rubs always seem to have
leftovers. Put on more than a sprinkling and less than 'heavy'. It's just
something you have to figure out on your own.

1 Cup Sugar
1 Cup Non-Iodized Table Salt
½ Cup Brown Sugar (Dried out lightly by exposing on cookie sheet room temp.
several hours, or slightly warmed)
5 Tablespoons + 1 Teaspoons Chili Powder
2 Tablespoons + 2 Teaspoons Ground Cumin
4 Teaspoons MSG (Accent)
4 Teaspoons Cayenne Pepper
4 Teaspoons Black Pepper freshly ground (important)
4 Teaspoons Garlic Powder
4 Teaspoons Onion Powder

3) Cook that baby for a long time over low heat (225 degrees). You'll need
1 1/2 to 2 hours per pound. I smoked it over charcoal, with fist-sized
chunks of hickory for flavor. I'm sure the oven would do a fine job too, and
be a whole lot less to deal with.

4) When the internal temp is around 170, wrap it tightly in heavy-duty foil.

5) When the internal temp is around 190, take it out of the oven / smoker.

6) Wrap it in an old towel, (in case it leaks) and stick it a small cooler for
at least an hour. This is the real 'trick', I think. It lets the juice back
into the meat and really finishes it nicely.

7) When you open it up, it will still be very, very hot, so be careful. Save
the juice from the foil.

8) Brisket has a strong grain to it. Slice across the grain and pour the foil
juice back over the meat.

9) If you like, wet the meat down with a BBQ sauce of your choice. I like
sweet more than hot. My personal favorite is Sweet Baby Ray's, which should
be easy to find.

Please let me know how it turns out.

Ever want to tar a lot of files (> 12000) and hit this limit? It's not tar's fault, nor is it 'mv', 'cp', or whatever else. As a matter of fact, it's not really even from your shell. Each shell session has a pre-configured amount of storage with a hard limit. To check it, thry this:

getconf ARG_MAX ===> 131072

What you'll need to do is to work around this. For tar, I found some good advice on pre-building a list of file-names and then passing the one pre-saved list to tar. That worked fine:

# cat names of all desired files. redirect to one file
find . -iname '*.daf' > my_file.lst
# run tar, passing that list in
tar czvf my_archive_file_name.tar.gz --files-from filelist.txt --remove-files

Another thing you can do is to use 'xargs', which is documented in the GNU FAQ:

find htdocs -name '*.html' -print0 | xargs -0 chmod a+r

I've been (happily) using OpenOffice for a couple of years now. The recent release 2 however uses a whole new document format. Of course, it can open older stuff. I've been manually upgrading formats as I need various documents.

That's a good way to get burned though. Ideally, you should figure out a way to batch convert any document formats that change. (Hence my affections for ASCII, but that's another post.) This article looks like it contains all the clue's you'd need to do that, but at this very moment, it looks like I've got other bridges to burn.

Here's a good article on mass-converting Office documents. It's written by a guy named Bob DuCharme, which is funny because I've had a document around here for ages in my reference directory written by him. It's a masterful quick and dirty introduction to operating systems, one system per chapter. In the work I do, you just never know what kind of system might present itself, so I've hung onto that article for a a long time.

(Funny how even on the Internet, it's still a small world.)

So, you have a linux box that's been running a while, and has had a lot of upgrades over the months or years. What happens is that you'll have support libraries that either have been superceded, or you'll have an application removed that was the last dependent package on a library.

If you want to clean those up, run this command (as root) until it comes up empty.

dpkg --purge `deborphan`

The first thing to happen is that debporphan runs. It returns a list of libraries that no package is dependent upon. The backticks (with the tilde, not the single-quote) are special. They take the results of the deborphan command and place those results into the dpkg command. In otherwords, dpkg gets a fresh list from deborphan each time this command runs.

Freeing one library, might create another library that can be purged, so it might take a couple of shots to be thourough.

Maybe you're not too web-savvy. Maybe you've heard of terms like RSS, Atom, or FeedBurner.

They're all ways that you can take advantage of emerging web standards. Almost every new site will let you link to it, with an RSS reader. That means that they're exporting the content in a predictable way that you can read in an application other than a standard web browser. (If you've been around, you'll realize that it's very similar to USENET newsreaders. But, if you know what USENET is, then you probably know about RSS too.)

So, set yourself free. Stop wasting time getting lost in one site after another. Stop checking to see if a favorite site has new content or not. Go get yourself an upgrade, and check out a better way to read....

This article on 'web feeds' at wikipedia will lead you to all you ever wanted to know.

PS: If you're on linux, take a peek at the Liferea RSS reader.