Haloscan Not Talking
Actually, according to Steve Bates, you won’t be able to communicate using Haloscan comments for about 24 hours.
On-line Opinion Magazine featuring annoyed rumblings from the leading edge of the Baby Boom firmly tied to a reality-based world.
Established: 21 November 2004
Editor
Commenting
The opinions expressed in Comments are those of the individuals making them. Truly absurd comments and opinions are subject to being cruelly mocked, but "flame wars" will take place on someone else's dime.
Your first comment, all comments with extensive links, and random comments that the software decides it doesn't like for no discernible reason will be held for moderation.
[Be aware that for unknown reasons the software rejects comments shorter than 15 characters, so if you want to leave a short comment fill the gap with periods ........]
Local Interest
Disaster Assistance
Notices
2 comments
Actually, they got it going after about half that time.
One commenter on the service blog asked a very reasonable question, though: why was the crashed HD not in a RAID?
The new project leader (well, new since JS-Kit took over) has a pretty good attitude, seems to have inherited a mess, and has been completely candid in his communications with irate users (including me) about the nature and magnitude of the problem. I just hope his candor doesn’t get him fired by the new owners, who may be a bit more, um, corporate than the previous ones. (I’m speculating; I have no evidence of that.)
Given the cost of hardware, I’m having a hard time understanding why anyone doing anything 24/7 isn’t using RAID. I remember paying $800 for a 10 MB drive back when a new pick-up costs $7K, so skimping on hardware is rather foolish.
I hate mergers and acquisitions, the users/customers always get shafted.