CPT 304: Operating Systems Design & Theory - Summary Blog Post

 This course enabled me to better understand the fundamental functions, designs, and objectives of operating systems (OS). Initially, I had a limited perception of an operating system as software that made a computer’s hardware usable. However, my knowledge on the topic has significantly expanded. I now see an operating system as a robust and structured system managing hardware resources, overseeing user and program interactions, and ensuring the computer environment’s security. This blog post summarizes the concepts and fundamentals underpinning operating systems and how I will employ that knowledge in subsequent academic and professional pursuits.

I learned that an operating system isn't a single, unbreakable unit; instead, it has a modular structure to provide flexibility, performance, and scalability. Typical operating system structures are the monolithic kernel, microkernel, modular, and layered. For example, a monolithic system like Linux provides all the fundamental services in one layer, which can be fast but complex to maintain. In contrast, microkernels offload everything not core to the kernel, like IPC and device management, to simplify the design and isolate faults.

OS structures also influence a system's performance, maintainability, and scalability. I understood why a company like Microsoft or Apple would select a particular design model for Windows or macOS, or why mobile operating systems like Android customize the Linux kernel to provide efficient operation while conserving battery.

Processes are running programs, and current OSs need to handle process creation, execution, termination, and communications at the same time. A significant point is to learn that OSs support scheduling algorithms like FCFS, SJF, and Round Robin to allocate CPU time among processes to maintain efficiency. The algorithms also affect how equitably and responsively a system can attend to user and system tasks.

Processes may also need to communicate and synchronize, which requires IPC. A simple instance is a pipe in Unix, while shared memory segments might be used in more complex systems. IPC facilitates cooperative multitasking and modular applications. Semaphores, mutexes, and monitors are used to avoid race conditions and deadlocks.

In the beginning, I didn't wholly understand how Operating Systems work to allocate and manage memory. But by learning about central memory management (paging and segmentation) and virtual memory, I better grasp how Operating Systems provide an illusion of a larger memory size for a program, even if only limited physical RAM is available.

Virtual memory uses secondary storage on disk to extend available RAM to efficiently run large programs while adding protections. Page tables, TLBs, and demand paging are all tools and techniques to make virtual memory a reality. This is especially relevant for projects with constrained resources like embedded systems or shared cloud infrastructure.

One key component of my concept map was dedicated to how modern OSs manage files and storage. The file system intermediates between a human-friendly file structure and hardware data blocks. Operating systems use directories, metadata, file descriptors, and access permissions to manage files. The physical storage devices are abstracted with block I/O and caching mechanisms.

Mass storage devices such as SSDs and HDDs are managed with scheduling algorithms such as SCAN or C-SCAN to reduce seek time and to improve overall disk utilization. I learned how I/O subsystems interact with device drivers and how OSs use interrupts, buffers, and spooling to manage input/output.

My concept map's protection and security section discusses how OSs control access to system resources and prevent malicious attacks. While I did not focus on specific security features like authentication or encryption, I covered violation categories, security layers (physical, human, software), and access control methods like access matrices and domain-based protection.

I had a more comprehensive understanding of the importance of layers in operating systems to help maintain data integrity and prevent malicious or accidental misuse. I also understand why concepts from this section are essential in today’s working world because of the increase in cyber attacks and crimes in both information technology and cybersecurity roles.

The knowledge I acquired will benefit me in future IT courses and careers. As a programmer and system architecture enthusiast, knowing how operating systems work helps me write more efficient code, anticipate performance bottlenecks, and interact more intelligently with APIs and system services. Whether working on a server backend, optimizing a game, or securing cloud-based systems, I have a foundation that links software behavior with hardware processes.

In the future, I plan to dive deeper into Linux and explore the concepts we covered in the course. I may even try contributing to an open-source project or setting up my custom environment for development and experimentation. There is also apparent practicality in understanding OS internals for DevOps, systems administration, or even ethical hacking roles.

OS has become an integral and invisible entity in computing. It ensures that everything is working together seamlessly. This includes executing programs, managing the memory, protecting information, and more. The main idea is to make it responsive and efficient. From this course and my concept map, I learned that the basic concepts in operating systems are process and memory management, system structure, files, I/O handling, and protection. Each ties in with the others to use resources efficiently, securely, and fairly. With the knowledge I gained from this course, I will be able to better face future technical situations and understand the complexity of the simplest user-computer interaction.