From the Command Line to Containers

The endeavor to reconstruct a fully functional UT Austin Decwar SDT represents a significant act of digital archeology. The project's evolution through three distinct stages in its development workflow offers a unique case study in the nature of computing systems. It demonstrates how a system is defined not just by its original hardware and software, but by the modern tools used to resurrect and interact with it. Developing and maintaining software for legacy computing environments such as the DEC PDP-10 presents a unique set of challenges. These systems, while historically significant, often rely on workflows and hardware that are incompatible with modern development practices. The need to bridge this technological gap, preserving the integrity of the original environment while leveraging the efficiency of contemporary tools, is paramount.

For any software reconstruction project, the first strategic imperative is to establish a stable, simulated hardware environment. This foundation serves as the core or historical substrate, upon which all subsequent creative and technical work is performed. For the SDT project this foundation consists of a meticulously simulated historical computing environment with DEC PDP-10 hardware running the TOPS-10 operating system and a particular early Fortran IV compiler. This environment forms the static, historical core around which the project's dynamic and evolving development workflow is built. It is this core that the developers had to interact with, leading to the initial dynamic challenge of bridging the gap between modern tools and the faithfully recreated past.

This document will examine the three eras of this reconstruction, beginning with the foundational SIMH PDP-10 environment itself and tracing the evolution of the development methodology from earlier, more cumbersome methods to a modern containerized approach, detailing the technical components and concluding with an analysis of the benefits this modernization delivers.

To fully appreciate the innovations of Project SDT, it is essential to understand the historical development workflows that preceded it. The journey toward a modern, portable environment was a three-stage evolution, with each phase introducing improvements while also revealing limitations that prompted the next leap forward. This progression from early manual experiments to a fully abstracted, containerized system highlights a deliberate path toward greater efficiency and portability.

The journey from initial dependence on the Kermit protocol and simple file transfers into and out of a SIMH PDP-10, to a more authentic system using SIMH tape image files and a reconstructed SDT, and finally to a fully containerized environment reveals a fascinating interplay between historical authenticity, developer efficiency, and the modern imperative for portability. We will trace the project's workflow from the pragmatic but awkward Kermit era of 2024, through the efficient and realistic SIMH tape image era that began at the end of 2024, to the ultimate containerized portability achieved in late 2025, a year after the project's inception. This progression is a compelling narrative of how a historical platform is re-contextualized and ultimately preserved through the lens of contemporary technology and development culture.

The result is a modern, container-based solution designed to overcome many of the practical obstacles. It transforms the intricate process of building and running a complete PDP-10 system and environment into a simple, automated, and platform-independent workflow. It simultaneously achieves historical fidelity by preserving the original tape-based build process and embraces modern principles through complete automation and hosting abstraction. By encapsulating the entire environment, both legacy and modern, within a set of interoperable containers, the project has freed the historical UT Austin Decwar artifacts from hardware-specific constraints and manual, time-consuming setup procedures.