Archive for October, 2004

Moved

The website hosting move has been a success. I’ve had a total of 8 hits on the old host today, so I guess the address propagation is nearly complete. Everything seems to be working fine at the new host. Spent a little time this morning setting up AWStats on the new host. That’s the package my old host offered, and I’m used to it. Eventually, I’d like to put together something of my own to do more specific analysis, but that’s a ways down my list.

My new hosting provider is Dreamhost. My old host was fine, but I really wanted shell access, which they didn’t offer. The plan I’m on now lets me host up to 15 domains, of which I’m using two. By paying for 2 years in advance, I’m paying the same as I was previously for two separate single-domain packages. If I ever need another domain (or 13), I’m all set. Sure am loving the shell access.

I’ll make a final check of my pop3 account at the old host tommorow evening, and Monday I’ll call and close the old hosting account. Prepaid a year in August, so I’ve even got a refund coming.

Moving Day

Today I’m initiating the DNS change to point the domain jclark.org at my new hosting provider. Apologies in advance if anything goes awry.

If this is the last sentence you see, you’re viewing the old host.

And if you’re viewing this sentence, you’re viewing the new host. Woohoo!

Update: The move has been remarkably painless. Mail seems to be working, site’s working fine. Bloglines sees the new site, as do my home and work broadband connections.

Also, I’ve re-enabled comments. I haven’t got the blacklist in place yet; I want to try to build in a performance enhancement first, and I need to setup an extra Perl module to do that. More on that later.

Update 2: Big thanks to Dugh for the heads up that my comments weren’t working. All fixed now.

Magic with wget

As mentioned previously, I’m in the process of switching hosts. Last night I uploaded my entire site at the new host, and set everything up. Along the way, I decided to refine my internal directory structures a bit. Everything is working fine on the new host, and once I get the e-mail accounts squared away I’ll be ready to make the DNS switch.

In the meantime, I have a synchronization problem. When I uploaded my site to the new host, I used a site backup (tarball) from the old host. This made it easy to preserve directory structures as well as timestamps. Because of the way Blosxom works, the file datestamps on my posts are very important… Blosxom uses them for the post date/time. After the upload (and after I moved a few things around), both old an new sites were in sync, with the same posts in the same categories, and having the same timestamps. From that point on, new posts to the old site are out of sync with the new site. Posting to both locations is no good; the timestamps will be off and it breaks the programmer’s first virtue (laziness). I can’t use scp because my old host doesn’t offer shell access.

I went looking for a way to transfer a file from the old host to the new host, preserving the timestamp, and preferably making it easy to keep things in the right directory. I’ll have to run this after each post until the old site goes away. I looked at cURL first, but it didn’t quite do all I needed, so I turned to wget. Magic ensued.

The setup: from the shell account on my new host, grab the file from my old host. The file can only be retrieved from the old host via FTP. As an example, I wanted to sync my prior post on the new iPods. It’s in the category Apple and the “stub” title is newpods. On the old host, the file is in /blosxom/Apple/newpods.txt. On the new host, it needs to go into ~/jclark.org/blosxom/content/Apple/newpods.txt. I didn’t want to specify the directory in both the source and destination. The solution:

cd ~/jclark.org/blosxom/content
wget -N -x -nH --cut-dirs=1 ftp://jclark.org/blosxom/Apple/newpods.txt 

The first command just puts me in the base directory for my posts on the new server. The magic is in the wget command. -N turns on timestamping, preserving my timestamps. -x forces wget to create directories locally to match the remote (this is the default for recursive fetches). Normally, the dirs created would start with the host name (e.g., jclark.org), but -nH removes the host name. Finally, –cut-dirs removes directories from the front of the path, so the file blosxom/Apple/newpods.txt on the remote end becomes Apple/newpods.txt locally. This combined with the initial cd lets me handle the changes I made to my directory structure. After I publish this post (on the old host), I’ll run the same command from the new host, plugging in the new file/path.

One detail of note: the above wget command will try to login anonymously, and give up if it fails. You can specify user and password on the command line, but bad idea on a shared host (think ps -aux, although my host protects against this). If you specify the user without password, you don’t get prompted for a password. The way around this is an old UNIX standby, the .netrc file.

New iPods

Apple today released two new iPods: the iPod Photo and the iPod Special Edition: U2. Both have been rumored for a while.

This interests me because I’ve recently decided to get an iPod. I’ve wanted one for quite a while, but hadn’t really been able to justify the expense. I considered asking Sherri to get me one for Christmas last year, but requested the Firewire HD and DVD Burner instead. With the growing size of my music collection and my new interest in Podcasting (I’m tired of burining CDs every day for my commute), I’ve made up my mind to get the iPod. I’ve been trying to decide if I should put it on my Christmas list, or wait until my birthday (in February) since Apple usually anounces new iPod models at Macworld in January. Looks like it’s safe to shoot for Christmas… now, which one?

The field before today had three choices: the 20gig model ($299), the 40gig model ($399), and the Mini ($249). The mini is out- I want storage. Of the standard models, the 40gig makes a much better choice for me. Besides double the capacity for only $100 more, the 20gig model doesn’t come with a dock or remote. I want the dock, and it’s $39 separately. Might as well get the 40gig.

Now we come to the new choices. First, the $349 U2 iPod. It’s a 20gig iPod for $50 more than a standard 20gig iPod. For your $50, you get a black iPod with a red scrollwheel, signatures from the band laser-etched on the back, and a $50 credit towards a 400+ song “digital boxed set” of all of U2’s music from the iTunes Music Store. I find it interesting that there’s no indication of the price of this “digital boxed set”, which won’t be available until the end of November. I’m not a huge U2 fan, so the boxed set is irrelevant to me. The black iPod would be sharp without the red scroll wheel, but with it, it’s quite atrocious (at least in photos… I’ll report again once I see it at the Apple store). This one’s out of the running.

This brings us to the product everyone will be talking about, the iPod Photo. Available in 40gig and 60 gig flavors, it looks like a standard iPod but with a color screen. It can store photos which you can view on the 2″ screen, and it comes with an A/V cable you can use to show your pictures on a TV. The battery life appears to be a bit longer than the b&w iPod according to the spec sheet. The 40gig model is $499 and the 60gig model is $599.

The new device is intriguing. We have taken all of our pictures with a digital camera for a couple of years now. Having a Series 2 TiVo on my home network lets me view photos on my TV, and it turns out to be great. These days, we just dock the camera, push the dock’s sync button, and head to the family room to see our pictures on the big screen. The only downside to the TiVo setup is portability; an iPodPhoto would make an excellent way to show photos to everyone when we visit family. Aside from pictures, the extra capacity of the 60gig model sounds nice.

Being already prepared to spend $399 for a 40gig (standard) iPod, is it worth $100 more for the photo feature? If so, is it worth another $100 for the extra storage? If the photo option isn’t worth $100, is the storage worth $200? I’m sure for some, the answers will be yes. For me, I don’t think the benefit of the photo feature is worth the cost. I would use it some, but not enough. And $200 is too much for the extra 20gigs storage. If they offered a 60gig standard iPod for $499, I might consider it. Then again, Macworld is only a couple of months away….

Mail Issues

I’m in the process of switching hosting providers (more on that in a later post). If your mailhost is at Dreamhost (my new provider), you may not be able to send me email until I get everything sorted. In the interim, if you send me mail and it bounces, you can contact me at jason.clark {at} comcast.net.