Archive for 'Computers'

X-Com Lessons Learned

Friday, October 19th, 2012

Having successfully rage-quit my first ironman run through XCOM: Enemy Unknown (dear God, the casualties and missteps!) and completed a full run-through, I’m still looking forward to another run through this highly-addictive exercise in sado-masochism. A couple of things I’ve picked up, mostly the hard way:

Read the rest of this entry »

X-COM Squad Strategy

Monday, October 8th, 2012

Looking forward to the unlocking my preload of XCOM: Enemy Unknown this evening, my thoughts keep wandering to what exactly I intend for my approach to be early on. With a limited number of troopers available for each ground mission, one temptation will be to expand the number I can deploy by upgrading my base to allow for five- or six-man squads.  Depending on the other options available at the moment, compared to my budget, that will be a strong temptation indeed.

Developing some basic body armor and support capabilities in the form of decent medical kits will be another early priority, presuming that I find my troopers’ weapons to be sufficiently deadly. In the original X-Com the conventional armaments were laughable, so I’ll be sorely temped to research and manufacture laser weapons. I’m leaning toward the defensive, though, as a shoddy weapon in the hands of a veteran is preferable to an excellent weapon held by a panic-prone rookie. I hope.

As for those rookies, as soon as I’ve got a squad worth of veterans, there will be a rotation of fresh meat on every mission I can swing it for.  I know at some point a valuable, experienced lynchpin of my tactics is going to get himself poisoned or burned or blasted all to hell, and end up spending quality time in the hospital or pushing up daisies.  Just having one good sniper or heavy or support guy isn’t a good option; it’s a recipe for long-term disaster. So somebody’s going to have to ride the bench every mission.  Sometimes getting laid up with an injury will make this decision easy, but other times it’ll be painful. As rookies get promoted and find their role, their place in the rotation will shift.

Once I’ve got a stable of modestly-experienced troopers available, I figure I’ll go half-and-half with hard-bitten veterans and the lower ranks. Nobody is really expendable, but I’d much rather take the hard-nosed position of sending a corporal in first instead of  a major or colonel.

When I have enough experienced troopers to fill out two full squads, it is time to expand squad size. The 1994 X-Com saw enough Normandy Beach effect, with rookies dying in droves as they exited their Skyranger. No need to repeat that more than absolutely necessary.

Squad composition will go balanced for a while, with a Sniper, Support, Assault, and Heavy Weapons specialist in the mix whenever I have them available, swapping out the Assault and Heavy Weapons troopers for rookies more often than not. I expect a lot of Assault specialist casualties early on. For early play I hope that a barely-competent Heavy Weapons guy will get his job done more often than not; he’s for clearing out walls, right? I hope to get a Support specialist early on and keep him on a road of continuous improvement. This role strikes me as particularly conducive to my cautious-advance style of play from the old days.

In a couple days, with any luck, it’ll turn out this is a good approach. Unfortunately luck seems to swing both ways in the X-Com world.

Server Wrangling

Saturday, September 8th, 2012

Failed Hard Drive

I’m not a big hardware guy. I use computers as a tool, sometimes for work, sometimes for hobbies, but I generally only get under the hood when something is wrong, and only then when whatever went wrong is seriously getting in my way.  Take the recent gallery outage for example.

I run an old Linux box with an unimpressive CPU, unremarkable storage and memory, in a seriously-oversized 4U rackmount chassis that I’ve had parked at my employer’s data center for the past half-dozen years.  Being not-particularly-inclined to fiddle with my operating system just for the heck of it, I let things get pretty seriously outdated, to the point where upgrading software like my WordPress install here was troublesome and required odd work-arounds. So I poked at it a bit, patching here and there, and at some point I managed to deny myself SSH terminal access. I could still get in via SCP (which is odd because SCP uses SSH to connect, but hey), so for the most part this didn’t matter to me.

