, | Tweet this is (as of the time of this writing) a leased server hosted at and we've been there for a few years. They've been great and we've never had problems with them. Recently they informed us we needed to upgrade to RedHat 9.0 and it either involved a per-month rate increase or some finagling with the hardware and downtime. I decided this was as good a time as any to switch over to a different hosting service with Debian.

This will make the third Linux flavor that I'll have extensive administration experience with. The first two being RedHat (I've run many of the versions since 5.2) and Gentoo (which I've been running for a couple of years now). I ran Mandrake for a bit, but never really did anything with it. Same with Slackware. I toyed with Debian a couple of times, but never got past the installation.

It's all very exciting. Hopefully, everything will turn out just right.

Half full vs. half empty

, | Tweet this

I think this expression is overused. Personally, I don't think anyone gives a damn whether the cup is half full or half empty--it's wholly uninteresting.

Now whether someone is half-naked or half-dressed--either way it's interesting and tells you a whole lot about someone.

His name is Adam

, | Tweet this

There's this guy who I've met a million times and I never remember what his name is. He reminds me of Mike Pawlik (the good Mike Pawlik) and I have this urge to call him Mark, though I'm not entirely sure why. Anyhow, his name is Adam and I decided to blog it figuring that if I forgot, I could then look it up. And if my blog disappeared, it would be cached forever in the annals of the Internet history. This one tidbit of vital information will never be lost short of asteroid impact, nuclear war, and things of that nature.... On second thought, maybe I should write it down on a post-it note as well.

It's June 4th, 2009 and I have no longer have a clue who I was writing about in this blog entry.

Lyntin 4.0 beta 2 released!

, | Tweet this

There's something wonderful about releasing software. I think it's probably the relief associated with throwing it to the world and knowing that you're done with it. Of course, in this case, since it's another beta, that isn't entirely the case. Though I don't plan on touching it for a few days, at least.

Anyhow, more information at

Now I'm going to take a nap and get my clippers and go to a party because I get to sleep an extra hour tonight. Whee!


, | Tweet this

So I've been lurking on python-dev for almost a year now. I think it's been a year--might be more. I forget. My friend just sent his first post to python-dev. This is what he said:

   I'd like to suggest "outer v" for this.  The behavior could be to scan
   outward for the first definition of v.  If the only outer-scope variable
   is at module-level, then the behavior would be the same as "global v".
   Or if everyone is comfortable enough re-using the keyword "global", then
   I also like "global v in f".


It was pretty exciting. So I asked him how he felt. To this he responded, "naked".

Are the Powerpuff Girls hooked on E?

, | Tweet this

Hell no!

Of course, that's not much of an argument, so I'll quote from someone who puts it all in perfect perspective:

   "They're SD Sailor scouts, for Pete's sake! Nobody fights crime on 'e'. 
   You hug it, jump around like a moron and quietly brain-bleed for a few 
   hours after the hydrogen peroxide effect kicks in. Sheesh. If the PPG 
   girls were taking 'e', they'd be more like hyper Care Bears with that 
   popular 'strug-out Monday' look. Subtle difference, I realize, but you 
   don't see too many well delivered flying kicks at the average rave."

   Fantastic Lad (

I think that covers the issue very nicely.

It's 2:30pm--do you know what your laptop is doing now?

, | Tweet this

I know what my laptop is doing. It's compiling Xfree86. I figured I'd do an emerge rsync and an emerge -uD world yesterday. I let it run through the night and when I awoke this morning, it was still chugging through XFree86.

I must admit, it's really awe-inspiring thinking about how much code is involved and how long it takes to compile it. It makes one think seriously about the

   code  ->  compile  -> examine issues -> fix code
                ^                            |
                |                            |

methodology. Fixing a bug that way on my laptop would take weeks. When I was in college, I would tutor CS 1 and CS 2. It was difficult to watch people do theme-and-variations programming with syntax: "Maybe I should add a ; here?... Nope. How about an extra *?... Nope--that didn't work either. How about ( ) around this?... Nope..." Then I would point out, "Um--this would never work. Remove that extra *." And they would say, "Nope--that won't work because it segfaults." Then I would sit there and try to explain why the two things are completely different issues and all I'd get back would be vacant looks.

It always made me wonder why they chose to study CS in the first place. If I was studying CS and was a theme-and-variations programmer, I would either:

  1. change methodologies
  2. quit

I wonder if that's true of other jobs and knowledge spaces.

Icky code....

, | Tweet this

I'm on vacation right now. In fact, today is one of two days it's actually been sunny. Instead of sitting outside, I sat down and implemented registry entry editing--something that's been sorely lacking. Unfortunately, the hacks I just did to get it to work are really icky. A small part of me wants to sit down and refactor it right now, but the other 90% of me is thinking that I don't have vacation very often... Refactoring can wait.

This whole SCO thing

, | Tweet this

I do a lot of Linux development and most of my projects involve Linux, GNU software, Python, PHP, Apache and a variety of other Open Source software components. Naturally, this whole SCO thing has been somewhat of a surprise and originally made me hesitant since it brought up a series of questions I didn't really know the answers to.

So this whole SCO thing has been a very nice learning experience for me. I imagine it's been a very nice learning experience for many other people as well. Things like, "How can an Open Source project prevent copyright violations?" and "What are the legal ramifications of using software that doesn't come with a warranty for possible legal issues?" are being explained in very public forums--things that pockets of the Open Source community have known for many years, but which may not have been as obvious to the rest of us.

As time has gone on and SCO continues to make press releases indicating that either they are incredibly intelligent and are playing some kind of really funky publicity game or that they have no clue what they're talking about and are learning alongside some of the rest of us, various members and groups of the Open Source community (which is so large in numbers and varied in philosophies, motivations, backgrounds, worldviews, religions, ethnic backgrounds, programming backgrounds, favorite colors, spoken language, geography, vocation and such we might as well say "people on planet Earth") have responded in an increasingly comprehensive manner.

The most comprehensive article on the topic is this response to Darl McBride's most recent open letter to the community. I would posit that any C*O/person who reads that article will no longer have doubts as to the extraordinary benefits of the Open Source development model as it applies to due diligence, copyright/patent/trademark laws, and freedom.

Where I once was hesitant about various aspects of the Open Source development model, I no longer have doubts that it is a solid and valid model and will be around for many years to come regardless of who is poo-pooing it in the press this week.