Linked by J. Scott Edwards on Fri 17th Dec 2004 18:51 UTC
Every hard-core OS aficionado has done it: Laid out a grand scheme for creating the perfect OS. Taking all the best features and attributes from the OSes we love, and making sure to assiduously avoid the pitfalls of the OSes we don't. Maybe our goals were modest, and we just wanted a slightly tweaked version of an existing OS. But sometimes we're feeling ambitious, and we have large, creative ideas for revolutionizing computing. Long-time OSNews reader and contributor J. Scott Edwards just couldn't help himself, and he has set about to not only plan, but to try to build his dream OS.
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Your proposal reminded me strongly of what (little) I've read about OS/400. In particular the ram as cache as persistent storage idea made me think of OS/400's "single level store":
[quote]
The AS/400 stores objects in a single address space, encompassing virtual memory and the file system. Each object has a single permanent address to which it is referred by all users and processes. Real memory functions as a cache for objects located on disk, managed by the SLIC, invisible to the MI or to OS/400. Programs access objects via the object’s permanent address, rather than copying portions of an object into a user’s address space, then using the temporarily assigned address in this address space. The system assigns all objects a permanent address in the virtual address space. Objects are referenced by name or by pointer, with the virtual addressing mechanism being responsible for moving the object into real memory.
[/quote]
You'll find that paragraph and more at http://pages.sbcglobal.net/vleveque/AS400_Arch.doc