HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
dspinellis
unix-history-repo
Assembly2014–2026
dspinellis / unix-history-repo

unix-history-repo

Continuous Unix commit history from 1970 until today

76Distinct people
104Mentions
0Explicit recommenders
7.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Continuous Unix commit history from 1970 until today

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 7:27:27 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year104 dated mentions

Observed mentions: 2014-05-25 22:21:07 UTC to 2026-09-18 12:06:57 UTC.

0510152014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20142015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 10 mentions; 4 submissions, 6 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 13 mentions; 1 submissions, 12 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 6 mentions; 2 submissions, 4 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 7 mentions; 2 submissions, 5 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 10 mentions; 2 submissions, 8 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 9 mentions; 0 submissions, 9 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 17 mentions; 1 submissions, 16 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 9 mentions; 1 submissions, 8 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC211
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC1046
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC13112
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC624
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC211
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC725
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC1028
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC909
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC17116
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC716
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC918
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC707
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC505

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Unix History Repository The history and evolution of the Unix operating system is made available as a revision management repository, covering the period from its inception in 1970 as a 2.5 thousand line kernel and 48 commands, to 2025 as a widely-used 41 million line system. The 2 GB repository contains about 850 thousand commits and more than eight thousand merges. The repository employs Git system for its storage and is hosted on GitHub. It has been created by synthesizing with custom software 22 snapshots of systems developed at Bell Labs, the University of California at Berkeley, and the 386BSD team, and the modern repository of the open source FreeBSD system. In total, about 2700 individual contributors are identified, the early ones through primary research. The data set can be used for empirical research in software engineering, information systems, and software archaeology. You can read more details about the contents, creation, and uses of this repository through this link. Two repositories are associated with the project: unix-history-repo is a repository representing a reconstructed version of the Unix history, based on the currently available data. This repository will be often automatically regenerated from scratch, so this is not a place to make contributions. To ensure replicability its users are encouraged to fork it or archive it. unix-history-make is a repository containing code and metadata used to build the above repository. Contributions to this repository are welcomed. Project status The project has achieved its major goal with the establishment of a continuous timeline from 1970 until today. The repository contains: snapshots of PDP-7, V1, V2, V3, V4, V5, V6, and V7 Research Edition, Unix/32V, all available BSD releases, the CSRG SCCS history, two releases of 386BSD, the 386BSD patchkit, the current FreeBSD repository, which now contains its full history. The files appear to be added in the repository in chronological order according to their modification time, and large parts of the source code have been attributed to their actual authors. Commands like git blame and git log produce the expected results. The repository contains a number of two-way merges. 3 BSD is merged from Unix/32V and Research Edition 6 Various BSD releases are merged from the development branch and a time point of BSD-SCCS Blame is apportioned appropriately. Tags and Branches The following tags or branch names mark specific releases, listed in rough chronological order. Epoch Research-PDP7 Research-V1–6 BSD-1 BSD-2 Research-V7 Bell-32V BSD-3, 4, 4_1_snap, 4_1c_2, 4_2, 4_3, 4_3_Reno, 4_3_Net_1, 4_3_Tahoe, 4_3_Net_2, 4_4, 4_4_Lite1, 4_4_Lite2 SCCS-END, 386BSD-0.0, 0.1, patchkit All release and releng branches found in the FreeBSD Git repository A detailed description of the major tags is available in the file releases.md. More tags and branches are available. The -Snapshot-Development branches denote commits that have been synthesized from a time-ordered sequence of a snapshot's files. The -VCS-Development tags denote the point along an imported version control history branch where a particular release occurred. Cool things you can do If you have a broadband network connection and about 2 GB of free disk space, you can download the repository and run Git commands that go back decades. Run git clone https://github.com/dspinellis/unix-history-repo git checkout BSD-Release to get a local copy of the Unix history repository. View log across releases Running git log --reverse --date-order will give you commits such as the following commit 64d7600ea5210a9125bd1a06e5d184ef7547d23d Author: Ken Thompson <ken@research.uucp> Date: Tue Jun 20 05:00:00 1972 -0500 Research V1 development Work on file u5.s Co-Authored-By: Dennis Ritchie <dmr@research.uucp> Synthesized-from: v1/sys [...] commit 4030f8318890a026e065bc8926cebefb71e9d353 Author: Ken Thompson <ken@research.uucp> Date: Thu Aug 30 19:30:25 1973 -0500 Research V3 development Work on file sys/ken/slp.c Synthesized-from: v3 [...] commit c4999ec655319a01e84d9460d84df824006f9e2d Author: Dennis Ritchie <dmr@research.uucp> Date: Thu Aug 30 19:33:01 1973 -0500 Research V3 development Work on file sys/dmr/kl.c Synthesized-from: v3 [...] commit 355c543c6840fa5f37d8daf2e2eaa735ea6daa4a Author: Brian W. Kernighan <bwk@research.uucp> Date: Tue May 13 19:43:47 1975 -0500 Research V6 development Work on file usr/source/rat/r.g Synthesized-from: v6 [...] commit 0ce027f7fb2cf19b7e92d74d3f09eb02e8fea50e Author: S. R. Bourne <srb@research.uucp> Date: Fri Jan 12 02:17:45 1979 -0500 Research V7 development Work on file usr/src/cmd/sh/blok.c Synthesized-from: v7 [...] Author: Eric Schmidt <schmidt@ucbvax.Berkeley.EDU> Date: Sat Jan 5 22:49:18 1980 -0800 BSD 3 development Work on file usr/src/cmd/net/sub.c View changes to a specific file Run git checkout Research-Release git log --follow --simplify-merges usr/src/cmd/c/c00.c to see dates on which the C compiler was modified. Annotate lines in a specific file by their version Run git blame -C -C usr/sys/sys/pipe.c to see how the Unix pipe functionality evolved over the years. 3cc1108b usr/sys/ken/pipe.c (Ken Thompson 1974-11-26 18:13:21 -0500 53) rf->f_flag = FREAD|FPIPE; 3cc1108b usr/sys/ken/pipe.c (Ken Thompson 1974-11-26 18:13:21 -0500 54) rf->f_inode = ip; 3cc1108b usr/sys/ken/pipe.c (Ken Thompson 1974-11-26 18:13:21 -0500 55) ip->i_count = 2; [...] 1f183be2 usr/sys/sys/pipe.c (Ken Thompson 1979-01-10 15:19:35 -0500 122) register struct inode *ip; 1f183be2 usr/sys/sys/pipe.c (Ken Thompson 1979-01-10 15:19:35 -0500 123) 1f183be2 usr/sys/sys/pipe.c (Ken Thompson 1979-01-10 15:19:35 -0500 124) ip = fp->f_inode; 1f183be2 usr/sys/sys/pipe.c (Ken Thompson 1979-01-10 15:19:35 -0500 125) c = u.u_count; 1f183be2 usr/sys/sys/pipe.c (Ken Thompson 1979-01-10 15:19:35 -0500 126) 1f
Read the full README on GitHub

