Hacker News new | ask | show | jobs
by zubairlk 2818 days ago
Running an OS + application entirely from memory is an interesting approach indeed.

I guess the fundamental big problem you are facing is SD card corruption. In our experience, we've found the SanDisk Extreme Pro cards to be most reliable. (coupled with a good power supply).

Read-only rootfs is almost a must have for any production environment.

resinOS does not satisfy all your requirements (nfs boot, state in memory etc).. But we do have stuff in place to reduce the problems you are facing.

- There is an initramfs in the kernel. When the kernel loads in memory, it runs fsck on the root/data partitions before mounting the rootfs. - The rootfs is read-only with only a few configuration files in the state partition. - Applications run inside a container so you can basically run rasbian on top of resinOS.

I wrote more about resinOS in another comment highlighting remote application container updates/vpn access etc.

https://news.ycombinator.com/item?id=18093336

Disclaimer: I work at resin in the OS team. I've noted down your feedback about running purely in memory.

1 comments

> Applications run inside a container so you can basically run rasbian on top of resinOS.

How well does that work? Do you get full access to the underlying hardware? Can you still access the GPIOs, HDMI-CEC etc? Are there any other downsides to doing this?

Sorry for the delay. Yes they get full access. CEC might be an interesting one. "If you choose, your containers can be configured to run as privileged, access hardware directly, and even inject modules into the kernel." from https://docs.resin.io/learn/welcome/primer/