Planning to build an open source tool from scratch to turn old e-waste laptops into home servers—what are the laptop-specific quirks I should automate?
retained text
Hey everyone, Whenever someone asks what to do with a 7 year old laptop gathering dust in a drawer, the standard advice is almost always: *"Wipe Windows, put Linux on it, and run your containers."* On paper, **laptops are the ultimate budget server**: low idle wattage, built in display and keyboard or debugging, and a built in UPS battery. But in practice, every time I set one up, there's always a list of laptop-specific annoyances for example: Leaving the battery pinned at 100% on the charger until it fully degrades. Preventing to sleep the second you close the lid or bump it. Backlights staying lit 24/7 or causing ACPI sleep bugs when you try to blank the console. Power outages draining the battery to 0% and corrupting databases instead of triggering a safe shutdown. Wi-Fi power saving modes randomly dropping SSH connections if you aren't on Ethernet. I’m trying to make a blueprint of an automated open-source provisioning tool (a bootable USB creator) that handles these laptop hardware quirks out of the box during an unattended Linux install, then hands you a pre-tuned, headless server ready to manage over the local network. **You still have FULL CONTROL over your server it’s just that the accessibility is made easier and the painful to set up steps are reduced.** Before I write the core installation logic, I want to make sure I’m solving real-world headaches rather than just my own: 1. If you run an old laptop as a server, what was the nastiest hardware or kernel quirk you had to hunt down and fix? 2. How do you personally handle the battery dilemma—do you rip the pack out completely, set charge thresholds via sysfs/TLP, or just risk it? 3. What would make an installer like this feel genuinely useful to you, rather than just another script wrapping an Ubuntu ISO? (e.g., automated clean shutdown daemons on low battery, auto-configuring CasaOS/Docker, headless Wi-Fi setup, dual-boot preservation)? Would love to hear your hot takes and annoying problems you face that you might want to solve before I get too deep into the architecture. *P.S. Treating this whole project as a deep dive to actually learn real Linux systems architecture under the hood rather than just copying scripts, so feel free to get as technical or nitpicky as you want :)*
document fetched 2026-11-04 00:29 · canonical https://reddit.com/r/selfhosted/comments/1xmum2q/planning_to_build_an_open_source_tool_from