Lenovo S10-3
A 2010 netbook rebuilt to do one thing — where almost every decision was a removal, and the build was automated so reinstalling beats repairing.
What it is
A Lenovo IdeaPad S10-3 netbook from 2010, rebuilt to do one thing: show a web page.
It powers on, logs itself in, starts X, and launches a browser. There is no desktop sitting behind that browser to return to.
The constraint
The hardware set the terms: an Intel Atom N455 at 1.66 GHz, 32-bit, with around a gigabyte of RAM. The 32-bit processor is what forces a 32-bit Debian build — never a preference.
Such a machine can technically run a modern desktop environment. It cannot run one and a browser, and the browser was the entire point.
What made it work
Most of the work was removal.
No desktop environment. No display manager. No window manager. No compositor. X.Org starts directly from the user’s own session file, and the browser is the only graphical application that session launches — it draws its own window because nothing else exists to do it.
xset s off
xset -dpms
xset s noblank
exec firefox-esrThen smaller subtractions: unnecessary background services switched off, screen blanking and power management disabled so it stays readable unattended, the extended-support browser release rather than the fast-moving one.
Two things were added rather than removed, both about not failing. A small swap file exists purely as a safety net, paired with a swappiness setting low enough that the system avoids reaching for it — swap should absorb a spike, not become the working surface. The wireless setup is deliberately over-prepared: it detects which of several Realtek adapter variants is fitted, loads the matching driver and firmware, accepts a fallback network, and stores the key as a hash rather than plain text.
Reinstalling beats repairing
What turns this from a configured laptop into something worth writing down: the build was automated. There is a manual path — one script on a fresh install, a second for wireless — and a remastered installer that performs the whole build unattended. That image was actually produced, not merely scripted.
On hardware this old and this replaceable, a configuration you can only reach by hand is fragile. One you can reproduce from an image is disposable in the useful sense: if it breaks, reinstalling is faster than diagnosing.
The setup script finishes by checking its own work, asserting that each thing it configured actually is.
Where it stands
Finished: the build pipeline is complete and the installer image exists.
I am not claiming it runs daily — the last change was May 2026, and nothing since shows otherwise. A completed experiment, not a running service.