From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] worm problems
Date: Sun, 9 Dec 2001 12:45:15 -0500 [thread overview]
Message-ID: <20011209174516.78F5E199D5@mail.cse.psu.edu> (raw)
Can you boot a Plan 9 terminal on the disk
(or boot the install floppy) and then look
at the second block on your pseudo-worm?
Also, backups are good.
I had a problem like this once right after I'd
set up a pseudo-worm and other partition on the
same disk using the p device. I never tracked
it down, but my superblock was the beginning of
a PostScript file. The case fan had broken, so
I think it might have just been heat problems.
Russ
next reply other threads:[~2001-12-09 17:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-09 17:45 Russ Cox [this message]
2001-12-09 19:44 ` Sam Ducksworth
-- strict thread matches above, loose matches on Subject: below --
2001-12-09 22:03 Russ Cox
2001-12-09 23:52 ` Sam Ducksworth
2001-12-09 13:47 Sam Ducksworth
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=20011209174516.78F5E199D5@mail.cse.psu.edu \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).