A friend told me he’d gone hiking around Angeles Crest.
“I thought it was still closed.” “Nope!”

Sure ’nuff, I check the CalTrans and CHP websites, and they show Hwy. 2 as having no closures. This morning I get my camera and hiking gear to tour the devistation.

Sure ’nuff, when I get to the National Forest entrance, the road is closed.
I’m going to have to ask him about it…

I was just upgrading my packages, like I do every so often. This time ’round the package update list was:
bash bluez-utils dkms-ndiswrapper e2fsprogs grub grub-doc libgcc1 losetup
ndiswrapper pclinuxos-release update-notifier

Went ahead, it installed cleanly, but afterwards I was getting floating point exceptions from some programs. ldd shows libgcc_s as a likely culprit, what with the just-done upgrade including
libgcc1-4.4.1-1pclos2010.i586 ############################## [100%]

Play around with apt-get, to see if I can get an older version from apt — uh oh, apt-get says floating point exception when invoked. Grab a Mandriva RPM from the net, give it to rpm — rpm dies with floating point exception. No problem, I’ll install the files by hand, just extract them with rpm2cpio — which hits a floating point exception.

Finally, I wise up, scp libgcc1_s.so.1 from a Debian system.
cd /lib
sudo mkdir brokengcc1
sudo mv libgcc_s* brokengcc1
sudo cp /tmp/libgcc_s.so.1 .
sudo chmod 0755 libgcc_s.so.1

And everything is working again, at least enough to tide me over until PCLinuxOS fixes the libgcc1 package. If anyone else is stuck by this, the libgcc I used is here.

Quick quiz: How do you find the arguments to your Scheme program?
  a) argv
  b) *argv*
  c) command-line
  d) program-arguments

Answer? It depends on whether you’re using Guile, SCM, umb-scheme, or mzscheme! That’s right, it’s impossible to write a Scheme program that takes arguments and is portable across implementations. Winnar.

Update: In 2013, option (c) was standardized.