I’m trying to make time to post at least something here each day. I tried to post something Friday, but it didn’t really go anywhere, and I was interrupted before I could finish the post. It wasn’t very interesting anyway, so I’ll sum it up in two sentences: If you’re a geek who wants not only to learn how to cook but just out-right learn, watch Good Eats. Alton Brown may know more about how to sauté than how to sudo, but he’s still a geek.
Now for the real reason for this post: As mentioned on the GPF site, I’ll be at Comic-Con International in San Diego, CA, July 14-17. It’s an expensive trip for us, but it’s well worth it. The title of this post says it all: it’s the comic book geek Mecca. 80,000+ people will converge on San Diego to buy stuff, talk comics (as well as lots of other popular arts stuff, like movies and TV), and meet their favorite creators and artists. I’ll be there with Keenspot, promoting the network and GPF. I’ll also be going for the meet-and-greet aspect as well, to see other online cartoonists, gawk at celebrities, and be a total fanboy myself.
For specifics on GPF@CCI, check out the GPF Comic-Con 2005 Pre-Con Report. This page will have all the details about where I’ll be when and what merchandise I’ll be bringing. I’ll update that page as frequently as I can get information, so if you’re planning to go and you’re interested in GPF and/or Keenspot activities, that’s the place to look. I’ll also try very hard to update it at least daily during the con with up-to-the-minute changes.
While I’m at it, I’ll also mention that I’ll be at Dragon*Con in Atlanta, GA, on September 2-5. It has its own pre-con report, so if that’s a closer con for you than CCI, you might want to give it a try.
Every now and then, I wonder if my geek license should be revoked. You know, those times when you come across a technological problem and you do everything you can think of–including and especially over-analyzing the problem to the point of pursuing the most extreme and obscure solution–only to find out it’s something incredibly simple or mundane.
The other times I think I should hand in my geek credentials are when I realize (or worse, I already knew but didn’t want to publicly admit) that I don’t quite know enough about something that I probably should know. Of course, not everyone can be a Fooker and know everything there is know about technology; geeks are often far too specialized, and while it’s good to know something about topics outside your field of expertise, you don’t have to be an expert. But I like to consider myself a UNIX geek. I have a Linux box (several boxen, in fact, and you’re reading pages served by one right now). At work I’ve been hacking out shell scripts, setting up cron jobs, etc. As I stated previously, I just spent a significant amount of time setting Apache’s virtual hosting just to give this site a new domain. But I have one little dirty secret I’ve been hiding for years, and now I must finally admit I have a problem.
I’m only just now learning vi.
You see, early on, I was introduced to Pico. Hold on a minute, don’t run away. Just hear me out. I was but a mere geeklet, a fledgling still being molded. At that time in college, I think I was still majoring in chemical engineering, so my computer was still mostly just a tool and a platform to play games. I had heard on the news about this “Internet” thing, and I wanted to try out “e-mail” and “browse” the “World Wide Web.” So I got an account on the school servers. This was still before they set up PPP networking, so I couldn’t e-mail or browse the Web from GUI apps on my personal machine. Instead, I had to log into the UNIX server and do things from there. And the e-mail client installed was Pine. Pico is a part of Pine (when you read or edit a message, Pine puts you into Pico), and so it was the first UNIX editor I had any experience with.
I liked Pico. I still like Pico. It’s nice and simple to use. In a lot of ways, it reminded me of Notepad or DOS Edit, which was comforting to someone familiar to DOS & Windows but new to UNIX. (Yes, kiddies, this was back when Windows ran on top of MS-DOS, when Microsoft actually used version numbers instead of dates.) I liked it so much that I was comforted when I set up first Red Hat Linux box and found Pico part of the standard install. I was also a bit concerned when I migrated to Fedora and found that it was not. It turns out since Pico is not considered free software, Red Hat decided not to include it. Not to worry, of course; I promptly downloaded it from the official site, compiled it, and installed it manually. All was right with the world. I’ve even surreptitiously compiled and installed Pico in a hidden place in my account on the Keenspot servers, just on the off chance I needed to edit a file directly there. (Just don’t tell Darren Bleuel.)
But sometimes you don’t have the luxury of installing your own software. Sometimes you don’t even have the luxury of editing a file on your PC and FTPing it to the server. You have to edit the file right there, and you have to work with the tools at hand. Such has been my recent situation at work. Technically, I’ve been developing in a production environment (instead of a dedicated development environment, for shame), and since I’m not allowed to know the production passwords, someone else has to log me in. Ergo FTP is out of the question. The C compilers on these machines are either crippled or non-existent (i.e., the customer won’t pay the UNIX vendor to install a full compiler and the SAs are too lazy/clueless/difficult to install a free compiler), so installing my own software is moot.
So here I am, learning vi.
I, of course, know the legends of vi. It’s cryptic commands, it’s arcane interface, the eternal holy war with Emacs… I’m certainly geek enough to keep up with all that. I’ve just never sat down and actually learned how to use the darn thing. Fortunately I have a very handy book and a wife who happens to know more about vi than I do. I’ve become fairly competent with it, to the point of actually looking up commands in the aforementioned book just to make things easier (like using “D” to delete the rest of a line instead of repeatedly using “x”). And it’s become so much of a habit that I’ve caught myself automatically typing “vi filename” on Demeter (my main Linux box) instead of “pico filename.” It’s only when vim starts showing things in all different sorts of colors that I realize what I’ve done.
Perhaps some of the more technically inclined out there may think less of me for admitting this. (If you do, get over it; half of this has been a joke anyway. And if you’re an Emacs fan, I’ve been just as afraid of it as I’ve been of vi.) But the soul-searching and growth has been liberating. Maybe now I’ll be motivated to learn something else, like sed or awk.
Nah. I already know Perl. What’s the point? 😉
Well, for all of you who have been paying attention (both of you… meaning my two eyeballs), I’ve made another change. This time, I’ve moved the blog from the gpf-comics.net domain (which serves the GPF Store) to jeffdarlington.com. The blog itself hasn’t moved; it’s still on the same physical machine in the same ol’ directory. I just thought I should eventually register a domain with my own name (something I’ve thought about doing for a while now, but never got around to it), and I needed somewhere for it to point to. So here it is. It took a while to get all the virtual hosting stuff to work, but between this and some work I’m doing in my day job, I can safely say I now know a lot more about the configuration and maintenance of Apache than I used to.
Of course, all this tweaking meant that I would have to eventually rebuild the MT files, which of course meant I would end up with another blank front page. Thus, another pointless entry to make sure the front page isn’t blank. 😉 However, I am considering on making this a more active blog and a more regular part of my life. So maybe you can expect this site to update more frequently than once ever two or three months. 😀