Revision as of 03:44, 7 March 2006 edit Nagle (talk \| contribs) Extended confirmed users, Pending changes reviewers, Rollbackers 16,117 edits Brief note on secure microkernels. ← Previous edit		Revision as of 03:45, 7 March 2006 edit undo Nagle (talk \| contribs) Extended confirmed users, Pending changes reviewers, Rollbackers 16,117 edits m Fix KeyKOS Next edit →
Line 14: Start up, or [[booting]], of a microkernel can be difficult. The kernel alone may not contain enough services to start up the machine. Thus, either additional code for startup, such as key device drivers, must be placed in the kernel, or means must be provided to load an appropriate set of service programs during the boot process. Some microkernels are designed for high security applications. [[EROS]] and [[~~KeyCos~~KeyKOS]] are examples. Part of secure system design is to minimize the amount of trusted code; hence, the need for a microkernel. Work in this direction, with the notable exception of systems for IBM mainframes such as [[~~KeyCos~~KeyKOS]] and IBM's [[VM]], has not resulted in widely deployed systems. ==Tradeoffs in microkernel design==

Microkernel: Difference between revisions