Right, that is an understatement. The Multics CPUs were multimillion dollar systems with dedicated support staff that took up large rooms. Compared to which most DEC machines of the time were less than toys. That's why UNIX was considered an "emasculated" Multics. It's really sad that BTL bailed, but such is life. The Multics memory protection mechanisms are so much different than what was available then, or now, that porting directly to x86/x84 is not feasible. We got it working under emulation only with much effort. That said, the folks doing the VMS port to x86/64 had similar problems with the x86 architecture. They decided to implement various missing bits in software. A x64 port of Multics would be quite doable using the same techniques. The realization of which is left as a exercise for the reader. For more information see http://multicians.org/https://sourceforge.net/projec... andhttp://ringzero.wikidot.com/ Multics Lives!
"Multics rulez, UNIX droolz"
Slashdot Mirror
We're making the big-time Dai, eh? H
Right, that is an understatement. The Multics CPUs were multimillion dollar systems with dedicated support staff that took up large rooms. Compared to which most DEC machines of the time were less than toys. That's why UNIX was considered an "emasculated" Multics. It's really sad that BTL bailed, but such is life. The Multics memory protection mechanisms are so much different than what was available then, or now, that porting directly to x86/x84 is not feasible. We got it working under emulation only with much effort. That said, the folks doing the VMS port to x86/64 had similar problems with the x86 architecture. They decided to implement various missing bits in software. A x64 port of Multics would be quite doable using the same techniques. The realization of which is left as a exercise for the reader. For more information see http://multicians.org/ https://sourceforge.net/projec... andhttp://ringzero.wikidot.com/ Multics Lives! "Multics rulez, UNIX droolz"