ELSEIF
Your brief EB
218 stories from 122 feeds 508 clusters Refreshed 21 minutes ago next pull 18:44

DEV TOOLS Signal 501

Newsletter revisits Unix's early design decisions from Thompson and Ritchie's original paper

Illustration only Photo by Ivan N on Unsplash

A newsletter issue examines the paper "The Unix Time-Sharing System" by Dennis Ritchie and Ken Thompson, tracing Unix's origins from Ken Thompson's disk-throughput experiments on a PDP-7 to the open/create system call design that separated data from programs.

WHY IT MATTERS

The open/create and exec system calls that Unix introduced were a deliberate rejection of Multics' single-level store, and that design choice still shapes how every modern operating system handles files and program execution. Understanding the original rationale clarifies why the file abstraction works the way it does for engineers who build on top of it daily. Only one feed carried this, so it is a single-source educational piece rather than a widely reported event.

Written by elseif from the cluster below · every claim links back to a source

The three things worth knowing

01

Ken Thompson built the first Unix on a little-used PDP-7 after losing access to a GE-645, completing a compiler, editor, assembler, loader, and user protection in roughly three weeks of assembly.

02

Unix's open/create system call design deliberately separated data from programs, rejecting Multics' single-level virtual memory store where segments were faulted in without distinguishing instructions from data.

03

The exec system call was added so that a file could be explicitly invoked as a program, a concept absent in Multics where instructions and data shared one unifying virtual memory space.

THE CLUSTER

Same story, 1 feed.

ORDERED BY FIRST SEEN
playtechnique.io via Hacker News Learning about "The Unix Time-Sharing System" Open ↗