I have a habit of poking around in other people’s closets. The find is almost always the same: a mid-2000s beige tower, a working power button, and a hard drive that has not spun up in three years. The owner always asks the same question. Should I recycle this thing or is there still a job in it?
There is. The PC is not too slow. It is just underused. The right framing is not whether the box can keep up with a modern browser tab. The right framing is whether it can keep up with one job, left running, for months at a time. Most closeted towers clear that bar easily. Linux is the part that lets you pick the job.
This is a short tour of the projects I have actually left running on retired hardware, the ones that survived a power outage or two, and the parts of each that surprise people the most.
What “good enough” actually means for a home server
For any project in this list, the bar is lower than you think. The PC does not need a recent CPU. It does not need a graphics card. It needs to be boring. Boring means a power supply that does not whine, a hard drive that does not click, and a network port that does not drop packets during a Zoom call.
A working CPU from the last fifteen years, even a dual-core Celeron, is fine. RAM matters more than people expect. 4 GB is the floor for almost every project here. 8 GB gives you breathing room. Beyond that, you are buying RAM for the browser tab you opened on another machine.
The hard drive is the part I check first. If smartctl (a command-line tool that reads drive health telemetry) shows reallocated sectors or pending failures, I do not install anything. I order a replacement SSD. A 240 GB SATA drive is twelve dollars and removes the most common silent failure mode in old towers. I have a small box of those drives for exactly this reason.
What I look for before committing a tower to a permanent job:
- A CPU from the last decade and a half, dual-core minimum
- 4 to 8 GB of non-flaky RAM, matched pairs where possible
- A healthy SSD or a hard drive with no SMART warnings
- A wired Ethernet port and a real network drop nearby
- A case with airflow, not a sealed shoebox
The wired Ethernet point matters more than the wireless one. A server that lives on Wi-Fi will work fine until the access point reboots, and then it will not come back without intervention. Wired is boring. Boring is what you want.
A network boot server pays back the first weekend
The first project I install on a spare tower is a network boot server. PXE (Preboot Execution Environment) means a computer can pull its operating system installer straight off the network instead of a USB stick. You boot a laptop, it asks the network what to load, the closet tower answers with an Ubuntu installer.
The reason I start here is selfish. Every other project in this list will eventually require reinstalling something. PXE means I never have to hunt for a USB stick at 11 PM. The whole library of installer images lives in one folder on the server, ready to ship.
What lives in that folder, after a couple of years of accumulation:
- The current LTS (long-term support) installer for each distro I actually use
- A small rescue environment for the day a main drive refuses to mount
- A memory test image for diagnosing unstable laptops
- A network filesystem mount for moving large installers around without burning optical media
The actual workload is small. The tower mostly serves files over the LAN. A spinning hard drive from 2014 can handle three laptops installing at once without sweating. What catches people is the DHCP (Dynamic Host Configuration Protocol, the network service that hands out IP addresses) coordination. If your home router already hands out addresses, your server has two choices. It can run its own DHCP server and have the router step aside. Or it can forward PXE requests to the server’s IP address. Mixing the two is the most common reason a home network stops handing out leases at 2 AM. Pick one path and stick with it.
The file and print server that earns its shelf
A file server is the second project I install, because every other project in the closet benefits from having shared storage. Samba (the open-source implementation of the Windows file-sharing protocol) is what I use. It is boring. It is twenty-five years old. It works on every device in the house, including the smart TV that does not advertise that it supports SMB (Server Message Block, the protocol Samba speaks).
What lives on the shared drive, after the dust settles:
- A flat folder of ISOs (disk image files used to install operating systems) for reinstalling anything
- A media library that every TV in the house can reach
- A “scans” folder that the household scanner writes to directly, no third-party cloud required
- Time Machine backups from the family’s laptops, which is a quiet use case until the day a laptop dies
The trade-off is the printer. A network print server is the single most likely thing to require a Sunday afternoon of fiddling. Drivers are driver-specific in a way that Linux users learn to expect and Windows users do not. I keep a USB printer plugged into the closet tower instead, and the family laptops print to it over the network. That keeps the failure mode to one place.
The application server nobody asked for, that everybody uses
This is the project I underestimated. A small home application server runs the things I used to pay monthly fees for, and the household has quietly adopted all of them.
The list, in roughly the order they earned their keep:
- A read-it-later service that captures articles from my phone and renders them on the Kindle
- A photo backup target that the phones upload to over Wi-Fi, so I do not have to think about cloud quotas
- A recipe app that the kitchen tablet pulls from, no ads, no tracking pixel
- A small kanban board for shared household tasks, because the free tiers got worse
The hardware demand is light. Photos and documents are small. A dual-core Celeron with 8 GB of RAM handles this stack without breaking a sweat. The part that surprised me was not the performance. It was the durability. I have rebooted that closet tower twice in two years, both times for kernel updates, and the household did not notice either time.
What to skip on a first attempt
A few project types look like a great fit on paper and turn out to be a poor one in practice. I have tried most of these. The shared trait is that they promise a lot and they fail in ways that are hard to debug from the couch.
The mistakes I have made or watched other people make:
- Game servers. A Minecraft server for the kids sounds great. A Minecraft server that the kids want to play on at 9 PM is a different machine than the closet tower. Pin it to a real budget box, or accept the lag.
- Bitcoin nodes. This is technically a fine job for old hardware. It is also a job that requires you to keep up with chain growth, which means a real SSD, not the spinning drive you were hoping to use. The math stops working.
- Home video surveillance. The motion-detection pipeline chews CPU on the wrong machine. Cloud subscriptions for the cameras will ruin the savings faster than the home server saves you anything.
- Machine learning inference. The CPU can do it. Slowly. The job does not match the hardware, even though the marketing materials say otherwise.
Trade-offs
None of this is free, in the part-of-the-weekend sense. A closet tower needs a wired network drop, and that is the part of the install that takes an afternoon. The first project, PXE, takes about three hours the first time and ninety minutes the second time, and it pays back forever. The application server stack takes longer to install than it does to use, which is the trade you accept in exchange for not paying a monthly fee.
The biggest hidden cost is mental load. A home server is one more thing on the network, and one more thing that can break. If you are the only person in the house who can read a log file when something stops working, that is a real constraint. I keep the install boring on purpose, because the boring install is the one I can debug at 11 PM on a Tuesday without swearing.
The second cost is backups. The closet tower is one hard drive in one room. If the house has a fire, so does your photo library. I keep an external drive in a different room that rsyncs (a command-line tool that mirrors files between machines) every Sunday. That is not a backup. That is a starting point. If your data matters, get a real backup.
What I would tell past me
If I could send a note back to the version of me who first stuck a Linux box in the closet, three lines:
- Match the job to the hardware, not the marketing. A closet tower is a PXE server, a file server, and a small application stack. It is not a game server and it is not a learning machine.
- Wired Ethernet is non-negotiable. Wi-Fi is fine for the laptop. The closet tower needs a cable.
- Buy one good SSD for the boot drive and one good external drive for backups. That is the whole upgrade path. Skip the rest.
The PC in your closet is closer to useful than you think. The job you give it this weekend is more satisfying than the one you never let it do.