home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.mach
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!wupost!sdd.hp.com!elroy.jpl.nasa.gov!nntp-server.caltech.edu!news
- From: ernest@pundit.cithep.caltech.edu (Ernest Prabhakar)
- Subject: Mach 3.0 and Windows NT
- Message-ID: <1992Aug26.184528.1886@cco.caltech.edu>
- Sender: news@cco.caltech.edu
- Nntp-Posting-Host: pundit.cithep.caltech.edu
- Reply-To: ernest@pundit.cithep.caltech.edu (Ernest Prabhakar)
- Organization: California Institute of Technology, Pasadena
- Date: Wed, 26 Aug 1992 18:45:28 GMT
- Lines: 30
-
- [I'm probably going to regret this]
- Could anyone clarify for me the relationship/similarity between Mach 3.0 and
- the micro-kernel portions of Windows NT. That, I don't want to get into DOS
- vs. Unix compatibility. I just want to know what low level features each
- 'core' supports. I've heard that lots of Mach developers went to Microsoft to
- build NT, and I've been told they have a lot in common, but I am curious as to
- details.
-
- I know (or at least think) that Mach supports the following:
- - user-level light weight processes (threads)
- - a common IPC format using Mach ports, and MIG
- - dynamically loadable kernel device drivers (or something like that)
- - flexibly memory management
-
- Are these facilities all available in NT? In the same fashion? Is there some
- sort of isomorphism?
-
- I think this would be an interesting discussion to have on the Net, but if I
- get significant e-mail on this I will summarize.
-
- Thanks for your time,
- - Ernie P.
-
-
- --
- Ernest N. Prabhakar Caltech High Energy Physics
- Member, League for Programming Freedom (league@prep.ai.mit.edu)
- CaJUN President NeXTMail:ernest@pundit.cithep.caltech.edu
- "...and ourselves, your servants for Jesus sake." - II Cor 4:5b
- #import <std/disclaimer.h>
-