I've assembled some notes from old manuals and other sources
on the formats used for on-disk file systems through the
Additional notes, comments on style, and whatnot are welcome.
(It may be sensible to send anything in the last two categories
directly to me, rather than to the whole list.)
Just cuz of this list and recent comments about SVRx and I see this comment in ftrap.s
fpreent: # this is the point we return to
# when we are executing the n+1th
# floating point instruction in a
# contiguous sequence of floating
# point instructions (floating
# pointlessly forever?)
Makes me wonder how many other humorous comments are buried in the code.
Oh, if no one out there has a SVR3.1 distribution (apparently for the 3b2), I’ve got one to send out….
Since early 2013 I've occasionally asked this list for help, and shared
the progress regarding the creation of a Unix Git repository containing
Unix releases from the 1970s until today .
On Saturday I presented this work [2, 3] at MSR '15: The 12th Working
Conference on Mining Software Repositories, and on Sunday I discussed
the work with the participants over a poster  (complete with commits
shown in a teletype (lcase) and a VT-220 font). Amazingly, the work
received the conference's "Best Data Showcase Award", for which I'm
obviously very happy.
I'd like to thank again the many individuals who contributed to the
effort. Brian W. Kernighan, Doug McIlroy, and Arnold D. Robbins helped
with Bell Labs login identifiers. Clem Cole, Era Eriksson, Mary Ann
Horton, Kirk McKusick, Jeremy C. Reed, Ingo Schwarze, and Anatole Shaw
helped with BSD login identifiers. The BSD SCCS import code is based on
work by H. Merijn Brand and Jonathan Gray.
A lot of work remains to be done. Given that the build process is
shared as open source code, it is easy to contribute additions and fixes
through GitHub pull requests on the build software repository , but
if you feel uncomfortable with that, just send me email. The most useful
community contribution would be to increase the coverage of imported
snapshot files that are attributed to a specific author. Currently,
about 90 thousand files (out of a total of 160 thousand) are getting
assigned an author through a default rule. Similarly, there are about
250 authors (primarily early FreeBSD ones) for which only the identifier
is known. Both are listed in the build repository's unmatched directory
, and contributions are welcomed (start with early editions; I can
propagate from there). Most importantly, more branches of open source
systems can be added, such as NetBSD OpenBSD, DragonFlyBSD, and illumos.
Ideally, current right holders of other important historical Unix
releases, such as System III, System V, NeXTSTEP, and SunOS, will
release their systems under a license that would allow their
incorporation into this repository. If you know people who can help in
this, please nudge them.
All, I finally remembered to export the unix-jun72 project over to Github:
This was our effort to bring the 1st Edition Unix kernel back to life
along with the early C compilers and the 2nd Edition userland binaries.
> On Thu, May 21, 2015 at 11:49 AM, Clem Cole <clemc(a)ccc.com <mailto:email@example.com>
> <mailto:firstname.lastname@example.org <mailto:email@example.com>>> wrote:
> ? HP/UX is an SVR3 & OSF/1 ancester. Solaris is SVR4. In fact
> it was the SVR4 license and deal between Sun and AT&T)? that
> forced the whole OSF creation. One of the "principles" of the
> OSF was "Fair and Stable" license terms.
> Which begs a question - since Solaris was SVR4 based and was
> made freely available via OpenSolaris et al, does that not
> make SVR4 open? I'm not a lawyer (nor play one on TV), but
> it does seem like that sets some sort of precedent.
This is indeed an interesting question. During the IBM vs SCO debacle,
IBM requested the use of TMGE to be used as an example for proof of
how the SVR4 kernel algorithms were already out in the public domain
and thus set the precedent. And this was also (eventually) approved by
AT&T for publication.
> From: Mary Ann Horton
> I have 5 AT&T SVR4 tapes among them .. Is it worth recovering them?
I would say that unless they are _known_ to be in a repository somewhere, yes
(unless it's going to cost a fortune - SVR4 isn't _that_ key a step in the
evolution, I don't think [but I stand to be corrected :-]).
A fantastic curatorial exploit!
> Deadly quote "and nobody cares about that early code history any more
> --so this is all water under the bridge."
This particular metaphor always reminds me of the Farberism: "That's
water over the bridge." Dave, a major presence at Bell Labs, master
malaprop, friend of many and collaborator with several of the early
Unix team, may be counted as an honorary Unixian.