BY JETPLAIN /
Retro Terminal Home Lab (for Cheap)
Give a spare computer one useful job and build a learning setup without a shopping spree.
I'll admit it: I like a green terminal. Give me an old computer with a useful job and I'm interested.
But before you start shopping, let's work out what you want the thing to do. My mechanic's instinct is to look at what's already on the bench before adding to the tool bill.
For a first home lab, I'd start with one computer, one job, and a notebook. This is a plan for a local learning setup, with room to choose hardware you already own. We'll leave replacing its operating system for another day.
Start with the machine you have
First, take stock. Look for a spare laptop or desktop that still works. Check that it has a usable power supply, a working display or monitor connection, and storage you're prepared to use for the project.
Before changing anything, copy off files you want to keep and check those copies. If the machine belongs to someone else, get their permission first. A computer with a swollen battery or damaged power cable needs attention before it becomes a project.
Already own a Raspberry Pi? It can be an option too. Include its power supply, storage, and any display or keyboard you need when deciding what the setup costs. The official Raspberry Pi guide covers model-specific setup and writing the operating system with Imager.
I'm not putting a magic bargain price on this. A suitable spare machine may save you a hardware purchase, but power, replacement parts, and extra storage still count. Price the whole setup before buying a supposed bargain.
Give it one job
Here's the first job I'd give it: a project notebook you can navigate from a terminal. Modest? Yes. It gives you a small system you can understand and check.
- Create a folder called Jetplain Lab using your system's file manager.
- Inside it, create Notes, Projects, and Scratch folders.
- Add a plain-text README file explaining what this machine is for.
- Open the terminal included with your operating system.
- Use that system's help or official documentation to find out how to show your current folder, list its contents, and move between folders.
The commands vary between shells—the program that interprets what you type into the terminal. You don't need to install Linux just to learn those three actions.
Keep the practice inside Scratch, using disposable files you created for the exercise. The goal is to learn what each action does and recognize the result.
Make the terminal comfortable
Choose a readable font size. If the terminal supports color themes, try pale green text on a dark background. Keep enough contrast to read it in daylight.
I want the retro look, but I also want to read the screen. Skip flickering effects and anything that gets in the way of seeing what you're doing.
Add another operating system only when you have a reason
If learning Linux is your next goal, consider a virtual machine before replacing the system on your everyday computer. A virtual machine runs a separate guest system using some of the host computer's memory, storage, and processing power. Check the current requirements for both the virtualization tool and the guest system first.
Keep the first experiment to ordinary local exercises. Leave port forwarding, shared folders, and remote access off until you understand what each enables. A virtual machine is useful for practice, but it is not a reason to run untrusted programs carelessly.
VirtualBox supports snapshots that let you return a guest to an earlier recorded state. Keep independent backups of important files; a snapshot stored on the same drive does not protect you from that drive failing.
If you choose installation media instead, follow the current official instructions for your computer and operating system. Writing a bootable USB erases the selected USB device, and an installation option may erase the computer's drive. Confirm the target before proceeding.
Finish with a small proof
Before we call this done, let's check the result. Use the terminal to find your Notes folder and confirm your README is still there. Open it in your editor and add three lines:
- What I tried.
- What worked.
- What I want to understand next.
That's enough for a first session. You've got somewhere to practice, something you can verify, and a note for the next time you sit down. We can give it a bigger job once this one makes sense.
Official setup references
- Raspberry Pi: Getting started
- Oracle VirtualBox: Working with virtual machines and snapshots
- Ubuntu: Create a bootable USB stick
References checked October 28, 2026. Follow the documentation for your installed version.
