Linked by Thom Holwerda on Mon 25th Nov 2013 17:43 UTC
IBM

The Ars Technica article on OS/2 mentions, in passing, Workplace OS, the pie-in-the-sky successor to OS/2 IBM was working on. I found this fantastic journal article written by Brett D. Fleisch and Mark Allan A. Co, which goes into this failed project in great detail.

IBM's Microkernel, named Workplace OS microkernel, was the core components of Workplace OS, a portable successor of OS/2. The basic premise of Workplace OS work was: 1) IBM would adopt and improve the CMU Mach 3.0 microkernel for use on PDAs, the desktop, workstations, and massively parallel machines, and 2) that several operating system personalities would execute on the microkernel platform concurrently. This architecture would allow users to switch between applications written for different operating systems while IBM would also benefit by having one common platform for all product lines. The goals of the microkernel and the technical features of design are described in this paper. We also present lessons that may benefit future projects with similar goals.

Also, I get to use the IBM icon!

Thread beginning with comment 577447
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Interesting
by kwan_e on Tue 26th Nov 2013 15:15 UTC in reply to "RE[4]: Interesting"
kwan_e
Member since:
2007-02-18

So it's not really a fork, or a generalization of fork, but a component of what could become a fork. As a matter of semantics.

Reply Parent Score: 2

RE[6]: Interesting
by some1 on Tue 26th Nov 2013 15:20 in reply to "RE[5]: Interesting"
some1 Member since:
2010-10-05

OK, let's say that NtCreateProcess and NtCreateThread together allow one to write fork(), fork()+exec(), spawn(), subset of clone(), and some other similar functions.

Reply Parent Score: 3

RE[7]: Interesting
by kwan_e on Tue 26th Nov 2013 15:29 in reply to "RE[6]: Interesting"
kwan_e Member since:
2007-02-18

Okay, I get it.

Reply Parent Score: 2