3 ms·
There have been Java OSes too, with the idea that verifiable bytecode does away with the need for "expensive" memory protection etc. Running everything in one m
by barrkel 15y ago
There have been Java OSes too, with the idea that verifiable bytecode does away with the need for "expensive" memory protection etc. Running everything in one memory space is error-prone, but it's the default way of the monolithic kernel. Having services delegated out to processes with separate memory spaces is architecturally more stable; a single bug in an obscure driver in a less actively maintained corner of the kernel shouldn't lead to a system-wide vulnerability. The approach I mention preserves the ability to keep things separate (with appropriate controls and verification at the boundary); the Singularity / Java OS approach seems rather different.
Snoracle says JavaOS itself is obsolete, FWIW.
- btilly 15y agoYet another variant on the idea was the AS 400. It had no memory protection and didn't need it, since there was no way to address anything that you weren't supposed to. Given the impressive stability and security record of the AS 400, they had a point.
- barrkel 15y agoYes, when you have typed pointers at the hardware level, it can be even better than page protection.
- swdunlop 15y agoOnly because Snoracle hasn't ported Oracle to it, yet.