On my (n + 1)th installation attempt

Every week or so, I have a 30 minute block of time where I decide I'm going to go tackle installing Debian on my Dell Inspiron 7000. It's good for me to keep trying this because it's incredibly humbling.

The machine has a CD-ROM drive, but it doesn't handle CD-RW discs (or at least it doesn't handle the ones I have). So every attempt I make, I create a coaster.

Going to try one more time. This time with a Knoppix cd. The biggest problem I'm having is getting the machine on the network. Once I get that done, then I'll be ok. But I can't seem to get the machine on the network with either my 3Com 10baseT pcmcia card or my SMC wireless pcmcia card.

One more time....

No more Gentoo for me

I was running Gentoo on my Dell Inspiron 7000 laptop but today I've gone and slicked it. I'm going to switch my laptop over to use Debian. Gentoo is pretty neat, but it takes me days to compile GNOME and I'm hitting the point where the novelty is wearing off and I want to actually use my laptop.

Anyhow, I recommend it for folks with more powerful machines. I enjoyed running it and learned a lot in the process.

Dusting off Lyntin

After a hiatus, I made some changes to the Lyntin website after looking at the Groovy web-site which I discovered after reading Ted's blog.

It's interesting how I can work on something for tens of iterations honing it here and tweaking it there. Then I'll see something that's very similar to what I'm doing and suddenly everything clicks and voila I realize what big changes need to be made for a dramatic improvement.

Anyhow, there's a bunch of stuff in CVS for Lyntin that should get summed up into a release. I may tackle Telnet LINEMODE handling (which really needs to get done) and also the MCCP plugin. Eugene has a really slick curses ui which I think has reached a point where it should get included in the main distribution.

Things are afoot once more!

Wacky weather day

Today was one of those weird New England days where every weatherman was right--didn't even matter what they predicted. On the drive to work it was overcast. At around noon it was snowing with heavy gusts of wind that made the snow go horizontal. At like 2, the snow had turned to rain. At 5, it was sunny and while there were a few clouds dotting the sky in wispy trails, there wasn't any evidence of rain or gusty snow. Wacky.

verify_installation for pyblosxom

A couple of weeks ago, I checked in code to help out PyBlosxom installation and configuration. I made changes to pyblosxom.cgi so that you could run it from the prompt:

./pyblosxom.cgi

It tells you your Python version, OS name, and then proceeds to verify your config properties (did you specify a valid datadir? does it exist?...) and then initializes all your plugins and executes verify_installation(request) on every plugin you have installed that has the function.

As a plugin developer, you should add a verify_installation function to your plugin module. Something like this (taken from pycategories):

def verify_installation(request):
    config = request.getConfiguration()

    if not config.has_key("category_flavour"):
        print "missing optional config property 'category_flavour' which allows "
        print "you to specify the flavour for the category link.  refer to "
        print "pycategory plugin documentation for more details."
    return 1

Basically this gives you (the plugin developer) the opportunity to walk the user through configuring your highly complex, quantum-charged, turbo plugin in small baby steps without having to hunt for where their logs might be.

So check the things you need to check, print out error messages (informative ones), and then return a 1 if the plugin is configured correctly or a 0 if it's not configured correctly.

This is not a substitute for reading the installation instructions. But it should be a really easy way to catch a lot of potential problems without involving the web server's error logs and debugging information being sent to a web-browser and things of that nature.

But the printer was just fine...

I was printing out the 1,203,481,288 pages involved in my tax return on my HP OfficeJet Series 700 printer which I got from my uncle a million years ago back when printers would print one dot at a time and it sounded like disco music, when suddenly an error message pops up saying in really big letters:

PRINTER ERROR

The computer has lost communication with the printer.

Cancel printing, turn the printer off, then back on, do the hokey pokey,
burn incense, twirl three times, tap your heels together and then
try printing again.

I'm skeptical of stuff like that. I'm a programmer--I'm fully aware that computers and software have no clue what they're doing. My printer was still printing the pages--albeit so incredibly slow that a three-toed sloth would start getting impatient. I figured I'd wait until the printer was done doing whatever it was doing.

I came back 24 days later to discover everything printed out just fine. And in color--I had no clue this was a color printer!

I still don't know what that error was all about. Maybe the software didn't expect the printer to take so damned long? Who knows? Regardless, I'm done filing my taxes, it's 60 degrees outside, and I'm going to go get some breakfast.

Bluesock died on Tuesday; resurrected on Thursday

Yea, and lo Bluesock did gasp its last breath early Tuesday morn and exhaled ne'er to be revived again. And lo, all my friends called me up to tell me the news. I submitted two, nay three, tickets in the tech-support ticket system. Minutes turned into hours.

Yea verily yea, Rob of the clan Atha did calleth up the ServerBeach people and gave them angry Texas hell and they agreed to give us some new hardware. Forsooth it turned out to be a defective disk or motherboard or some such hardware issue (or so we think--hard to tell when I'm in Boston and the server liveth in Texas).

Then on the second day, Bluesock rose again with a new mortal coil and the old drive was mounted as a partition of the new. With great speed, we re-configured and re-installed all the stuff we had configured and installed on the original Bluesock.

Then when we were done, it was as if the tragedy had never occurred. The users were happy once more [1].

Every language war ever

I keep getting into the classic "your language sucks; mine is better" discussions with various people. Regardless of what they say, I still like Python, C, sort-of like Perl and dislike Java. Some day when I have a free moment or two, I'll remember/learn enough SML/Lisp to like that again as well.

Link to Every Language War Ever

registry v.1.3 released

I decided the registry plugin needed to allow users to see all the pending submissions and details therein. So I made some changes:

  • added handling of /registry_queue which shows all the pending submissions.

  • added some code to displaying of the entry so that the "edit" link doesn't appear if there's already a pending change.

Get it on my pyblosxom page.