From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Sun,  6 Aug 1995 12:20:44 -0400
From: forsyth@plan9.cs.york.ac.uk forsyth@plan9.cs.york.ac.uk
Subject: link=3Dvga; broken f.s.
Topicbox-Message-UUID: 1320bd84-eac8-11e9-9e20-41e7f4b1d025
Message-ID: <19950806162044.wPTDmhBZrQ1-Jp2jfHkRy_KO4UdCrT5SWGb6s5ObdJw@z>

>>2) i don't understand the reference to "link=3Dvga", you haven't been fiddling
>>   with aux/vga without a licence have you?

splite@wdni.com's mailer seems to be using = as an escape (3D is `=').

>>Content-Type: text/plain; charset=X-roman8
>>Content-Transfer-Encoding: quoted-printable

anyhow, as far as this goes:

>>prompt.  /tmp/x contains:
>>	tag = Tnone; expected Tfile

that probably signifies a corrupt file system; that looks to me like a
message from disk/kfs (or /fs).

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.)

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.

while it is possible to make the curdled file system consistent again using
the options to disk/kfscmd 'check', it's probably better to unpack the
distribution again into a remade file system.