From: Jonathan Gray <jsg@jsg.id.au>
To: Clem Cole <clemc@ccc.com>
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, tuhs@tuhs.org
Subject: [TUHS] Re: Unix v7 icheck dup problem
Date: Sat, 4 Mar 2023 13:45:50 +1100 [thread overview]
Message-ID: <ZAKw3lpStgFLGdEF@largo.jsg.id.au> (raw)
In-Reply-To: <CAC20D2Ow1tp4_0fjHMnEvxu_AyUmB5fGLYobJ6A-JZtT83DKcA@mail.gmail.com>
On Fri, Mar 03, 2023 at 02:35:37PM -0500, Clem Cole wrote:
>
> > Interesting. I wonder how 'fcheck' made it from CMU to Bell?
>
> The late Ted Kowaski - the primary author. Undergrad EE UMICH (Bill Joy's
> roommate) and Grad EE at CMU (and my programming/lab partner originally in
> Dan Sieworick's grad RT course and Gordon Bell System Architecture
> courses). MTS and TSS had a disk scavenger from IBM for their common FS
> [which Ted has used at MICH and I had CMU]. icheck/ncheck/dcheck seemed
> less useful.
> A new program was started when he was an undergrad and never finished.
>
> It had more colorful name originally - fsck (pronounced as fisk BTW) was
> finished. I suspect the fcheck name was a USG idea. The reason why many
> of the error messages are upper case is that was the IBM convention which
> both MTS and TSS used for system programs.
It is difficult to determine when fsck appeared in the USG releases.
fsck was perhaps present in USG Program Generic PG-1C300 Issue 3
(March 1977), as it was in the MERT Release 0 manual:
https://www.tuhs.org/Archive/Documentation/Manuals/MERT_Release_0/Unix%20Programmer%20Manual%20-%20UPM%20-%20White%20Tabs/System%20Programs%20-%20man8/fsck.8.pdf
"I would like to thank Larry A. Wehr for advice that lead to the first
version of fsck and Rick B. Brandt for adapting fsck to UNIX/TS."
T. J. Kowalski, FSCK - The UNIX/TS File System Check Program
included in System III manuals
'Credit for the various pieces involved goes to Ted Kowalski of CMU and
BTL, Mike Accetta of CMU, and George Goble of Purdue Univ. Kowalski
wrote the "fsck," file system check program, which does all that
icheck/dcheck did and more and also repairs errors that it finds. In the
Purdue V6 system Goble had added code to ensure that inodes and indirect
blocks on disk were always in a consistent state so that the worst that
could happen in a sudden halt or crash was that the file system may have
some dups in free, but never dups between files. Accetta enhanced these
and added a few of his own.
In the current Berkeley distribution (4BSD) all of these techniques are
provided as well as some additions.'
Bill Joy, A Crash-resistant UNIX file system
https://archive.org/details/login_january-1981/page/30/mode/2up
next prev parent reply other threads:[~2023-03-04 2:46 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2023-03-03 23:00 ` Jonathan Gray
2023-03-04 9:07 ` Jonathan Gray
2023-03-04 11:19 ` 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-04 14:41 Noel Chiappa
2023-03-04 14:49 ` 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:
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=ZAKw3lpStgFLGdEF@largo.jsg.id.au \
--to=jsg@jsg.id.au \
--cc=clemc@ccc.com \
--cc=jnc@mercury.lcs.mit.edu \
--cc=tuhs@tuhs.org \
/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).