From: KenUnix <email@example.com>
To: Noel Chiappa <firstname.lastname@example.org>
Subject: [TUHS] Re: Unix v7 icheck dup problem
Date: Wed, 1 Mar 2023 16:54:34 -0500 [thread overview]
Message-ID: <CAJXSPs-oGmhTV8vAwzVKnpYnMrkWZ9MiA7qZXThgt=JTW5+tbA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1450 bytes --]
Downloaded your fsck.c to play with but things are missing:
# cc fsck.c
Is there a makefile?
Yes, I am trying to compile it on Unix v7.
On Wed, Mar 1, 2023 at 4:29 PM Noel Chiappa <email@example.com> wrote:
> > I'm not sure if 'fsck' would fix these
> Turns out it was called 'fcheck' when we had it.
> > I have a V6 one
> I'd already put it on my Web site, here:
> if anyone wants it.
> > From: "Ron Natalie"
> > You had adb?
> Yeah, MIT had a lot of stuff that 'fell off the back of a truck' (including
> things like the circuit design tools, etc). Well, having an undergrad who
> in the famous Boy Scout troop at Bell helped... :-)
> > From: KenUnix <firstname.lastname@example.org>
> > What I finally did was restore the ".disk" files from a previous
> You may sit with Arlo Guthrie on the 'Windows user' bench. :-)
> > From: "Theodore Ts'o"
> > some have argued that if someone doesn't do backups of their research
> > data, maybe they don't *deserve* to get their Ph.D. :-)
> 'Think of it as evolution in action.'
> Although I like the old story about the person at their oral exam and
> the Coke bottle in the window.
End of line
[-- Attachment #2: Type: text/html, Size: 2401 bytes --]
next prev parent reply other threads:[~2023-03-01 21:55 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 21:29 Noel Chiappa
2023-03-01 21:54 ` KenUnix [this message]
2023-03-01 21:55 ` John Cowan
2023-03-01 22:15 ` Jon Forrest
2023-03-02 4:16 ` Jonathan Gray
-- 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-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 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
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).