← Back to catalogue
Research draft

operating system

vr.tr.operating-system · PHY.OBJ

Let an agent identify which operating system and version a device runs, explain what the system is responsible for, relay support lifecycles, security update and compatibility information from vendors, and separate the operating system from firmware, applications and hardware.

Thing Registry Physical world and living systems

Research draft, second pass

A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.

written by Claude from model knowledge without web access - no source was read, every claim is a lead to verify

Researched by: Claude

Purpose and description

Let an agent identify which operating system and version a device runs, explain what the system is responsible for, relay support lifecycles, security update and compatibility information from vendors, and separate the operating system from firmware, applications and hardware.

The system software that manages a computer or device: it controls hardware, schedules processes, manages memory, storage, files, devices, networking and security, and provides the interfaces that application programs and users depend on; examples include Windows, macOS, Linux distributions, Android, iOS and real-time systems for embedded devices.

What it is for: Running a computer and the programs on it.

It can be identify the system and version on a device; explain what the operating system does; relay support and update information; compare systems for a use case.

Distinguishing features

Sits between hardware and applications

Owns processes, memory, files, devices and access control

Has a version and a support lifecycle

Firmware and applications are separate layers

What it looks like

Not visible as an object; seen through its user interface, its name and version in settings, and its command shell.

How it is recognised

Name and version shown in system settings or by a command

Kernel, shell and package manager identify a Linux distribution

Firmware such as BIOS or UEFI starts the machine and is not the operating system

Related models

is a kind of - the category

system software

runs on - the hardware it manages

computer

is confused with - BIOS and UEFI start the machine but are a different layer

firmware

runs - what the system exists to host

application software

In practice

Families and kinds

desktop and laptop systems such as Windows, macOS and Linux distributions

mobile systems such as Android and iOS

server systems

real-time and embedded systems

systems for televisions, cars and appliances

Identifiers

name and version vendor naming shown in settings

kernel version numeric for Linux and similar systems

build number vendor specific identifies the exact release

Standards and regulation

POSIX from IEEE for interfaces

Vendor support lifecycle policies

Security certification schemes such as Common Criteria

Accessibility requirements in public procurement

Failure modes and hazards

Unsupported versions without security updates

Driver and hardware incompatibility

Data loss during upgrades

Malware exploiting system vulnerabilities

Also called

BIOSABIOSFlash BIOSIBM PC ROM BIOStelevision operating systemmobile operating systemproprietary operating systemoperating environmentsmartwatch operating systemfree operating systemAmigaDOSGuardianembedded operating systemWebAssembly System InterfacevisionOSDebian derivativesMicrosoft WindowsUnix-like operating systemcross-platformreal-time operating systemnetwork operating systemsingle-user operating systemmulti-user operating systemmulti-tasking operating systemsingle-tasking operating systemlibrary operating systemtemplated operating systemsingle address space operating systemlive distributionTrusted operating systemsecurity-focused operating systemoperating system distributionWoW64Mac operating systemhobbyist operating systemdistributed operating systemdisk operating systemAmigaOS-like operating systemNewDos/80Object-oriented operating system

+39

Where this came from

wikidata · CC0 1.0

Drafted structure

Bundle to layer to finding to question, as the second pass will find it: 4 bundles · 8 layers · 8 findings · 16 questions.

Identify Which system this is.

Everything depends on the system and version.

Which system

Name and version.

Which

Which.

  1. Which operating system and version does the device run, and how is that read? definition
  2. Is the question about the operating system, the firmware or an application? boundary

Lifecycle

Support status.

Lifecycle

Lifecycle.

  1. Is this version still supported, and when does support end according to the vendor? provenance
  2. Where is the lifecycle policy published? action
Function What it does.

Responsibilities define the system.

Core

Kernel duties.

Core

Core.

  1. How does the system manage processes, memory, storage and devices? definition
  2. Which entry fits file systems or networking in depth? action

Interfaces

User and program interfaces.

Interfaces

Interfaces.

  1. What interfaces does the system offer to users and to programs? definition
  2. Which standards govern those interfaces? provenance
Operate Running and securing.

Systems need care.

Updates

Updates and patches.

Updates

Updates.

  1. How are updates delivered, and what does the vendor advise about applying them? provenance
  2. Is the user asking for help with a specific device, which needs its vendor support? boundary

Security

Security.

Security

Security.

  1. What security features and hardening guidance do vendors and agencies publish? provenance
  2. Which entry fits malware and incidents? action
Choose Comparing and learning.

Choice and study.

Compare

Comparison.

Compare

Compare.

  1. How do systems compare for a given use case in compatibility, licensing and support? measurement
  2. Which criteria matter for the user? action

Learn

Study.

Learn

Learn.

  1. How are operating systems taught and studied, and which references are standard? provenance
  2. How did operating systems develop historically? provenance

What the second pass must settle

  • Should each operating system be a separate entry?
  • How should support lifecycle dates be linked?
  • The registry entry has merged BIOS aliases, which are firmware; should they be split off?