From: Steven Plite splite@wdni.com
Subject: link=3Dvga; broken f.s.
Date: Mon, 7 Aug 1995 14:30:11 -0400 [thread overview]
Message-ID: <19950807183011.izrgR0PS3gIOwuVdKgyawQIkqmIKzNwiU7S2rWOBUc4@z> (raw)
>>> 2) i don't understand the reference to "link=3D3Dvga", you haven't be=
en
>>> fiddling with aux/vga without a licence have you?
> =
> splite@wdni.com's mailer seems to be using =3D as an escape (3D is `=3D=
').
Yeah. I'm going to build MH this afternoon. HP's mailx has (broken) met=
amail
support. (Hmmm... metamail came from BL too. Coincidence or conspiracy?=
:)
>>>prompt. /tmp/x contains:
>>> tag =3D Tnone; expected Tfile
> =
> that probably signifies a corrupt file system; that looks to me like a
> message from disk/kfs (or /fs).
Ahh... the light of realization dawns.
> it isn't surprising there are problems if the system hung up
> and had to be reset before a disk/kfscmd halt could be done.
> (if it happens again, wait about 30 seconds before resetting
> to give it a chance to sync automatically; normally the f.s. will
> then be consistent.)
I've been wondering how Plan 9 dealt with a corrupted filesystem. I figu=
red
that resetting without halt'ing would screw something, but it never compl=
ained
on boot, so I (wrongly) assumed the fs was okay.
> disk/kfscmd 'check' will show the extent of the damage, but
> the demo. system is small enough that there aren't any optional files;
> something is bound to break later.
"optional files"?
> while it is possible to make the curdled file system consistent again u=
sing
> the options to disk/kfscmd 'check', it's probably better to unpack the
> distribution again into a remade file system.
I'll do that. Thanks.
(Sorry about all the bandwidth. I'm reading the docs as fast as I can, b=
ut
it's hard (for me, anyway) to learn a system without having a working one=
to
play with.)
_________________________________________________________________________=
______
Steven Plite <splite@wdni.com> Open Systems Eng. & Support, Weyerh=
aeuser
"This is the roller coaster of endless and violent vomit." -- Jason F=
ox
next reply other threads:[~1995-08-07 18:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-08-07 18:30 Steven [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-08-08 17:02 Steven
1995-08-08 12:50 presotto
1995-08-07 23:36 Scott
1995-08-06 16:20 forsyth
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=19950807183011.izrgR0PS3gIOwuVdKgyawQIkqmIKzNwiU7S2rWOBUc4@z \
--to=9fans@9fans.net \
/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).