惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

美团技术团队
Microsoft Azure Blog
Microsoft Azure Blog
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
B
Blog
Y
Y Combinator Blog
博客园_首页
有赞技术团队
有赞技术团队
博客园 - Franky
腾讯CDC
G
Google Developers Blog
Recent Announcements
Recent Announcements
博客园 - 【当耐特】
D
Docker
The GitHub Blog
The GitHub Blog
MyScale Blog
MyScale Blog
H
Help Net Security
Apple Machine Learning Research
Apple Machine Learning Research
A
About on SuperTechFans
D
DataBreaches.Net
T
The Blog of Author Tim Ferriss
V
V2EX
U
Unit 42
aimingoo的专栏
aimingoo的专栏
WordPress大学
WordPress大学

LWN.net comments

tcmalloc's weird hack [LWN.net] Fixed? [LWN.net] mpd [LWN.net] Userspace AX.25 [LWN.net] RIP [LWN.net] My two cents... [LWN.net] pipx [LWN.net] Tragedy [LWN.net] A young man destined for glory [LWN.net] And 'less' won't let you search [LWN.net] A great loss [LWN.net] Sad and shocking news [LWN.net] Easy migration from Clementine [LWN.net] Sad coincidence [LWN.net] GNOME is actually usable thanks to Seth et al [LWN.net] Sad news :( [LWN.net] armhf supports preempt_rt [LWN.net] MusicBrainz accurracy [LWN.net] On open source maintainership [LWN.net] Let's stop here [LWN.net] Not a new thing [LWN.net] uv is indeed great pgmoneta Some comments on this on a Postgres blog feed [LWN.net] uv [LWN.net] going to Debian [LWN.net] Upgrading 64-bit-capable systems to 64-bit kernels? [LWN.net] Free Software foundations Maintainers can wait for code review but not for publish review? A reasonably extreme point of view [LWN.net]
DSEE for reproducible builds [LWN.net]
jreiser · 2026-05-15 · via LWN.net comments

DSEE for reproducible builds

Posted May 14, 2026 23:07 UTC (Thu) by jreiser (subscriber, #11027)
Parent article: Debian to require reproducible builds

The reproducible build idea was part of the Domain Software Engineering Environment" (DSEE; pronounced "dizzy") which was offered by Apollo Computer Inc around the 1980s and 1990s: thirty to forty years ago. (Apollo Computer and Sun Microsystems were serious competitors in some markets.) Each software component had a Makefile which specified all the tools and versions that were used to build it, and the result of each build contained a unique identifier for that build. Each tool also had such a Makefile (recursively), and the version control system for source code and built components contained the complete history of all components that ever existed. The operating system guaranteed that enough machinery existed to re-create any build in the entire history, using the specified version of each tool at each step. A typical build farm used dozens to hundreds of machines connected by 400MHz token-ring cabling (circular full duplex daisy chain.) It was a chore to keep every machine running during a build of the entire system, which might take several days depending on which point-in-time was chosen to be the epoch.