undefined | Better HN

0 pointsdzavalishin6y ago0 comments

Religions are very different around the world. Though my gods do not forbid anybody to 'very carefully verify the stored persistent data, and re-create the state from it' even if persistent data is stored in... persistent memory.

Well, just kidding, I'm agnostic, there's no such thing as my gods. ;)

Key point is code that 'very carefully verifies'. Forced RAM nullification on reboot does not help per se.

And there's no need to reboot in any case. If you feel you're busted, in persistent env you still can clear all state and recreate it from some other state.

It's just very traditional to think of files, not RAM as storage.

Memory mapped files, btw, are quarter a step to Phantom.

0 comments

1 comments · 1 top-level

gumby6y ago

Back in the days of core memory I remember restarting a machine after the power had gone out. No need to reboot (unless power had gone out while the monitory ("kernel") was running) -- only the running process, with its semiconductor registers, would die. Everything else was persistent.

The original Multics design did not make a distinction between memory pages on disk and in RAM. Files were just a way to describe a collection of memory pages, wherever they might be.

j / k navigate · click thread line to collapse