From: dave@horsfall.org (Dave Horsfall)
Subject: [TUHS] Claim your early Unix contributions on GitHub
Date: Sat, 2 Apr 2016 00:06:35 +1100 (EST) [thread overview]
Message-ID: <alpine.BSF.2.11.1604012352490.76221@aneurin.horsfall.org> (raw)
In-Reply-To: <CAC20D2MWhZczOAd-pCTTOspTejyvTYEwRm+Sd_XTd_62aTuBpg@mail.gmail.com>
On Thu, 31 Mar 2016, Clem Cole wrote:
> The original FS tools for UNIX icheck/dcheck/ncheck were very crude.
I guess I should mention that somewhere in the AUUGN archives is a paper I
wrote on the proper use of these tools (after having seen, and made, too
many mistakes), along with the tool-of-last-resort "clri".
FSCK is a wonderful program, and has saved my bacon many times.
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
next prev parent reply other threads:[~2016-04-01 13:06 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 7:53 Diomidis Spinellis
2016-03-30 12:31 ` Joerg Schilling
2016-03-30 13:10 ` Diomidis Spinellis
2016-03-30 13:44 ` Joerg Schilling
2016-03-30 19:17 ` Larry McVoy
2016-03-30 21:07 ` Random832
2016-03-30 23:03 ` Joerg Schilling
2016-03-31 3:20 ` Larry McVoy
2016-03-31 3:34 ` Random832
2016-03-31 3:40 ` Larry McVoy
2016-03-30 23:42 ` Joerg Schilling
2016-03-31 3:54 ` Larry McVoy
2016-03-30 14:25 ` Marc Rochkind
2016-03-30 15:23 ` Joerg Schilling
2016-03-30 19:14 ` Larry McVoy
2016-03-30 15:49 ` Diomidis Spinellis
2016-03-30 16:07 ` Joerg Schilling
2016-03-30 16:29 ` Diomidis Spinellis
2016-03-30 16:14 ` Pat Barron
2016-03-31 21:06 ` Clem Cole
2016-03-31 21:54 ` Ron Natalie
2016-04-01 9:01 ` Diomidis Spinellis
2016-04-01 14:41 ` Clem Cole
2016-04-01 21:00 ` Jeremy C. Reed
2016-04-01 13:06 ` Dave Horsfall [this message]
2016-04-01 21:52 ` Pat Barron
2016-03-30 16:30 ` Marc Rochkind
2016-03-30 16:40 ` Joerg Schilling
2016-03-30 16:55 ` John Cowan
2016-03-30 18:28 Norman Wilson
2016-03-30 20:06 ` Ronald Natalie
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.BSF.2.11.1604012352490.76221@aneurin.horsfall.org \
--to=dave@horsfall.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).