Journal Entry Week 2 – Process Management

1. Identify the topics we covered in class:

This week focused on Process Management. We covered OSTEP chapters 4 to 8, which included Processes, Process API, Limited Direct Execution, CPU Scheduling, and MLFQ Scheduling. We also worked on Lab 2 (learning and scheduling practice), PA2 code, Quiz 2, and our group discussion.

2. Explain what each of the topics were in your own terms:
A process is a program that’s running on the system. The Process API shows how new processes are created and controlled using system calls like fork() and exec(). Limited Direct Execution explains how the operating system allows programs to run directly on the CPU but still keeps control. CPU Scheduling is about how the system decides which process should run next, and MLFQ Scheduling changes process priorities depending on how much CPU time each one gets.

3. Identify least-understood topics:
The hardest part for me this week was PA2, especially setting everything up again after I formatted my laptop.

4. Explain the nature of your confusion:
I had trouble running the testers because I had to reinstall Homebrew and set up my virtual environment all over again. It took time to get everything working properly before I could even test my code. Once I got it running, I still found it challenging to connect the .c and .h files and understand how each function worked together to simulate process behavior.

5. Identify “aha” moments:
My “aha” moment came when the code finally compiled and passed the tests. That helped me understand how the readings and the code were connected — the OS is constantly creating, managing, and switching between processes in the background.

6. Ask questions:
I wonder how these coding ideas are applied in real operating systems and how this will connect to memory management in the next module.

7. Connections to other classes or applications:
This connects to my programming classes because it uses logic, debugging, and problem-solving, especially when dealing with process control and code structure.

Closing reflection:
Even though this week was frustrating at times, it helped me see how much goes into process management. Setting everything up again was tough, but it reminded me how important it is to understand my environment and tools before coding. Overall, I learned a lot from both the technical and problem-solving sides of this week.