Tag: Rants

I have a somewhat antique Palm Zire 71 that has, periodically, synced perfectly with various flavors of GNU/Linux. On the other hand, sometimes a new release / kernel / version prevents it from syncing at all.

My life is simple enough that I really don’t need to actively sync it with an online calendar, which is a damn good thing. Back when I needed to do hotsyncing, it always came heartbreakingly close to working; apparently that’s still the case. Having to comb out a complete set of duplicate addressbook entries pretty much soured me on futher experimentation.

Currently, the Zire on the outs with Ubuntu / Kubuntu Hardy. The hack that makes it work goes a little something like this:

The file /etc/modprobe.d/libpisock9 blacklists the visor module, which allegedly lets all the pilot-* programs connect using libusb, but that flat-out doesn’t work for me.

Replace this stanza inside /etc/udev/rules.d/60-symlinks.rules:

#KERNEL=="ttyUSB*", ATTRS{product}=="Palm Handheld*|Handspring *|palmOne Handheld", \
#                                       SYMLINK+="pilot"

With this one:

BUS=="usb", SYSFS{product}=="Palm Handheld*|Handspring *|palmOne Handheld", \
KERNEL=="ttyUSB*", NAME="ttyUSB%n", SYMLINK+="pilot", GROUP="dialout", MODE="0666"

Make sure you’re in the dialout group. If you’re not, add yourself, log out, then log back in again.

I back the Zire up once a month, which is rarely enough that I just load the visor module by hand:

sudo modprobe visor

Create a directory for backing up into:

cd ~/Zire71
mkdir 2009-01-03

And then backing up the Zire is easy enough. Pop the thing in the cradle, poke the hotsync button, and quick like a bunny whack Enter on this:

pilot-xfer -p /dev/ttyUSB1 -b 2009-21-03/

The ttyUSB1 device will, of course, vary depending on whether you have any other USB-serial gizmos plugged in at the time.

Frankly, the utter unreliability and instability of this whole USB PDA mess is one of the reasons why, IMHO, GNU/Linux really isn’t “ready for the desktop” despite the fact that all our boxen here run it. I don’t particularly want a phone / camera / PDA / ebook reader / pocketwarmer, but I can see I’ll wind up with one some day just to get a USB interface that actually works.

Memo to self: remember to modprobe visor

Update: Xubuntu 8.10 fixed all that, so USB hotplugging seems to work right out of the box. Install pilot-link, then just:

pilot-xfer -p usb: -b /path/to/backups

Now, whether syncing to contacts & calendars works correctly, I cannot say.

Remember when they said CDs would last for a hundred years?

Some years back, a bit o’ PC shuffling around here spat out a 60 GB hard drive and brought the Big Box of CDs up from the fireproof safe at the same time. A little mental math: hey, why not?

Turns out that all 130+ of my “purchased” CDs, mostly with Windows programs & device drivers, add up to 42 GB of ISO images. Creating ISOs is trivial with Linux:

dd if=/dev/cdrecorder of=image.iso

and you’re done. Depending on your system, you’ll get faster transfer with a bigger blocksize: bs=1M is more than enough.

I used the two upstairs PCs as readers, with the hard drive installed in the milling-machine PC downstairs. It took the better part of a day to think up file names and feed CDs into the slots. Typical speeds were 3 MB/s, dropping dramatically with read retries: a minute or two or three per CD. The average CD is half-full.

I wrote a trivial script to do the tedious work: loaded the CD, issued the dd command, computed MD5 checksums on the raw CD data and the stored file, and ejected the CD. The checksums always matched except when the disc had read errors, but gave me confidence I wasn’t losing any bits along the way, because the CD got read twice and any marginal sectors that were fixed-in-error would pop out.

One CD was completely unreadable because of a nasty scratch. Another, never used, turned out to be cracked in the sealed envelope.

What’s scary is the number of previously good, visibly undamaged, used-once-or-twice CDs that couldn’t be read in at least one drive. I don’t abuse the things and I -know- some of these haven’t seen the light of day more than once or twice.

Dozens (I lost count) weren’t readable in at least one drive and many weren’t readable in three drives. If you happened to have two of those drives in your one-and-only PC you’d be sunk without a trace.

I had a visibly undamaged CD that couldn’t be read in any of the four drives, although rubbing it down with toothpaste (got nothing to lose!) persuaded it to play in the CD burner. Perhaps a minute scratch? Dunno, but if that CD was damaged, then you can’t even look at ’em without damaging the things.

The most reliable drive was a CD-only burner. The DVD-ROM and DVD-burner drives could read most discs, but fell flat on others. There’s no obvious difference between a DVD+(only) burner and the DVD+/- burners.

Bottom line: maybe a quarter of those spendy pressed commercial CDs on your shelf won’t work when you really need to reinstall those programs. Should you happen to do an installation that doesn’t read the part of the CD with rotten bits, then you’ll never notice. I was copying the entire bit stream off the disc, so every single sector had to pass muster. How lucky do you feel?

If you think you’ll ever need ’em again, get ’em on a hard drive now. Then you can burn ’em as needed. Oh, yeah, put the serial number right in the file name, too, it’ll come in handy.

Hundred years, ptui!

Back then I didn’t know about GNU ddrescue. Now, I do. Life is good. Well, better.

Update: Nowadays, I keep everything on a 500 GB drive in the file server, which does a daily backup to a 500 GB external drive. Once a month, more or less, I dump the contents of the daily backup drive to a similar drive that lives in the fireproof safe.

Tip: mounting an ISO is easier than finding & mounting the CD. They’re served up over an NFS share mounted locally at /mnt/diskimages, so it goes a little something like this:

mount -o loop,ro /mnt/diskimages/ISOs/name-of-CD.iso /mnt/loop/

and away you go. The ro option keeps you from screwing things up with an inadvertent write.

That doesn’t work in Windows, more’s the pity, but you can find GUI utilities that more-or-less do the same thing from a SAMBA share. Not that I care all that much.