Learning about "The Unix Time-Sharing System"
gwynforthewyn
18 points
8 comments
August 22, 2026
Related Discussions
Found 5 related stories in 55.7ms across 4,128 title embeddings via pgvector HNSW
- Late.sh – a command-line Clubhouse for computer people itherseed · 60 pts · July 22, 2026 · 48% similar
- LLMs are proof that Unix won Pseudomanifold · 40 pts · August 21, 2026 · 46% similar
- Linux on the Sega 32X. Who needs hardware synchronization primitives anyway? cakehonolulu · 118 pts · July 13, 2026 · 46% similar
- Systems and Delays vinhnx · 48 pts · July 26, 2026 · 44% similar
- Co-Opting Linux Processes for High-Performance Network Simulation (2022) teleforce · 19 pts · July 24, 2026 · 43% similar
Discussion Highlights (2 comments)
gwynforthewyn
I'm the writer of this essay. My subject is some details surrounding the first white paper that Bell Labs published about Unix was "The Unix Time-Sharing System". I wrote what Ken Thompson was doing in between the end of Multics but before he found the "little used PDP-7" that he wrote Unix on, the difference between opening files on Multics and Unix, and what the "comfile" mentioned in the paper is. I wrote this without AI involvement; I follow Unix history because I love knowing what the history is and what I can learn from it, and I love showing others these sorts of cool details. I'd love to hear any feedback you might have :)
bch
> So what's a comfile? Clearly it's a shell script, yeah? So why're they called comfiles? It's short for "command files". The vestige I'm amused by on my (BSD) systems is <foo>.S files. "S" for "Source". From the time when "source code" meant "assembly". Python, zig, C++, C, etc would be invented later...