Discussion 1: What Is an Operating System?

01 Overview

Course	COMP 3150 / CMIS 3150 — Operating Systems
Unit	Unit 1 — Introduction to Operating Systems
Weight	Part of the 5% participation grade (each discussion is worth approximately 0.4% of the final grade)
Opens	Monday of Week 1
Initial post due	Thursday of Week 1, 23:59 (end of day)
Peer replies due	Sunday of Week 1, 23:59 (end of day)
Format	One initial post (400–600 words) and at least two substantive peer replies (150–250 words each)
CLOs assessed	CLO1, CLO7

02 Learning outcomes addressed

By participating in this discussion you will

Define an operating system and distinguish the two classical views: resource manager and extended machine (U1.1).
Describe the historical evolution of operating systems and explain the technological drivers of that evolution (U1.2).
Compare major operating-system architectures — monolithic, microkernel, and hybrid — and evaluate their trade-offs (U1.4, U1.5).
Articulate a reasoned position on a design question and respond constructively to the positions of others.

This discussion assesses CLO1 (explain operating-system concepts, services, and architectures) and CLO7 (evaluate operating-system technologies).

03 Discussion prompt

The two classical views of an operating system are the resource manager (the OS arbitrates among competing requests for CPU time, memory, storage, and devices) and the extended machine (the OS hides the complexity of the hardware and presents a clean, convenient abstraction to applications).

These two views are complementary, not contradictory — every real operating system does both — but they emphasise different priorities. The resource manager is concerned with fairness, efficiency, and protection; the extended machine is concerned with usability, portability, and abstraction. When a design decision forces a trade-off, the two views may pull in opposite directions.

Your task

Choose one operating system that you use regularly (for example, Linux, Windows, macOS, Android, iOS, or a specialised OS such as FreeRTOS or a real-time OS in an embedded device).
Identify one design decision in that operating system that illustrates the tension between the resource-manager view and the extended-machine view. Examples: the choice of scheduler (fairness versus responsiveness), the memory-management model (protection versus abstraction), the file-system interface (POSIX versus application-specific APIs), or the driver model (monolithic kernel versus microkernel versus hybrid).
Argue for the view that best explains the decision. In your argument, address:
- What problem was the designers trying to solve?
- Which view guided their decision, and what would the other view have suggested instead?
- What are the consequences of the decision for users, for application developers, and for the OS itself?
- Would you have made the same decision? Why or why not?

