OS Abstraction

Abstraction in operating systems hides complex, low-level hardware details and provides simplified, consistent interfaces for users and programmers. Here's how this benefits everyone:

✅ For Users

• Simplicity: Users don't need to understand how files are stored on a disk or how memory is managed—they simply interact with files, folders and applications.

• Consistency: Whether using an SSD, HDD, or network drive, the OS presents everything as a unified "file system."

✅ For Programmers

• Portable Code: Applications can run on different hardware without modification because the OS provides standardised APIs (e.g., POSIX, Windows API).

• Focus on Logic: Developers can concentrate on application logic rather than dealing with hardware interrupts, memory registers or device protocols.

• Security and Safety: OS abstractions provide protection through memory isolation and mechanisms like permissions and user authentication.

Examples of Abstractions:

• Physical memory: Virtual memory

• CPU: Processes and threads

• Disk storage: File systems

• Network interface: Sockets

• I/O devices: Device drivers & APIs

Context: This list maps raw hardware resources to the specific software abstractions provided by the operating system to simplify development and usage.

🧠 2. How might OS design differ between general-purpose and specialised systems (e.g., embedded systems)?

Different design goals and constraints lead to distinct OS architectures:

• User Interface:

  • General-Purpose OS: Full GUI, multiple users.

  • Embedded OS: Often no UI, or minimal (e.g., LCD/LED).

• Hardware Support:

  • General-Purpose OS: Supports a wide range of devices.

  • Embedded OS: Tailored to specific hardware.

• Resource Management:

  • General-Purpose OS: Designed for multitasking, dynamic loads.

  • Embedded OS: Predictable timing and resource use.

• Performance Priority:

  • General-Purpose OS: Throughput, responsiveness.

  • Embedded OS: Real-time guarantees, low latency.

• Size/Footprint:

  • General-Purpose OS: Large and modular (GBs).

  • Embedded OS: Minimal and lightweight (KBs–MBs).

• Reliability:

  • General-Purpose OS: Fault-tolerant, but user-recoverable.

  • Embedded OS: Mission-critical (e.g., no room for crashes).

• Security:

  • General-Purpose OS: Supports user accounts, sandboxing, etc.

  • Embedded OS: Often simpler security models, but critical.

• Update/Upgrade:

  • General-Purpose OS: Frequently updated.

  • Embedded OS: Rarely updated once deployed.

Context: A comparison of features highlighting how design priorities shift when building an OS for general desktop use versus a high-reliability embedded environment.

Example Use Cases

• General-purpose: Browsing, gaming, office apps, development, etc.

• Embedded: Automotive systems, medical devices, industrial controllers, IoT sensors.

🛠️ Summary

• Abstraction is the OS's superpower—it simplifies, unifies and protects.

• Design priorities vary by domain: desktop systems prioritise versatility, while embedded systems focus on precision and reliability.