I let it sit for a few months, taking a poke at it now and again when the mood struck me, but eventually I managed to totally screw it up to the point where I couldn’t connect via my https control panel (Webmin), SSH, nor SCP. I don’t let anybody else use any of the above, so nobody else was affected. People who wanted to use my gallery could, the handful of web robots and actual people that visit this blog could still do so as normal, and my Riddle of Steel wiki was functioning, so no harm, no foul.

Then I bit the bullet and opted for the nuclear option. In the back of my mind I was already concerned about disk usage and my decrepit old IDE drive, so I pulled the old 4u from its rack to pop a fresh disk in, install a modern operating system, and migrate the old data over. No problem, right? I’d have it done in an evening.  Of course not.

My first challenge was my server’s neighbors.  It turned out that the five servers above mine in the datacenter cabinet were not properly mounted. They weren’t even improperly mounted. They were just resting atop my box. Four little bolts in the face of my server were the only thing between them and plummeting to the floor. Oh, and one slightly-short CAT-5 cable that just about gave up the ghost as everything sagged.  A metal rack shelf and a couple of 4x4s later (I kid you not, the’re still there) my lazy neighbor’s equipment was reasonably secure again and I had my server out and ready to service.

This is when I realize for the first time in half a dozen years that my server has no CD drive. It had been a network install and never needed one before. But I didn’t have anything set up ready to serve a network install, so I’d have to cannibalize one from one of my retired desktop machines at home. Glorious. While I was was at it, I figured I would use the drive from the same machine. This will come back to haunt me later.

I finally get the CD drive and new HDD installed and promptly discover that the tray won’t open to take my freshly-burned install CD. Great.  Cue another pause in getting the gallery back up.  I cannibalize another drive from another retired machine, and lo this one opens and is bootable.  I get my install disk up and running, and 23% of the way through the process it declares I’ve got a corrupted file. Outstanding. I burn another install disk and get 11% in before getting the same error.  Two disks later it finally completes, I’ve got a simply LAMP server to migrate my data to. Or do I?

I power down, put in the old server’s HDD, and turn it back on. ATAPI errors out the butt. I fiddle with the jumper configurations, but they persist. Finally I discover that one of my ATA cables wasn’t set up correctly, and perhaps never had been. I get the sorted out and find out that my cannibalized HDD won’t boot, for reasons unknown.  Off to the store, get a new HDD, install the operating system from scratch, get the old HDD back into the picture, figure out how to mount it, and get the files copies over.

Then comes wrestling with the network configuration.  Linux likes to play coy about things like network interfaces and whether it’s got link on which port.  I get it up and running by DHCP on my office LAN to make sure I’ve got Apache and MySQL up configured properly, import the gallery database from backup, square away a couple of php.ini and virtualhost issues, and it’s time to re-rack the sucker.

There is currently a metal shelf and two 4×4’s where my box used to be, but there’s a convenient 4U opening elsewhere in the cabinet, so no problem there. I slide it in, secure it properly out of deference to the folks whose gear is below mine, and go to plug back into the switch.  The CAT5 cable I had left when I pulled the box is now gone. I grab a spare and plug it into the port I used to be on and see my link indicator light up. I fire up a console and manually enter my static IP information. Which is, naturally, kept in a different place than my DNS resolver information. Thanks, Linux.

I discover that I can’t ping out. Not by name, not by IP. I check for link. I check to make sure I’m connected to the port I used to be on. No good.  I double-check the syntax on /etc/network/interfaces and restart the network services. No good.  I check the records of which port I’m supposed to be on. The record says I’m supposed to be four ports off what what I had noted when I had removed my gear. I try that port. I get link. I reset my network. I still cannot ping. I try each of the other open ports on the switch in turn, getting link each time and finding myself unable to ping each time.  So I check for other loose cables. I find three in all, one of which I think was my old cable. I try it. No dice.  I try the others, and lo! what used to be port 10 is now port 2 and I’m back up and running.

I configured my DNS and hostname, buttoned down the cabinet, and popped the gallery link back up atop my blog.

The moral of the story here is that getting it to work is half the fun. If you can’t enjoy a process like the one described above, hire a professional.