Re-centralised

So I pulled the old Fullslack server, aka “superfly”, out of mothballs this afternoon.

I can’t believe I only ran 128mb of ram in her for over a year! She was always up and running, and I was low on time – hay, if it works, right? Either way, I took the opportunity to give her another 128 from the boneyard. Dusted her off and started the shakedown.

(Above: Ready to launch for Sea Trials)

NB: Say what you will about commodity hardware & servers – I’ve got “iron” in the next room. Why use more resources then you need? Besides, the electricity bill gets a bit much if I run it 24/7)

She sprang to life – the motherboard recognised the new ram – but alas I was the weak link. It had been so long I forgot the login information! I tried the various combination’s i used to use but none worked. I hunted around the case looking for the note I made when I changed it months ago – no luck. I rebooted my main main machine into Linux and checked the encrypted password list I keep – no entry! It came down to me having to hack my password. Fortunately, my GRUB was not password protected (inb4 security experts- if someone had physical access to her I have bigger problems – besides my biggest fear was my son turning her off) and I was able to use the method outlined here to make quick work of them.

After that jaunt she loaded fine, was able to log in proper (and changed my password). Everything seemed in order and no errors were reported on the HD. I have a stunning lack of mice so no GUI, but I’ve almost completed backing up most important files (the ones needed for the KB proof-of-concept).

(Above: Look Ma, No Swap}

To be continued in Pt. 2