Computers and Operating Systems overview
100 topics in 13 lessons, each in one line. Every topic opens the page that teaches it.
After this course you can
- Name every part of a desktop, laptop and phone, read its specification, and choose a part that fits.
- Explain what an operating system does, and carry out the same task on Windows, Linux and macOS.
- Work from a symptom to a cause with the six-step method the A+ exams test.
1What a computer is
- What a computer doesEvery computer does the same four things
- Hardware and softwareHardware is the machine. Software is the instructions it follows.
- Bits and bytesInside, everything is a number written in 0s and 1s
- SizesKilobyte, megabyte, gigabyte, terabyte: each is 1,000 of the last
- Kinds of computerPhone, laptop, desktop, server: the same machine in four shapes
- The parts of a computerSix parts, one job each
- The course aheadThe hardware, then the operating system, then the work
2Inside the computer
- Inside the computerThree parts do no computing, and nothing runs without them
- The motherboardEverything plugs into the motherboard
- Power supplyThe wall gives the wrong kind of power for chips
- CoolingHeat goes from chip to metal to air to outside
- Expansion cardsA card adds something the board does not have
- LaptopsThe same parts, smaller and mostly fixed in place
- What comes nextNext: the two parts that decide how fast it feels
3The processor and memory
- The processorA processor follows simple instructions, one at a time
- Cores and threadsA core does one thing at a time
- Clock speedThe GHz figure is how many billion steps it takes each second
- MemoryMemory is the desk. Storage is the filing cabinet.
- Running out of memoryWhen memory is full, the disk stands in
- Memory typesDDR4 and DDR5 do not mix
- Finding the limitThe full gauge names the part
4Storage
- What storage is forMemory forgets at power-off. Storage keeps your files.
- Hard disks and SSDsOne has to move to the data; the other does not
- How a drive connectsSATA uses a cable. NVMe plugs straight into the board.
- File systemsA new drive is blank. Formatting gives it an index.
- When a drive failsTwo disks holding the same data survive one failure
- Drive healthA drive counts its own faults
- What comes nextNext: how everything outside the case plugs in
5Ports, cables and displays
- What ports are forEvery port does one of five jobs
- USBUSB is one family that keeps getting faster
- USB-COne shape, many possible contents
- Connecting a screenA screen connects by HDMI or DisplayPort
- Resolution and refresh rate4K is four times the pixels of Full HD
- The network portOne port and one kind of cable join the wired network
- The weakest linkA connection runs at the speed of its slowest part
6What an operating system does
- Why an operating systemPrograms would have to know every device, and take turns
- The kernelPrograms never touch hardware. They ask the kernel.
- ProcessesA process is a program that is running
- ProcessesOne core runs one process at a time
- Memory managementEvery process gets its own private memory
- Files and foldersFiles live in folders, and a path leads to each one
- DriversA driver teaches the kernel one device
- Users and permissionsEvery request is checked against who is asking
- The five jobsAn operating system does five jobs
7How a computer starts
- The start-up problemThe operating system is on the drive, and memory is empty
- The start-up sequenceFour programs run in turn, and each loads the next
- FirmwareFirmware tests the hardware, then looks for a drive to start from
- Bootloader and kernelThe bootloader finds the kernel and hands over
- ServicesOne process starts everything else
- Trust at start-upWhatever starts first controls everything after it
- Start-up failuresHow far it got tells you what failed
8Windows, Linux and macOS
- Three familiesWindows, Linux and macOS, and where you meet each
- Three systemsThe same jobs under three sets of names
- File layoutDifferent paths, the same places
- Installing softwareWhere software comes from decides how it stays updated
- Updates and end of lifeEvery version has an end date
- The command lineThe same jobs, typed
- Where to go for moreThe command line has a course of its own
9Installing, updating and backing up
- Three habitsInstall once, update regularly, back up every day
- Installing a systemWhat survives depends on how you install
- UpdatingUpdates go out in rings
- Why back upData is lost in four ways
- The 3-2-1 rule3 copies, 2 kinds of storage, 1 somewhere else
- Ways backEach safety net brings back a different thing
10Virtual machines and containers
- Why virtual machinesSeveral pretend computers can share one real one
- Three ways to run softwareA virtual machine brings its own operating system
- HypervisorsA hypervisor runs on the hardware, or on an operating system
- Sharing a hostProcessor time can be promised twice. Memory cannot.
- SnapshotsA snapshot freezes the disk and records changes beside it
- ContainersA container carries the application, not a kernel
- ChoosingChoose by what must be kept apart
- Where to go for moreContainers have a course of their own
11Mobile devices and printers
- Inside a phoneA phone is a whole computer on one board
- WirelessEach radio suits one distance
- Sync and managementThe data lives in the account
- PrintersTwo questions sort out any printer
- Printer typesFour ways to put a mark on paper
- Laser printingA laser printer draws with light, then powder, then heat
- Printing on a networkOne stuck job blocks the whole queue
12Troubleshooting and professional practice
- Why a methodGuessing is expensive. A method finds the cause first.
- The methodSix steps, always in the same order
- Identify the problemWho is affected tells you where to look
- Form a theoryHalve the problem with every test
- Test the theoryOne change at a time, cheapest test first
- EvidenceThe log has usually recorded the cause
- Finish the jobVerify it, prevent it, write it down
- Professional practiceThe fix is half the job
- TicketsEvery request becomes a ticket
- Change managementA change needs a plan, an approval and a way back
- CommunicationSay what happened, what you did and what comes next
- SafetyA spark too small to feel can destroy a chip
- PrivacyYou will see private data. The job is to not use it.
13The laptop got slowWorked case
- The problemA slow laptop is a symptom; four parts can be the limit
- Measure firstRead every gauge before naming a cause
- The first guessA processor that mostly waits is not the limit
- The causeMemory runs out, the disk stands in, and everything waits
- The fixFix the cause, then read the same gauges again
- The trade-offThe cheapest fix that removes the cause comes first
- The methodSix steps, the same for every fault
- A real caseAt Netflix, a slow server gets ten checks in a fixed order
Sources and credit
43 sourcesThe chapters and drawings are written by NeuroqAI from these sources. Each lesson lists its own at the end of its chapter, and figures on the pages are taken from them or computed from them.