Since this description of the system is fairly vague, you will have to make certain assumptions to answer the questions. Read the questions below and before you start you answer clearly list/state all assumptions that you will be making to answer the question.

Consider that you are designing the OS for a mysterious client. The full functionality of the OS is never elaborated to you; however, you are provided the following bits and pieces of information are available to you.

1. Number of processes in execution is fixed, i.e. there are always X number of processes in execution.

2. These X processes request the same number of resources Y every time.

3. When and how a process would request a resource is never known.

4. User is allowed to execute new task (via a custom shell) in which case an older task has to be stopped.

Given your design decisions, the requirement of the system; list and elaborate on all possible mechanism which can be used to detect race conditions during runtime in this system.

A solution that can detect more scenarios than others will be considered better, keeping view that the underlying assumptions and design are reasonable and implementable. Simply stating race conditions cannot be detected at runtime will be awarded with zero marks. Marks will be deducted for writing unnecessary and irrelevant details like the definition of race conditions etc.

Answer rating: 100% (QA)

Designing an operating system needs these steps 1 First of all we will have to decide what our opera... View the full answer