Tuesday, December 29, 2015

Old Laptop: Must Revive

In a quest to re-revive an old IBM Thinkpad, I sifted through many articles and forums surrounding the subject of operating systems. The piece you're reading now isn't intended to be a technical instructional as much as a high level overview of an approach that resulted in a fairly elegant, user friendly system on an outdated laptop computer powered by Linux.

If, like myself, you're only mildly acquainted with using a command line interpreter - or a black screen with a blinking cursor, your first order of business should be to ensure you have a primary web connected computer or tablet for referencing purposes. Many plug-and-play distributions do exist, but can be burdensome to older, memory deprived systems...

Here's a (very) rough breakdown of my Thinkpad's limitations:

  • Intel Celeron M Processor (1.16 GHz) 
  • 40 GB HDD
  • 256 MB RAM

...which is why I chose to 'build' the o/s from a base installation up.

Installing a base (sans graphics / desktop) Linux distribution is simple enough - configuring everything appropriately using a shell with just a prompt and blinking cursor awaiting cryptic commands can be quite daunting. After reading several online reviews and poking around forums, I drew the conclusion that the 'Slackware' distribution might best suit my needs. Using a freely available program called "Rufus" on my Windows 7 PC, I installed the downloaded .iso on a USB flash drive.

I was wrong about Slackware. With all due respect to its developers (who are most certainly echelons above my own abilities in the realm of compu-skillz), I was somewhat put-off by a cute sounding embedded system FYI that struck me as somewhat of a shout-out to insiders. In a way that's kind of cool, but I'm not an insider, and so I ultimately settled on Arch Linux.

Likely you've surmised that my Thinkpad is equipped with USB ports. It also has a built-in WiFi adapter and network interface. When you boot the Arch Linux .iso from external media, it 'pops' the kernel into RAM (I think) and requires an internet connection to install on your HDD.

Your first order of business should be to establish and confirm web connectivity. Since I used a WiFi connection, this was simple enough with the USB booted system, but reactivating the adapter presented some challenges AFTER the installation.

Next you'll want to partition your hard disk drive(s). I just followed a schema I found on line that basically devotes 100 MB to the /boot partition, 1 GB for a 'swap' partition, 20 GB for the root system, and the remainder to the /home division.
I would recommend you take a fair bit of time to become accustomed to entering rudimentary commands.


  

On Learning Linux

After so much mucking about, and being faintly aware that the entire process is wrapped in a brilliant, yet haphazard fashion betwixt so many layers of abstraction that it must surely be transparent at some level, I finally manage to invoke a little icon on my Windows 7 operating system. The icon represents countless nuanced tangents and countless hours spent editing configuration files to achieve a simple result: enable the Windows spirited PC to read & write files contained on the HDD of a PC sitting right next to it, but engendered with a Linux o/s.

With the help of so many geniuses before me, I made a very particular something happen. Something so particular in fact, that I'd wager more than 99% of the whole worlds population might dismiss it as so much black magic. Were it not for the 0.001%  of dedicated computer science devotees, I'd probably be on tour with some stupid rock band.

The embarkation itself is half the battle. I know I'm not reinventing the wheel, but I'm marvelling at the spoke-work. Is it a complete waste of my time to become adept at identifying interoperability issues now that the information age is behind us now? Short answer: I don't care. For a Scrabble head like myself, the challenge is the whatever.