It's cool to see your interest in running Linux on highly constrained systems. I might check out eXe Linux, since I spent a bit of time messing with Linux on my Cr-48 Chromebook, which has an Atom N455.
Although, if I'm getting silly enough to try making N455 usable (which was seriously underpowered even at launch), I'm probably going full-on tinkerer mode, which is why I used it as an excuse to learn about Arch Linux. I figured hey, if I only have 2GB RAM and slow 16GB storage, I should have assurance that every single component on the machine is something I opted into installing. Problem is, I can't retain knowledge of the ins and outs of my fully custom environment unless I'm daily driving it, which...how exactly could I daily drive an N455 for anything, other than it being a thin client?
Although, if I'm getting silly enough to try making N455 usable (which was seriously underpowered even at launch), I'm probably going full-on tinkerer mode, which is why I used it as an excuse to learn about Arch Linux. I figured hey, if I only have 2GB RAM and slow 16GB storage, I should have assurance that every single component on the machine is something I opted into installing. Problem is, I can't retain knowledge of the ins and outs of my fully custom environment unless I'm daily driving it, which...how exactly could I daily drive an N455 for anything, other than it being a thin client?
Here's my own blog post covering Arch Linux on the Cr-48: https://dansalva.to/resurrecting-a-prototype-chromebook-with...
Note that since my writing of that post, i915 graphics support in Wayland has been fixed, so it's now viable to run a Wayland DE if desired.