The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: reed@reedmedia.net (Jeremy C. Reed)
Subject: [TUHS] Questions regarding early Unix contributors
Date: Thu, 24 Sep 2015 14:04:03 -0500 (CDT)	[thread overview]
Message-ID: <alpine.NEB.2.11.1509241333120.27255@t1.m.reedmedia.net> (raw)
In-Reply-To: <CAC20D2N5dEQit0pz-X-rjUo-AA-j5Ef=4mRPYXssFH98J00hcw@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]

On Thu, 24 Sep 2015, Clem Cole wrote:

>    I believe he gave a copy of the sources very early to wnj -- which is how
> it ended up in 4.1BSD.  I don't think it was in the original 3.0 or 4.0
> packages as it was not in V5, V6 or V7 either.  I believe it was released in
> PWB 2.0 - not sure and Minnie does not seem to have them.

Yes, it is in 4.0BSD (the copy I have has it documented in the setup.t 
from Nov. 15, 1980, fsck.mm from Oct. 15, 1980). It appears to be the 
same code as in 4.1 also.

(But I cannot find 4.0 in Diomidis's git repo. I also don't have the 
original SCCS data from the early fsck, probably because it got moved 
and extended in different location.)

By the way, I see the .8 manual for it got a Regents copyright placed on 
it between 4.2 and 4.3 (even though contained lots of original text as 
in 4.0BSD). The extensive rewrite to the fsck code happening between 4.1 
and 4.3. fsck.c split up into main.c and others in August 1981, even 
though 4.2 a later year still shipped fsck.c and not the new code.

(Reminds me I need to listen to video from McKusick about history of 
ffs again.)

"the calm before the storm ... the storm ... the Coast Guard to the 
rescue" (from the fsck document)


  parent reply	other threads:[~2015-09-24 19:04 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24 14:08 Clem Cole
2015-09-24 15:20 ` Mary Ann Horton
2015-09-24 17:08   ` Jeremy C. Reed
2015-09-24 17:28   ` Clem Cole
2015-09-26  2:37     ` Dave Horsfall
2015-09-26 23:22       ` Clement T. Cole
2015-09-27  6:52     ` Armando Stettner
2015-09-27 17:31       ` Clem Cole
2015-09-28 14:59       ` Dave Horsfall
2015-09-28 16:55         ` scj
2015-09-28 23:23           ` Greg 'groggy' Lehey
2015-10-01  2:09             ` Dave Horsfall
2015-10-01  3:52               ` Greg 'groggy' Lehey
2015-10-01  4:51                 ` Dave Horsfall
2015-09-29  6:57           ` arnold
2015-09-24 19:04 ` Jeremy C. Reed [this message]
2015-09-24 20:13   ` Clem Cole
2015-09-24 20:16     ` Clem Cole
2015-09-25  8:04   ` Diomidis Spinellis
2015-09-25 12:04   ` Clem Cole
  -- strict thread matches above, loose matches on Subject: below --
2015-10-07 13:26 Nelson H. F. Beebe
2015-10-02 18:00 Nelson H. F. Beebe
2015-10-01 16:37 Norman Wilson
2015-10-01 18:57 ` Dave Horsfall
2015-09-29  8:07 Hellwig Geisse
2015-09-29 15:35 ` scj
2015-10-01 18:00   ` Aharon Robbins
2015-09-25  2:14 Doug McIlroy
2015-09-24 17:12 Norman Wilson
2015-09-24 20:07 ` scj
2015-09-24 13:56 Noel Chiappa
2015-09-24 14:38 ` Lawrence Stewart
2015-09-24  9:27 Diomidis Spinellis
2015-09-24  9:52 ` Warren Toomey
2015-09-24 12:59 ` Clem Cole
2015-09-24 13:27 ` arnold
2015-09-24 16:12 ` John Cowan
2015-09-24 17:58 ` Jeremy C. Reed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.NEB.2.11.1509241333120.27255@t1.m.reedmedia.net \
    --to=reed@reedmedia.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).