What Hacker News says

13 sources
You haven't proven it wrong. Here's the earliest implementation in that repo (in Research UNIX V6; your link in V7): https://github.com/dspinellis/unix-history-repo/blob/Researc... calloc(n, s) { return(alloc(n*s)); } There are several interesting things we learn from poking around V6 though: - `calloc` originated not on UNIX, but as part of Mike Lesk's "iolib", which was written to make it easier to write C programs portable across PDP 11 UNIX, Honeywell 6000 GCOS, and IBM 370 OS[0]. Presumably the reason calloc is the-way-it-is is hidden in the history of the implementation for GCOS or IBM 370 OS, not UNIX. Unfortunately, I can't seem to track down a copy of Bell Labs "Computing Science Technical Report #31", which seems to be the appropriate reference. - `calloc` predates `malloc`. As you can see, there was a `mall
Read the rest
oc`-like function called just `alloc` (though there were also several other functions named `alloc` that allocated things other than memory). (Ok, fine, since V5 the kernel's internal memory allocator happened to be named `malloc`, but it worked differently[1]). [0]: https://github.com/dspinellis/unix-history-repo/blob/Researc... (format with `nroff -ms usr/doc/iolib/iolib`) [1]: https://github.com/dspinellis/unix-history-repo/blob/Researc...
In Why does calloc exist?
I know they don't want to open source it, but I wonder if they would be amenable to having a volunteer who would help organize and push the code into a version control system hosted on their private server. In an interview I read, Tarn said something to the effect of that "he was not interested in learning about version control and it would just be a distraction that would take away time from the important work, since the way he works has worked for him for many years". I can't help but think that first, it's a bit dangerous way to work, all "past, current and future" state of the project is only in his head and if he happens to become indisposed, the project is very very likely to die (though I suppose there would be hardcore fans willing to reverse engineer it)... Second, it's a loss of historical record... imagine in fifty years histor
Read the rest
ians wanting to analyze the project's history, it would be so much more useful to have a granular history instead of just a blob of files scattered across thousands of directories... Just look at Unix History repository here for example: https://github.com/dspinellis/unix-history-repo - I think there's immense long term value in preserving this kind of archival history.
In Dwarf Fortress Development
I was curious what the oldest reference of it was, https://github.com/dspinellis/unix-history-repo.git has different branches for various unix versions Seems the earliest reference I could find in there was dated november 1973, but it is from a full import in 77: commit c849507974bd2c0e2fd8c17e06f6f65b68075ca9 Author: Bill Joy <wnj@ucbvax.Berkeley.EDU> Date: Wed Nov 23 12:43:50 1977 -0800 Start development on BSD 1 Create reference copy of all prior development files Synthesized-from: 1bsd Some of the earlier copies i can see were even just shell scripts: trap "" 1 15 if test -t 2>&1 ; then echo "Sending output to 'nohup.out'" exec nice -5 $* >>nohup.out 2>&1 else exec nice -5 $* 2>&1 fi Research-V3-Snapshot-Development did not have nohup Research-V4-Snapshot-Development had the nohup man page
Read the rest
but not nohup Research-V5-Snapshot-Development has nohup.c commit 0281f55d1cf7aa94555d8522d8b37161b97791be Author: Ken Thompson <ken@research.uucp> Date: Tue Nov 26 18:13:21 1974 -0500 Research V5 development Work on file usr/source/s2/nohup.c Co-Authored-By: Dennis Ritchie <dmr@research.uucp> Synthesized-from: v5 Then later v7 reverted back to the shell version commit 6144d5b3a973b515977eef01a828cdd82c480fe3 Author: Ken Thompson <ken@research.uucp> Date: Wed Jan 10 15:25:04 1979 -0500 Research V7 development Work on file bin/nohup Co-Authored-By: Dennis Ritchie <dmr@research.uucp> Synthesized-from: v7
In Systemd developer asks tmux to add systemd specific code
You'd be hard pressed to convince me that Windows model for locking files is superior to what Unix offers, at least as far as file deletion goes. Conceptually speaking, it's pretty simple: * Files are blobs of storage on disk referenced by inode number. * Each file can have zero or more directory entries referencing the file. (Additional directory entries are created using hard links.) * Each file can have zero or more open file descriptors. * Each blob has a reference count, and disk space is able to be reclaimed when the reference count goes to zero. Interestingly enough, this means that 'rm' doesn't technically remove a file - what it does is unlink a directory entry. The 'removal' of the file is just what happens when there are no more directory entries to the file and nothing has it open. https://github.com/dspinellis/unix-history-re
Read the rest
po/blob/Researc... In addition to letting you delete files without worrying about closing all the accessing processes, this also lets you do some useful things to help manage file lifecycle. ie: I've used it before in a system where files had to be in an 'online' directory and another directory where they were queued up to be replicated to off-site storage. The system had a directory entry for each use of the file, which avoided the need to keep a bunch of copies around, and deferred the problem of reclaiming disk storage to the file system.
In Server Retired After 18 Years Running on FreeBSD 2.2.1 and a Pentium 200MHZ

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.