I had an HP Mini. It had a weird 1024x600 display panel, and a lot of applications expect you to have at least 1024x768. Sometimes apps would work fine until they opened a modal that was just a bit too tall, and you had to pray that Enter or Escape did something reasonable.
A few years ago I installed Debian, qBittorrent and Samba. I figured it could handle something IO-bound. I ran it for a couple of years and then recycled it when my Internet got faster than the 100 Mbps ethernet card.
A tip if you have one of those laying around and it always ran a 32-bit OS is to check if the CPU is really 32-bit only. Only the very first Atom generation was 32-bit, but the next generations had poor 64-bit driver support on Windows, so OEMs shipped it as a 32-bit machine. Not the case for OP’s netbook, theirs is really 32-bit only.
My main machine is a 13 year old Lenovo y510p running Debian and KDE. You'd be hard-pressed to tell that it's anywhere near that age.
The only aspect that has been annoying with both is graphics. Both machines are nvidia and are long past their support periods. The y510p has SLI (one graphics card is in the CD drive slot) which never worked on Linux. When removing the second card, the on-processor Intel graphics can be used, which have better support than nvidia, so I stick with that. I don't do anything graphics intensive anyway.
The biggest upgrade with old computers, without any doubt, is an SSD. I still remember getting my first one back in about 2011, a used 60GiB OCZ Vertex, and it was truly magic seeing the computer boot to the desktop in a few seconds even on a core 2 duo.
My main desktop I use for full time software development and video editing is from 2014. I've run Windows on it forever. I put Arch on it ~8 months ago.
A full desktop environment I put together based on niri boots at 1.1 GB of memory. Every app I want is installed (tons of CLI tools, various GUI tools, Docker, video editors, browser, etc.) all together comes in at 10 GB of disk total for everything based on what `df -h` says for my root partition.
My machine does have 16 GB of memory so I'm not pressed for memory, but it's nice to know the machine runs on a system designed to not be bloated.
After switching from Windows 10 Pro, it felt like I got a hardware upgrade. Things open faster and generally speaking everything just feels snappier.
As an aside, it was super fun spending a few days setting everything up in a repeatable way which I've now replicated on a number of systems with https://github.com/nickjj/dotfriedrice.
Recently retired my pc with fx6300 because it take too much desktop space; and just setup a mini pc with j6412, also installed arch Linux, i3wm for desktop stuffs
Also find a old usb Bluetooth receiver make it play some music
It works great and use this new setup to get a Agent free experience
Always loved the netbook form factor, and they were cheap!
Funny thing is that probably I also have some 2GB DDR2 stick somewhere. Last thing I need to check for is the battery, I presume it is completely down after all those years.
Anyway, this article will be very handy for this side project. Thank you!
The early ~2008 Linux-supplied dirt cheap Acer Aspire One A110L netbooks came with small (8GB?) and horrifically slow SSDs.
Back in the days of such things, we'd upgrade the RAM and use Windows XP with the write filter to make them great little machines. There was an SD card slot in the side that would happily store files.
The SSDs were very limited in read-write cycles from what I remember. More noticeable they brutally slow at writing. By shoving all the writes into RAM instead of direct the SSD, everything ran more smoothly.
If you wanted to keep any changes (usually due to OS or software updates) then you ran a batch file that wrote out the changes to the SSD before shutdown. Otherwise you shut the machine down and all your changes were immediately forgotten.
RAM Upgrade: https://www.youtube.com/watch?v=n3WVb1dL--o Enhanced Write Filter: https://www.prime-expert.com/articles/a04/speeding-up-ssd-ba...
It was more than fast enough for the time, the form factor was perfect for my teenage hands (not that they're much bigger now) and it was cheap and small enough to drag everywhere with me. (I copied and pasted some of that from a previous comment of mine about it.)
There was also a EeePC specific https://en.wikipedia.org/wiki/EasyPeasy which was even better.
Since then I have installed various things for amusement, including a cut down Chromebook OS and the OLPC Linux. The limit was always the tiny root partition (4GB SSD). I had some limited success joining with the second SSD (16GB) using btrfs.
I think the albeit tiny SSD was this machine's saving grace compared to HDD models, in terms of speed.
As others have mentioned, the RAM is really low for a desktop but perfectly fine for running a FTP/File/PiHole etc and are usually more powerful than a RaspberryPi.
They also have multiple USB A ports if you want to add storage, ethernet etc.
The challenges came from tracking down working Wi-Fi drivers for the proprietary hardware and updating the BIOS, since the stock version has a bug where it emits lid close events that Windows XP ignores but Linux dutifully handles.
Today realistically I don't think it really makes that much sense to bother with those devices even for small home servers. You can e.g. get used thin clients for cheap which run circles around those old CPUs and support way more RAM while likely being as power efficient if not more. At the bare minimum I would avoid using any 32 bit x86 CPU for running anything modern, even Debian dropped official support for that architecture now.
Apparently, I do still have a few photos in backups of someone's own enchanted marvel of a portal to universes powered by a Celeron D, USB pen-drive of 16 GiB, a single RAM of 1 GiB, we all managed to acquire and built, for such a short time we had!
Preview of the device: https://imgur.com/gallery/h1tWKp3
Since the CPU had no physical address extension (PAE) to electrify a more common OS, and something customary was required for the limited resources, where we chose ArchLinux 32-bit (now ArchLinux32, indeed) and arranged a custom AwesomeWM environment visually suggesting a console design just for it!
And dear... we adventured a few nights back then backed by this machine and some self-compiled emulation software, ZSnes and Gens, for the titles she had collected from a few local stores and magazines!
It was quite long ago... more than a decade and half... but it like all happened just yesterday, and how freaking awesome it was!
You likely had a similar event/memory! Please do remember these...
Related: https://www.archlinux32.org/architecture/ (The below table lists the compatibility of CPUs (identified by their available flags) with architectures...)
I would look at swapping out the HDD for something solid state - lighter, less power, higher performance for random R/W.
Then it's just a case of lightening the load of the CPU as much as possible, strip out everything that is not needed.
I've run modern Firefox on much lighter devices. One of my netbooks is the same spec as this, and I do browsing + coding on it easily.
It works decently, is sufficient for ssh-ing into other hosts. Though web browsing is a pain. I used to mostly use Dillo and elinks, MPV+yt-dlp for videos.
Unfortunately I left it sit for a bit too long and the battery is dead now. I'm thinking of fixing it and upgrading the power port to USB-C. Sometimes I also think about building a compute module-based motherboard for it.
There were interesting bits in the setup (blacklisting defective RAM addresses for instance), maybe I should make a short writeup :)
I still have it, it still holds a charge. Amazing little machine, portability and usage time were really top notch (not so the performance, but I was patient, and even used it for Sketchup and Illustrator)
https://github.com/parksb/parksb.github.io-comments/issues/2...
The author doesn't explain why but I'm guessing this is because `/tmp` is filling up. Setting a quota on this mount point would help limit the impact that badly behaving programs might have on RAM usage.
In addition to the usual suspects (aging hardware, planned obsolescence, bad memories), I wonder how much CPU is burned by software trying to talk to long dead backends and the retry loops and errors that occur as a result.
They came out in 2008, were sold until 2010, had literally less performance than a 2000 Pentium III CPU, were lauded from pundits left and right, and probably the school/hand-me-down laptops of that age (like today's e-waste class Chromebooks).
Especially when Acer and whatever had proper laptops with proper Intel SU-class CPUs and 3-4 GB RAM for the same price.
I disliked these "netbooks" back then and still do, and all that followed its footsteps, including the "laptop"-lookalikes with 32 GB e-MMC storage some mobile carriers would give out with their plans.
It's a disrespectful destitute class of computing.
I know that the Raspberry Pis came out later, but a Raspberry Pi 2 is a hundred times better engineered and well-rounded product, that will also run a desktop better than these netbooks (or at all).
On a related note, I also have colleagues at work who will run only sub-200 dollar smartphones and enjoy living the proper Nigeria/Bangladesh experience from 1-2 years ago. I also know that they don't use heating at home, and do everything in the name of efficiency.
It ran Octoprint for me :)
Is it just me or did it end on a cliffhanger? That's the last line!
#!/bin/sh
modprobe zram
if [ -e /dev/zram0 ]
then
echo "zram0 on"
exit 1
fi
zramctl --find --size 512M
mkswap /dev/zram0
swapon -p 99 /dev/zram0
Run the script as root.While most things ran absolutely fine, Firefox ran like crap, which really makes you realise how awful the modern web is.
When I got the netbook I had dreams of hacking in Emacs wherever I went. The tiny keyboard makes that quite uncomfortable, though. So it was only really used as a music player and web browser while traveling a few times, basically what you'd use a phone for today.