Unix v4 復元: SimH エミュレータ上で最初の C カーネルを復元する

50年以上にわたり、コンピューティング史の鎖における重要なリンクが欠けていました。オペレーティングシステムの後の反復が現代コンピューティングの基盤となった一方で、Unix v4—1973年にさかのぼるバージョン—は、時間の流れに失われたと考えられていました。それが変わったのは、ユタ大学の資料室にあった9トラック磁気テープが正常にイメージ化され、復元されたときです。

これは単なる博物館の展示品ではありません。このバージョンは、オペレーティングシステムがアセンブリからCに移行した特定の瞬間を示すため、ソフトウェアのポータビリティの誕生を表しています。復元が完了したことで、愛好家や研究者はこの遺物を探索できるようになりました。コードは利用可能で、ドキュメントは読みやすく、仮想化のおかげで今日のラップトップ上でこの1973年の環境を起動できます。

User Experience: Running Unix v4 with the SimH Emulator

歴史的な仕組みに飛び込む前に、実際にこのシステムとどのように対話するのかを見てみましょう。The recovery of Unix v4 is functional. これは単にコードのスキャンされたPDFではなく、実行可能なライブオペレーティングシステムです。

ただし、シームレスな「プラグアンドプレイ」の体験を期待しないでください。1973年のOSを実行するには、50年のハードウェアギャップを埋める必要があります。このコードを動作させる標準的な方法は、SimH emulatorです。これはDEC PDP-11のような歴史的なハードウェアをシミュレートするために設計された非常に有能なツールで、the minicomputer Unix v4 was originally built for.

The Boot Process

このバージョンを動作させるのは、ISOをマウントするほど単純ではありません。コミュニティのテストと復元チームのメモに基づくと、このプロセスは実験室の実験のように感じられます。ここでは単なるユーザーではなく、システムオペレーターとして行動しています。

1. Environment Setup: PDP-11アーキテクチャをモデル化するように specifically 設定されたSimH emulatorインスタンスが必要です。

2. Tape Loading: 復元された40MBのデータセットがテープ入力として機能します。

3. Compilation: 事前にパッケージ化された最新のディストリビューションとは異なり、初期ブート環境を確立してからOSの一部を自分でコンパイルする必要があると報告されています。

Friction Points

これは生のコンピューティング環境です。安全装置はありません。SimH emulator setupsで正常に動作させているユーザーは、現代のLinuxやBSDシェルと比べてユーザーからのフィードバックが著しく異なることにしばしば気づきます。コマンドは簡潔で、エラーは不可解です。

One verified instance involved a user bridging the gap between eras by running the simulation on an IRIX workstation, adding layers of historical complexity. For most, the challenge lies in understanding the file system hierarchy and the specific limitations of the C compiler from that era. It functions, but it demands you understand the hardware it thinks it is controlling.

The Discovery at the University of Utah

The survival of Unix v4 comes down to luck and the hoarding habits of university researchers. 問題の特定のテープは3M製の9トラック磁気リールでした。ユタ大学コンピューティング学部の資料室に何十年も置かれていました。

The provenance of the tape is significant. It was originally received by Martin Newell. Newell is a name that carries weight in computer science—he is the creator of the "Utah Teapot," a standard reference object in computer graphics. While Newell was revolutionizing 3D modeling, he was also evidently backing up operating systems.

This tape was not labeled as a treasure. It was simply part of a pile of old media that could easily have been discarded during a cleanup. The restoration project, led by Al Kossow of Bitsavers, identified the tape's content not through a label, but by analyzing the raw magnetic data. It turned out to be the only known copy of this specific transition point in Unix history.

Why Unix v4 is the Critical Missing Link

To understand why this recovery matters, you have to look at how operating systems were built before Unix v4.

In the early 1970s, operating systems were inextricably linked to the hardware they ran on. If you wrote an OS for a PDP-11, you wrote it in PDP-11 assembly language. If you wanted to move that OS to a different machine, you didn't just recompile; you rewrote the entire thing from scratch.

The C Language Revolution

Unix v4 changed that. It was the first version where the kernel and core utilities were rewritten in C. This was the moment Unix stopped being a PDP-specific curiosity and became a portable piece of software.

