![1 0 1 1 0 1 1 0 1 1 0 1 1 0 0 1 1 0 1 1 0 1 1 0 1 1 0 1 1 1 0 1 1 0 1 1 0 1 1 1 1 1 0 1
Simple Structure [MS DOS]
Not divided into modules
Initial Operating System.
Simple and lightweight
Single-tasking, no multitasking
Md. Shakib Ahammed](https://image.slidesharecdn.com/osstructure1-241117072011-d6138ac1/85/OS-Structures-MS-DOS-Solaris-Modular-3-320.jpg)
![BBC NW_Tech Facilities_30 Odd Yrs Ago [J].pdf](https://cdn.slidesharecdn.com/ss_thumbnails/bbcnwtechfacilities30oddyrsagoj-250830230619-0d747bd6-thumbnail.jpg?width=560&fit=bounds)
OS Structures ( MS DOS, Solaris Modular)
- 1. 1 0 1 1 0 1 1 0 1 1 0 1 1 0 0 1 1 0 1 1 0 1 1 0 1 1 0 1 1 1 0 1 1 0 1 1 0 1 1 1 1 1 0 1 </ /> } /> [ Operating System Structures 1. Md. Shakib Ahammed (221-15-5431) 2. Saifullah Anik (221-15-4922) Team: Double S
- 2. 1 0 1 1 0 1 1 0 1 1 0 1 1 0 0 1 1 0 1 1 0 1 1 0 1 1 0 1 1 1 0 1 1 0 1 1 0 1 1 1 1 1 0 1 {04} Solaris Modular </ Table of contents Microkernel vs Monolithic Kernel {05} {06} Conclusion {01} Simple Structure {02} Layered Structure {03} Microkernel Md. Shakib Ahammed
- 3. 1 0 1 1 0 1 1 0 1 1 0 1 1 0 0 1 1 0 1 1 0 1 1 0 1 1 0 1 1 1 0 1 1 0 1 1 0 1 1 1 1 1 0 1 Simple Structure [MS DOS] Not divided into modules Initial Operating System. Simple and lightweight Single-tasking, no multitasking Md. Shakib Ahammed
- 4. 1 0 1 1 0 1 1 0 1 1 0 1 1 0 0 1 1 0 1 1 0 1 1 0 1 1 0 1 1 1 0 1 1 0 1 1 0 1 1 1 1 1 0 1 Layered Structure Approach The OS is divided into layers, each responsible for specific functions. Easier to maintain and debug. Performance overhead due to multiple layers. Example: Theoretical OS design (not widely used in practice). Layer 1 Layer 0 Hardware Layer n Md. Shakib Ahammed
- 5. 1 0 1 1 0 1 1 0 1 1 0 1 1 0 0 1 1 0 1 1 0 1 1 0 1 1 0 1 1 1 0 1 1 0 1 1 0 1 1 1 1 1 0 1 Solaris Modular Approach Use object oriented approach Each core components is separate Each is loadable as needed in the kernel Saifullah Anik
- 6. 1 0 1 1 0 1 1 0 1 1 0 1 1 0 0 1 1 0 1 1 0 1 1 0 1 1 0 1 1 1 0 1 1 0 1 1 0 1 1 1 1 1 0 1 Monolithic Kernel Approach All essential services, like drivers and file systems, run within the kernel, simplifying communication Direct access to services within the same space allows faster execution. Less modularity makes debugging and maintenance harder. Saifullah Anik
- 7. 1 0 1 1 0 1 1 0 1 1 0 1 1 0 0 1 1 0 1 1 0 1 1 0 1 1 0 1 1 1 0 1 1 0 1 1 0 1 1 1 1 1 0 1 MicroKernel Approach Remove all the non-necessary programs from the kernel & implement them as system and user level programs. Highly modular and secure. Can be slower due to communication between kernel and user space Saifullah Anik
- 8. 1 0 1 1 0 1 1 0 1 1 0 1 1 0 0 1 1 0 1 1 0 1 1 0 1 1 0 1 1 1 0 1 1 0 1 1 0 1 1 1 1 1 0 1 MicroKernel vs Monolithic Kernel Monolithic Kernel Microkernel 1. Micro-kernel is smaller. It’s execution slower. 2. Easy to add new functionality 3. Easy debugging & management 4. If one component crashes others keep running 1. Monolithic kernel is larger than microkernel. 2. It is not easy to extend monolithic kernel. 3. Difficult debugging 4. If one component crashes, entire system crashes Saifullah Anik
- 9. CREDITS: This presentation template was created by Slidesgo, and includes icons by Flaticon, and infographics & images by Freepik 1 0 1 1 0 1 1 0 1 1 0 1 1 0 0 1 1 0 1 1 0 1 1 0 1 1 0 1 1 1 0 1 1 0 1 1 0 1 1 1 1 1 0 1 } /> [ Team: Double S Thanks! Do you have any questions? </ />