The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: (Noel Chiappa)
Subject: [TUHS] Re: Unix v7 icheck dup problem
Date: Sat,  4 Mar 2023 09:41:34 -0500 (EST)	[thread overview]
Message-ID: <> (raw)

    > From: Clem Cole wrote:

    > It had more colorful name originally - fsck (pronounced as fisk BTW)
    > was finished. I suspect the fcheck name was a USG idea. 

I dunno. I don't think we at MIT wold have gratuitously changed the name to
'fcheck'; I rather think that was its original name - and we pretty
definitely got it from CMU. 'fsck' was definitely descended from 'fcheck'

    > From: Jonathan Gray

    >> (are 'fsck' and 'fcheck' the same program?)


Having looked the the source to both, it's quite clear that 'fcheck' is a
distant ancestor of 'fsck' (see below for thoughts on the connection(s)). The
latter has been _very_ extensively modified, but there are still some traces
of 'fcheck' left.

A lot of the changes are to increase the portability, and also to come into
compliance with the latest 'C' (e.g. function prototypes); others are just to
get rid of oddities in the original coding style. E.g.:


Perfectly legal C, but nobody uses that style.

    > From: Jonathan Gray

    > fcheck is from Hal Pierson at Bell according to

Hmm. "the major features that were added to UNIX by CB/UNIX ... Hal Person
(or Pierson?) also rewrote the original check disk command into something
that was useful by someone other than researchers."

I poked around in CB/UNIX, and found 'check(1M)':

(dated November 1979). Alas, the source isn't there, but it's clearly in the
fheck/fsck family. (CB/UNIX also has chkold(1M), which looks to me like it's

So now we have a question about the ancestry of 'check' and 'fcheck' - is one
an ancestor of the other, and if so, which - or are they independent
creations? Without the source, it's hard to be definitive, bur from the
messages (as given in the manual), they do seem related.

Clem's message of 3 Mar, 14:35 seems to indicate the the original was from
CMU, authored by Ted Kowalski; he also:

says "Ted Kowalski shows up for his OYOC year in the EE dept after his summer
at Bell Labs ... He also brought his cool (but unfinished) program he had
started to write originally at U Mich - fsck". So maybe the CB/UNIX 'check' is
descended from a version that Ted left behind at Bell Labs?

Is anyone in touch with Hal Pierson? He could surely clear up these questions.


             reply	other threads:[~2023-03-04 14:41 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-04 14:41 Noel Chiappa [this message]
2023-03-04 14:49 ` KenUnix
  -- strict thread matches above, loose matches on Subject: below --
2023-03-06  8:14 Noel Chiappa
2023-03-06  8:58 ` Jonathan Gray
2023-03-07  2:05   ` Kenneth Goodwin
2023-03-03 18:22 Noel Chiappa
2023-03-03 19:25 ` Chet Ramey
2023-03-03 21:26   ` John Cowan
2023-03-04  0:23     ` Chet Ramey
2023-03-03 19:35 ` Clem Cole
2023-03-04  2:45   ` Jonathan Gray
2023-03-03 23:00 ` Jonathan Gray
2023-03-04  9:07 ` Jonathan Gray
2023-03-04 11:19   ` KenUnix
2023-03-02  1:59 Noel Chiappa
2023-03-02  2:11 ` Dan Cross
2023-03-02  1:36 Noel Chiappa
2023-03-02  1:56 ` John Cowan
2023-03-02  6:41   ` Lars Brinkhoff
2023-03-02  2:12 ` Bakul Shah
2023-03-02  2:46   ` Rich Salz
2023-03-01 21:29 Noel Chiappa
2023-03-01 21:54 ` KenUnix
2023-03-01 21:55 ` John Cowan
2023-03-01 22:15 ` Jon Forrest
2023-03-02  4:16 ` Jonathan Gray
2023-03-01 15:09 Noel Chiappa
2023-03-01 16:18 ` Ron Natalie
2023-03-01 16:45   ` KenUnix
2023-03-01 16:57 ` Theodore Ts'o
2023-03-01 20:52 ` Dave Horsfall
2023-03-02  1:46   ` Jonathan Gray
2023-03-02  3:05     ` Dave Horsfall
2023-03-02  7:56       ` John Cowan
2023-03-02  8:53         ` Steve Nickolas
2023-03-02  8:01       ` Jonathan Gray
2023-03-02  7:34   ` arnold

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:

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

  git send-email \ \ \ \

* 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).