Either pxe netboot or usb or installable. Immuttable or not. Ramfs. With a host selector or fully auto login ?
Ultra light 16 to 128mb storage 64-128mb ram. Or “full sized”
And lastly, something like that, but that would run on a proxmox host.
Either pxe netboot or usb or installable. Immuttable or not. Ramfs. With a host selector or fully auto login ?
Ultra light 16 to 128mb storage 64-128mb ram. Or “full sized”
And lastly, something like that, but that would run on a proxmox host.
“64-128mb ram” is hardly “low memory”!
For video it is. Unless you want your desktop to be in 128p
It’s probably plenty for vnc or spice though. I had a 486 with 8mb of video RAM that could do 1024x748 display resolutions…
Know you can’t. That would require 12mb of ram for a single frame. In reality you need lots and lots of frames with hardware decoding plus network overhead.
Not to mention that CPU would be way to slow to run anything but the bare Linux kernel (the kernel requires 8mb)
1024x768x24bit is 2.4 MB
I mean… I did. 🤷♂️
https://www.google.com/search?q=(1024+*+768+*+32)+bits+in+mb
Using 32 bits to be conservative that’s a bit over 3MB.
Granted I couldn’t play most games at that resolution on a 486 but it worked for a desktop resolution.
You kids with your GPUs with gigabytes of memory and your blue jeans…
I am pretty sure my p200mmx with 64mb ram could run a vnc client while listening to a blink182 mp3 in XMMS using the enlightenment window manager
Megabytes, a thousand of which make a gigabyte. Chrome in my machine right now is taking over one gigabyte of memory, that alone is using more than 8 times what OP wants the whole system to. It’s definitely an ask for low memory, almost embedded levels of ram.
I wouldn’t be against something that needs 1gb or 4gb. Of course it’s different hardware class, but if it actually does a better job, it would be fine.
Although I suspect for a thin client, 512mb would be more than enough and adding more wouldn’t improve much of anything.
Chrome is actually doing a lot of work to display modern webpages though. A thin client only needs to receive a video stream and send inputs to a server. That can be done with an extremely low memory footprint. The Steam Link only had 512MB of RAM and it actually ran a steam client (which contains embedded chromium) instead of acting as a pure thin client.