Most of what I write here is Solana safety tooling. Sometimes it's good to step away from crypto for a day and just help someone get an old computer working again. This is what that looked like, and how each piece works, in case you're in the same spot.
The constraints were real ones:
- No working PC to prepare anything on. Just an Android phone (not rooted) running Termux.
- One 64 GB USB stick.
- Old laptops: a 2006 Dell that's 32-bit only, and a 2009 Compaq Presario CQ50 (Celeron 575, 2 GB of memory, Intel GMA 4500M graphics).
Step 1: pick the distro by the hardware, not by taste
The first question isn't "which Linux is best", it's "which Linux will this machine actually run".
| Machine | What decides it | What fits |
|---|---|---|
| 2006 Dell, 32-bit CPU | Ubuntu, Mint, Debian 13 and ChromeOS Flex all dropped 32-bit | antiX (has a 32-bit build) |
| 2009 Compaq, 64-bit CPU, 2 GB | Enough for Debian Xfce or antiX; Mint started but drew lines across the screen on its old Intel graphics | antiX (light, and it displayed fine) |
How to check before you download anything: the sticker, the model number and the spec sheet tell you 32 or 64-bit and how much memory. If you can already boot something live, lscpu and free -h tell you for sure.
We downloaded four ISOs to the phone (antiX 26.1 32-bit, Debian 13.7 Xfce, Ubuntu 26.04.1, Linux Mint 22.3) and checked every one against its official SHA-256 checksum before using it. A download that stalls halfway still looks like a file. One of ours did: the antiX ISO sat at 61 MB of 2.26 GB for a while. The checksum is what tells you it's complete and untouched.
Step 2: one stick, many systems (Ventoy, built on a phone)
Normally you'd "burn" one ISO to a stick, and the stick becomes that one installer. With several machines and one stick, that's a lot of rewriting.
Ventoy solves that: you set the stick up once, then just copy ISO files onto it like normal files. When a computer boots from it, Ventoy shows a menu of every ISO on the stick and boots the one you pick.
How it works on a computer with no operating system at all:
- When the computer powers on, its firmware (the BIOS) doesn't care what's on the hard drive. If you choose the USB stick in the boot menu, it reads the first sector of the stick (the boot record) and runs the small program there.
- That program loads Ventoy's boot menu, which is built on GRUB2, the same boot loader most Linux systems use. It lives in a small 32 MB partition on the stick.
- The menu lists the ISO files it finds on the stick's big data partition (exFAT, readable by phones, Windows and Linux).
- You pick one, and Ventoy boots that ISO directly, as if it had been burned to the stick on its own.
So the machine needs no OS, no network and no installed anything. Just a firmware that can boot from USB.
The catch: Ventoy's installer needs a computer. We didn't have one. So we wrote a small Python script that does exactly what Ventoy's official installer script (Ventoy2Disk.sh) does, but into a disk-image file instead of onto a real stick:
- the partition table (a big exFAT "Ventoy" partition plus the 32 MB boot partition, aligned the way Ventoy expects)
- Ventoy's boot code in the first sectors
- the exFAT formatting, using Ventoy's own formatter
Then we tested the image in an emulator (QEMU, old-style BIOS boot, the same path the old laptops use) and watched it boot straight into the Ventoy menu before touching the real stick.
Then:
- Writing the image to the stick from the phone with EtchDroid (an Android app that writes images to USB without root). At about 13 MB/s, a 32 GB image took around 44 minutes. The stick's write speed is the limit, not the phone.
- Adding systems is just a copy. In plain Termux (not inside a proot Linux, which can't see plug-in drives):
cp -v -n /storage/emulated/0/Download/*.iso /storage/<stick-id>/ && sync That's the whole trick: the slow write happens once, and every distro after that is a few minutes of copying.
Step 3: the phone's hotspot as a little private network
Here's the other half, and it works even when nothing else does.
When you turn on your phone's hotspot, the phone becomes a tiny router: every device that joins gets an address on a local network that only exists between them. It's not the internet, and nothing on it is exposed to the outside. And both machines can talk to each other directly.
We used that two ways.
1. Handing a computer files straight from the phone. For a laptop with no USB stick at all, we set the phone up to serve the Linux Mint installer with Python's built-in web server, on the hotspot only. To keep it safe and simple:
- it checks the ISO against the official checksum first and refuses to share a bad file
- it shares a folder containing only links to the files meant to be shared (the ISO and a setup script), so nothing else on the phone is visible
- it stops by itself after 60 minutes
python3 -m http.server 8080 --bind 0.0.0.0 # run inside that one-file folder On the laptop, connected to the hotspot, you open a browser to http://<phone's hotspot address>:8080 and download.
2. Working on the laptop from the phone. With antiX running live from the Ventoy stick and the Compaq joined to the phone's hotspot, one command on the laptop turned on remote login:
sudo service ssh start From then on, the phone could work on the laptop as if it were at its keyboard. Before installing anything, that let us do the careful parts:
- read the real hardware: CPU, memory, graphics chip and Wi-Fi card, which explained why Mint drew lines (the old Intel graphics)
- check the hard drive's health first: SMART passed, 0 bad sectors, only 630 power-on hours. No point installing onto a dying drive.
- look for personal files on the old Windows partition, mounted read-only so nothing could change, before anything got erased
- dry-run the installer (antiX's installer has a
--pretendmode that walks every step without writing to the disk) before the real install
One lesson from that: an installer started remotely can still stop and wait for a "Continue?" box on the laptop's own screen. If a remote install seems stuck, go look at the machine.
What to take from it
- Check the hardware first: 32 vs 64-bit and memory decide the distro.
- Always verify checksums. A half-downloaded ISO looks like a whole one.
- Ventoy turns one stick into a menu of systems. You can even build its image without a PC, as long as you copy the official steps exactly and test the image in an emulator before you write it.
- A phone hotspot is a private local network. It's enough to hand a computer an installer or to work on it remotely, with no router and no internet involved.
It was a good break. Back to Solana safety tools next week.

