Category: Rant

Another sleepless night

I was having trouble sleeping. I thought it was because I have a sort of “rubbed raw” feeling in my arm pit. I got the same thing last time – because I can’t lift the arm, my arm pit doesn’t dry out properly and so it rubs painfully. But then I realized there was a lot of light coming from my office. And so I went to have a look, and sure enough my Linux box had crashed, frozen on boot, and so therefore the screen saver wasn’t shutting down the monitors properly.

A few days ago I got a little overzealous in removing old kernels, and since then every time the update process has installed new stuff it’s given me a failure message about running lilo. (Yes, I still use lilo rather than grub because when I first installed this system you couldn’t use grub with a software raid and lvm2 – one of these days I’m going to have to reinstall just to correct that and a few other nagging problems)

I realized that if that was the cause of the problem, I was going to have to boot with a live or rescue CD and remount everything, chroot to it, and fix the lilo problems and run the lilo installer command. So the first thing I tried was downloading the “Ubuntu Rescue Remix”, burning a CD with it, and booting with it. I discovered the hard way that the “Rescue Remix” is a i686 kernel, which means I can’t chroot to my amd64 install and expect to run commands. Oops.

Next I started to download the latest Ubuntu CD. Chrome said I had 27 minutes remaining, so while I waited I dug out the previous Ubuntu CD, and booted with that. I had to “apt-get install lvm2” and “apt-get install mdadm”, but afterwards I was able to “mdadm –assemble” both software RAIDs, and mount the lvm2 partitions under /mnt. I chrooted to /mnt, and ran “lilo”. First problem was that the boot drive was specified using /dev/disk/by-id/…., which it didn’t like in the chroot environment, so I changed that to /dev/sda. Then it complained about the “Linux.old”, so I commented that out. With both of those changes made, lilo installed without any further errors, and when I rebooted everything came up fine.

I’m just manually restarting all my nightly backups which normally happen during the time the computer was down, and then I’m going to try to get an hour or two sleep.

Forth? Why Forth?

Had a dream last night, in which the programming language Forth played a big role. Which is a bit of a puzzlement because I’ve never learned to program in Forth. There was a time when Forth was tagged as the next big thing and every computer magazine had articles about it, but that was around the time when commercial software started advertising “written in C for speed” and an interpreted language like Forth didn’t have a chance. I believe Forth became the core of PostScript.

The first thing I remember from the dream is seeing two small computers with a wire connecting their ‘pin 1’s. Somebody asked the Forth guru why they were connected, and I said “I know that, it’s so their clocks are in sync” and I said something about events on rising edges. I have no idea what that’s about – I’ve never done anything that low level. Evidently my dream self has been taking electrical engineering courses.

Later I was talking to the guru in front of three real train tracks, and every time a train went by a single alphanumeric letter above the track lit up. I wonder if that is some dream reference to the famous Tech Model Railway Club, but I really only know about them from the Jargon File. I wonder if they used Forth?

Later the guru was showing me about ports to respond to external events and control things like lights and heat in a house. I distinctly remember a panel showing four room mates and an indicator of whether they were using Forth to control their thermostats or not.

Anyway, it seems odd to me to be dreaming about a programming language I’ve never used, and low level hardware stuff I’ve never done. Not sure if that’s a subconscious reflection of my recent surgery, or trying to do object oriented programming in Perl.

No good news on the medical front

I had a talk with my shoulder surgeon yesterday. He said my MRI didn’t show any “smoking gun”. There was a little damage where the acromium meets the collar bone. There is also evidence of bone bruising, but I’m not sure how that could have happened or how it could be causing a problem that started 3 months ago. He said that might be the problem, or there might even be referred pain from the neck. He basically said that we need to try a few things to help diagnose the problem, so he injected some cortisone into the AC joint. A few hours later, when the numbing agent wore off, I was treated to some of the worst pain of my life.

I slept on a chair last night because I knew that if I slept on a bed, I’d roll onto that side and make it even worse. It’s still pretty bad this morning, but I’m trying to keep it propped on my chair arm and not move it much. I’m back to using my old Bamboo trackpad instead of a mouse because I use that with my other hand, but it registers things as clicks when I don’t mean to click and doesn’t register when I do want to click, so I don’t like it much.

Anyway, if this cortisone shot is anything like the one I got last summer, I’m hoping to start feeling some relief tomorrow or the next day.

Meanwhile I spent half the night wondering what I’m going to do for fun when I can’t paddle any more.

Phil Gustafson, diode re-arranger

Back around 1991-2 era, I joined an on-line community. Or rather, I started participating in a Usenet newsgroup called alt.folklore.urban, the core membership of which was turning into an on-line community, pretty much before the idea of “on-line community” had been invented. We cognoscenti called the newsgroup “AFU”, and the core of the core were known as “the hats” or “old hats” (or later “Best Mates”). One of the first “old hats” was a guy named Phil Gustafson. He was funny, he was smart, he made wicked puns, and he was part of the memes of the group (one of which was that Phil would “rearrange your diodes” if you didn’t behave). He travelled to all the real life meet-ups (which at the time were almost always on the west coast) and it was frequently his descriptions of these meet-ups that had the rest of us rolling in the aisles and wishing they’d have some out this way.
Continue reading “Phil Gustafson, diode re-arranger”

This time I think it was the cache…

As I wrote about in 2007 in articles and , back in 2004 I wrote a cache for part of the product I was working on at Kodak. In the first release to QA, I made sure that area of the code got tested thoroughly, and they found a bug, and fortunately I got it fixed before it went out to the customers. But to my chagrin, my boss and other people on the project got it in their heads that somehow any problem anywhere near that part of the product must be the fault of my cache, even though time and time again it was proven that there were no further bugs in that code for the following 3+ years.

Now flash forward to the product I’m working on now. We have a “go live to the very important customer” happening in just a few days, and we’re supposed to be in code semi-freeze. But the “Performance Project” just put their performance cache into the product, evidently without giving the local QA much chance to test it before it went to the customer’s QA. That seems just a little bit dangerous to me. But no matter, they assure me they’ve written tons of unit tests. So what could possibly go wrong?

Today the customer called up saying that they’re setting up a new client on the admin site, but every time they go to the “branding setup” for that new client, they see some other client’s branding setup. This branding consists of things like the client logo and some “terms and conditions” text and the like. Since they’ve got literally hundreds of QA people hitting this site, I naturally wondered if they weren’t seeing some interaction between multiple people messing with the setup. But after hours of poking around on their site, one of my peers and I (neither of us members of the “Performance Product”, I might add) are convinced it’s the performance cache. Evidently if you use one browser to look at one client’s branding, and then use a different browser to look at the branding of the client who hasn’t been setup yet, you see the branding from the client that you’d looked at in the first browser. Somehow the cache is reacting to the absence of information in the database for a client by pulling up information from some other client out of the cache. That’s not good.

Hopefully that will get fixed, and hopefully somebody will set up a test plan that actually tests what the cache does not just on a cache miss, but also on a database miss as well. And hopefully the important customer won’t think we’re all a bunch of idiots for not testing this properly.