Re:Half an operating system: The triumph and tragedy of OS/2
by chiph on Monday November 25, 2013 @08:17AM
(#6793854)
The thing I find interesting about OS/400 (or whatever it's name is this month) is the single-level store. When your program needs access to the contents of a file, it's just a memory offset. The OS relies on the swapping mechanism to bring those pages into available memory. Which, when you have flat 64 (one could argue 65) bit addressing … why not?
[ Parent
| on HN ]
Re:Half an operating system: The triumph and tragedy of OS/2
by rodgerd on Monday November 25, 2013 @07:53PM
(#6798298)
"Everything's a file!"
"No, everything's memory!"
Re:Half an operating system: The triumph and tragedy of OS/2
by angersock on Monday November 25, 2013 @10:46AM
(#6794650)
Wait wait wait...so it effectively memory maps all the things?
Mainframe environments are weird.
Re:Half an operating system: The triumph and tragedy of OS/2
by pjmlp on Monday November 25, 2013 @02:09PM
(#6796181)
And OS/400 files are libraries that you need to open, as another example of strangeness.
Or the OS/360 which uses virtualization for all OSs, like Hyper V does on Windows.
The first OS to boot from the hypervisor has master rights, but all OSs are virtualized.
Re:Half an operating system: The triumph and tragedy of OS/2
by fulafel on Tuesday November 26, 2013 @05:27AM
(#6800302)
> Or the OS/360 which uses virtualization for all OSs, like Hyper V does on Windows
No, the hypervisor was called VM. According to WP it most frequently ran CMS guests, which was a light weight single-app OS. But could also run OS/360 guests (which predated VM).