Orientation to Computing — I
Unit 2: Operating System & Computer Languages
From pressing the power button to writing your first program — understand how software controls hardware, how code becomes executable, and why Linux dominates the world's servers.
🏢 Industry-Aligned | 📝 15 MCQs (Bloom's Taxonomy) | 🔬 5 Lab Exercises | 💼 Interview & Career Prep
Why This Chapter Changes How You Think About Computing
Without an operating system, your ₹80,000 laptop is a fancy paperweight. The OS is the invisible manager that lets you click icons, open files, and run programs. It decides which app gets CPU time, how much RAM Chrome can use, and where your files live on the SSD. Every single thing you do on a computer — from typing in WhatsApp to deploying code on AWS — is managed by an OS.
And the code you write? It doesn't magically run. Your Python script goes through a chain of transformations — from human-readable text to machine instructions that the CPU understands. Understanding that chain (source code → compiler/interpreter → machine code) makes you a fundamentally better programmer. When something breaks, you'll know where and why.
🏢 Industry Snapshot — Who Uses This Knowledge Daily?
ISRO (Indian Space Research Organisation) — Chandrayaan-3's landing system ran on a Real-Time Operating System (RTOS). In space, every millisecond matters — a regular OS like Windows could pause the landing software to update an icon. An RTOS guarantees "this task completes within 5 microseconds, period." ISRO engineers choose OS types the way pilots choose aircraft.
Infosys & TCS — 80% of enterprise backend systems run on Linux. Every fresh hire at Infosys learns the boot process, kernel commands, and process management in their first 3 months. When a production server crashes at 2 AM, you need to understand what the kernel logs are telling you — this chapter gives you that skill.
Google — Android (the OS on 95% of Indian smartphones) is built on the Linux kernel. Chrome OS, Google's cloud servers, YouTube's infrastructure — all Linux. The compiler team at Google maintains LLVM/Clang, which compiles code for billions of devices. Understanding compilers isn't academic — it's Google's core infrastructure.
Prerequisite Checklist ✅
- ✅ You've used Windows or Android — that means you already interact with an OS daily
- ✅ You know what CPU, RAM, and storage are (from Unit 1)
- ✅ You've heard of Python, Java, or C — even if you haven't written code yet
- ✅ No programming experience needed — this chapter is about understanding, not coding
Learning Outcomes — Bloom's Taxonomy
| Bloom's Level | Learning Outcome |
|---|---|
| L1 — Remember | List the functions of an OS (process, memory, file, device management) and name the phases of a compiler |
| L2 — Understand | Explain the complete boot sequence from pressing the power button to the login screen, and describe the difference between compilation and interpretation |
| L3 — Apply | Trace a simple program through compiler phases (lexical analysis → parsing → code generation) and identify the OS type suitable for a given use case |
| L4 — Analyze | Compare monolithic vs microkernel architecture and analyze why Linux dominates server environments while Windows dominates desktops |
| L5 — Evaluate | Justify the choice between Python (interpreted) and C (compiled) for an e-commerce recommendation engine, considering performance, development speed, and team expertise |
| L6 — Create | Design a boot sequence flowchart for a custom embedded system and write pseudocode that maps to compiler phase outputs |