The recovered code confirms this transition. While there is still assembly code present—specifically for the lowest-level hardware interactions—the logic of the system is expressed in C. This structure allowed Unix to eventually spread to every architecture imaginable, from supercomputers to the phone in your pocket.

Verified Code Fragments

The restoration also settled some historical debates and brought legendary code snippets back to light. The most famous of these is a comment found deep in the process switching code. The line simply reads:

"You are not expected to understand this."

For years, this comment was known anecdotally or from later snapshots. Seeing it in its original context within the Unix v4 source tree provides a tangible connection to the developers (Ken Thompson and Dennis Ritchie) who were aware they were performing complex memory manipulation that would confuse future readers.

Technical Analysis of the Recovery

Restoring data from a 50-year-old magnetic tape is a race against physics. The magnetic oxide on these tapes binds to the plastic backing with a binder that degrades over time, often turning sticky or flaking off entirely (a condition known as "sticky-shed syndrome").

The Digitization Process

Al Kossow did not simply put this tape in a standard drive. The mechanical stress of a vintage tape drive could have stripped the oxide right off the backing, destroying the data permanently.

Instead, the team used a specialized, gentle transcription method involving high-speed multi-channel A/D (Analog to Digital) converters. They didn't read "files"; they read the magnetic flux transitions directly from the physical media. This raw data was huge—far larger than the original 40MB capacity of the tape.

From Flux to Files

The raw dump was processed in a modern environment with massive overhead. It took roughly 100GB of RAM to hold the transition data while software analyzed it to determine where the 1s and 0s actually were.

Len Shustek, a key figure in this preservation effort, wrote custom programs to decipher this magnetic map. The software had to interpret the signal timing to reconstruct the bitstream. This is forensic computing. They reconstructed the logic of the Unix v4 file system from what was essentially magnetic noise.

The result is a complete snapshot. It includes the kernel, the user-space utilities, and the documentation, all dating precisely to November 1973.

Legacy and Modern Application

The release of the Unix v4 source code offers more than nostalgia. It provides a baseline for understanding complexity. Modern operating systems are comprised of millions of lines of code, making it nearly impossible for a single person to grasp the entire system.

Unix v4 is small. It is understandable. A single student or engineer can read the kernel source and hold the entire logic of the operating system in their head. This makes it an invaluable educational tool.

When you boot this system on a SimH emulator, you are interacting with a machine that supports multiple users and preemptive multitasking, yet runs on a few kilobytes of memory. It serves as a reminder of efficiency. The utilities found in this version—grep, diff, cat—are the direct ancestors of the tools developers use today. They work largely the same way, proving that the design philosophy established in 1973 was fundamentally sound.

For the community, the next steps involve documentation and stabilization. While the tape has been read, the ecosystem around running Unix v4 easily is still being built. The barrier to entry remains high, requiring familiarity with legacy hardware architectures. But the data is safe. The gap in the timeline has been filled.

FAQ: Unix v4 and Historical Restoration

Q: Can I install Unix v4 on a modern laptop directly?

A: No, Unix v4 was written for the DEC PDP-11 and cannot run on x86 or ARM processors natively. You must use hardware virtualization software like the SimH emulator to translate the instructions.

Q: What makes Unix v4 different from previous versions like v1 or v3?

A: The primary difference is the language implementation. Unix v4 is the first version where the kernel was rewritten in C, moving away from pure Assembly language and making the OS portable to other hardware.

Q: How was the data recovered from the decaying tape?

A: Archivists used a high-speed analog-to-digital converter to capture the magnetic flux of the tape into a massive RAM buffer. Custom software then analyzed these waveforms to reconstruct the binary data without relying on the physical logic of an old tape drive.

Q: Is the "You are not expected to understand this" comment real?

A: Yes, the recovery confirms the comment exists in the source code. It appears in the context of a tricky section of process switching code, serving as a warning to other developers about the complexity of that specific routine.

Q: Where did this specific tape come from?

A: The tape was found in the archives of the University of Utah. It originally belonged to Martin Newell, a computer scientist famous for creating the Utah Teapot 3D model.

Q: How large is the recovered OS?

A: The entire recovered dataset is approximately 40MB. However, the operating system itself is incredibly small by modern standards, designed to run on machines with very limited core memory.