Bluesock died on Tuesday; resurrected on Thursday

, Will Kahn-Greene | share this (mastodon)
Note: This is an old post in a blog with a lot of posts over a long span of time. The world has changed, technologies have changed, and I've changed. It's likely this is out of date, the code doesn't work, the ideas haven't aged well, or the ideas were terrible to begin with. Let me know if you think this is something that needs updating.

Yea, and lo Bluesock did gasp its last breath early Tuesday morn and exhaled ne'er to be revived again. And lo, all my friends called me up to tell me the news. I submitted two, nay three, tickets in the tech-support ticket system. Minutes turned into hours.

Yea verily yea, Rob of the clan Atha did calleth up the ServerBeach people and gave them angry Texas hell and they agreed to give us some new hardware. Forsooth it turned out to be a defective disk or motherboard or some such hardware issue (or so we think--hard to tell when I'm in Boston and the server liveth in Texas).

Then on the second day, Bluesock rose again with a new mortal coil and the old drive was mounted as a partition of the new. With great speed, we re-configured and re-installed all the stuff we had configured and installed on the original Bluesock.

Then when we were done, it was as if the tragedy had never occurred. The users were happy once more [1].

Want to comment? Send an email to willkg at bluesock dot org. Include the url for the blog entry in your comment so I have some context as to what you're talking about.