Your post should be 400–600 words. Use concrete examples and cite at least one source (a textbook, a paper, or the operating system's documentation). Feel free to disagree with the designers of the system you chose — a well-argued critique is worth more than an uncritical description.

04 Guidelines

4.1 Initial post

Length: 400–600 words (excluding citations).
Structure: a clear thesis statement, a body that supports it with concrete examples, and a conclusion that summarises your position.
Citations: at least one authoritative source, cited in a consistent style (APA, IEEE, or another discipline-appropriate style).
Originality: your post must be your own work. You may discuss the prompt with classmates, but the post must be written individually.
Post the initial response before you can see the posts of your classmates (the discussion board is configured this way so that everyone commits to a position before reading the others).

4.2 Peer replies

Respond to at least two classmates.
Length: 150–250 words per reply.
A substantive reply does at least one of the following:
- Challenges the reasoning with a counter-example or an alternative interpretation.
- Extends the argument by connecting it to a different operating system or a different unit of the course.
- Identifies an unstated assumption and explains why it matters.
- Provides a concrete example that supports or contradicts the original post.
A reply that merely agrees ("Great post! I totally agree") does not count. A reply that summarises the original post without adding anything does not count.
Respond to classmates who have not yet received a reply, so that everyone gets feedback.

4.3 Timeliness

The initial post is due by Thursday of Week 1. Posts submitted after the deadline incur a 20% penalty per day, up to the end of the discussion on Sunday.
Peer replies are due by Sunday of Week 1. Replies submitted after the deadline are not counted toward the grade.
Late initial posts cannot be replied to by classmates, which is why the deadline is enforced strictly.

4.4 Netiquette

Be respectful of your classmates' views, even when you disagree with them. Critique the argument, not the person.
Use clear, concise language. Avoid jargon unless you define it.
Read your post aloud before submitting it. If a sentence is hard to read aloud, rewrite it.
If you cite a source, provide enough information for a classmate to find it.
If you are unsure whether a comment is appropriate, ask yourself: would I be comfortable if the instructor and my classmates read it? If not, rewrite it.

05 Grading rubric

The discussion is marked out of 100 points. The criteria and their weights are given below, followed by the descriptors for each level.

Discussion 1 grading rubric — weights
Criterion	Weight
Post quality	40%
Peer response quality	30%
Engagement and timeliness	20%
Netiquette and clarity	10%
Total	100%

5.1 Post quality (40 points)

Level	Descriptor
Exemplary (90–100%)	A clear, well-argued thesis. The chosen design decision is well-chosen and correctly described. The argument for the resource-manager or extended-machine view is convincing, with concrete examples from the operating system. The consequences for users, developers, and the OS itself are analysed. The post engages critically with the designers' decision, not just describes it. Sources are cited correctly.
Proficient (80–89%)	A clear thesis. The design decision is described correctly. The argument is sound but relies on general statements rather than concrete examples. The consequences are mentioned but not fully analysed. A source is cited.
Developing (70–79%)	A thesis is present but not clearly argued. The design decision is described at a high level, without specific details. The argument is largely descriptive. Sources are missing or not relevant.
Beginning (60–69%)	The post does not have a clear thesis. The design decision is described inaccurately or vaguely. The argument is weak or absent.
Not demonstrated (<60%)	The post is missing, off-topic, or a restatement of the prompt.

5.2 Peer response quality (30 points)

Level	Descriptor
Exemplary (90–100%)	Two or more substantive replies. Each reply engages with the classmate's argument, adds a new perspective or a concrete example, and invites further discussion. The replies show that the student has read and understood the original post.
Proficient (80–89%)	Two substantive replies. Each reply engages with the classmate's argument and adds something, but the addition is modest (for example, a supporting example without analysis, or a question that could have been pushed further).
Developing (70–79%)	One substantive reply, or two replies that are largely agreeable and add little to the discussion.
Beginning (60–69%)	One reply that is largely agreeable, or replies that are off-topic.
Not demonstrated (<60%)	No replies, or replies that do not engage with the classmates' posts.

5.3 Engagement and timeliness (20 points)

Level	Descriptor
Exemplary (90–100%)	The initial post is submitted by the Thursday deadline. The peer replies are submitted by the Sunday deadline. The student returns to the discussion to respond to replies on their own post, showing active engagement throughout the week.
Proficient (80–89%)	The initial post and the peer replies are both submitted by the deadlines. The student does not return to respond to replies on their own post, but the required posts are all present and on time.
Developing (70–79%)	The initial post or one of the peer replies is submitted late (within 24 hours of the deadline).
Beginning (60–69%)	Two or more required posts are submitted late (within 48 hours of the deadline).
Not demonstrated (<60%)	The initial post or both peer replies are missing, or submitted more than 48 hours late.

5.4 Netiquette and clarity (10 points)

Level	Descriptor
Exemplary (90–100%)	The posts are respectful, clear, and free of errors that impede comprehension. The tone is appropriate for an academic discussion. Sources are cited consistently.
Proficient (80–89%)	The posts are respectful and clear. A few minor grammatical or citation errors are present but do not impede comprehension.
Developing (70–79%)	Some posts are less clear or contain several errors. The tone is generally respectful.
Beginning (60–69%)	The posts are difficult to follow, or the tone is inappropriate. Citations are missing or inconsistent.
Not demonstrated (<60%)	The posts are disrespectful, or the writing is so unclear that the argument cannot be followed.

06 Resources

Silberschatz, A., Galvin, P. B., & Gagne, G. Operating System Concepts, 10th ed., Chapter 1 (Introduction).
Arpaci-Dusseau, R. H., & Arpaci-Dusseau, A. C. Operating Systems: Three Easy Pieces, Chapter 1 (Dialogue on the Book).
Tanenbaum, A. S., & Bos, H. Modern Operating Systems, 4th ed., Chapter 1 (Introduction).
The Linux Kernel documentation: kernel.org/doc.
Microsoft's documentation on the Windows architecture: learn.microsoft.com.
Apple's documentation on the XNU kernel: developer.apple.com.
Ritchie, D. M., & Thompson, K. The UNIX Time-Sharing System. Communications of the ACM, 1974.
Liedtke, J. On Micro-Kernel Construction. ACM SOSP, 1995.