From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: [TUHS] Re: Unix v7 icheck dup problem
Date: Wed, 1 Mar 2023 16:29:16 -0500 (EST) [thread overview]
Message-ID: <20230301212916.0583418C07B@mercury.lcs.mit.edu> (raw)
> 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:
http://ana-3.lcs.mit.edu/~jnc/tech/unix/s1/fcheck.c
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 was
in the famous Boy Scout troop at Bell helped... :-)
> From: KenUnix <ken.unix.guy@gmail.com>
> What I finally did was restore the ".disk" files from a previous backup
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.
Noel
next reply other threads:[~2023-03-01 21:29 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 21:29 Noel Chiappa [this message]
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
-- 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
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=20230301212916.0583418C07B@mercury.lcs.mit.edu \
--to=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).