From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Illumos )
Date: Wed, 7 Jan 2015 11:26:24 -0500 [thread overview]
Message-ID: <CAC20D2Oc5SKecCwOaNh-JugE7k_a=KrvoE2RC2hywhqObTQPKA@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.11.1501071248120.58880@aneurin.horsfall.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 544 bytes --]
On Tue, Jan 6, 2015 at 8:53 PM, Dave Horsfall <dave at horsfall.org> wrote:
> Somewhere, deep in Minnie's bowels, is the article I wrote, explaining
> exactly how to use icheck/ncheck/dcheck/clri etc.
>
Shows I am old - it would fun to read that again. I never saw the
article, I learned from doing it (wrong probably) a few times ;-)
Then Ted gives us fsck . . .
Clem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20150107/35139e59/attachment.html>
next prev parent reply other threads:[~2015-01-07 16:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-31 6:22 Larry McVoy
2014-12-31 9:28 ` Wesley Parish
2014-12-31 13:13 ` John Cowan
2014-12-31 17:42 ` Diomidis Spinellis
2014-12-31 20:32 ` Clem Cole
2014-12-31 20:36 ` Larry McVoy
2014-12-31 22:19 ` Jacob Ritorto
2014-12-31 22:42 ` Larry McVoy
2014-12-31 22:50 ` Larry McVoy
2015-01-01 1:17 ` Larry McVoy
2015-01-01 1:34 ` Erik E. Fair
2015-01-05 12:02 ` Tim Bradshaw
2015-01-05 17:04 ` Jacob Ritorto
2015-01-06 4:54 ` Andy Kosela
2015-01-06 11:10 ` Kurt H Maier
2015-01-06 15:37 ` Tim Bradshaw
2015-01-09 9:23 ` Jose R. Valverde
2015-01-06 21:58 ` Clem Cole
2015-01-06 22:02 ` [TUHS] pre-FSCK days Ronald Natalie
2015-01-07 1:53 ` [TUHS] Illumos ) Dave Horsfall
2015-01-07 16:26 ` Clem Cole [this message]
2015-01-07 18:32 ` scj
2015-01-16 8:40 ` [TUHS] sync; sync; sync; halt (was: Re: Illumos )) Tom Ivar Helbekkmo
2015-01-16 13:39 ` random832
2015-01-16 14:14 ` Brantley Coile
2014-12-31 9:46 ` [TUHS] Illumos ) 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='CAC20D2Oc5SKecCwOaNh-JugE7k_a=KrvoE2RC2hywhqObTQPKA@mail.gmail.com' \
--to=clemc@ccc.com \
/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).