Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site sfsup.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!mhuxm!sftig!sfsup!mjs
From: mjs@sfsup.UUCP (M.J.Shannon)
Newsgroups: net.micro,net.micro.att,net.micro.pc
Subject: Re: Notes on the UNIX-PC
Message-ID: <112@sfsup.UUCP>
Date: Fri, 7-Feb-86 10:42:50 EST
Article-I.D.: sfsup.112
Posted: Fri Feb  7 10:42:50 1986
Date-Received: Tue, 11-Feb-86 04:40:59 EST
References: <1709@ihuxl.UUCP>
Distribution: net
Organization: AT&T Information Systems, Summit N.J.
Lines: 31
Xref: watmath net.micro:13745 net.micro.att:883 net.micro.pc:6882

> 
> There are a couple of problems that I've encountered with the UNIX PC.  One
> concerns fsck.  As the computer comes from the factory, it will not save
> unreferenced files that fsck finds.  The reason for this is there is no
> lost+found directory in the root node.  Also, the install diskettes do not make
> this directory.  They should!!
> 
> Anyone who does not have this directory on their system should do:
> $ mkdir /lost+found

Further, you should also:
	$ cd /lost+found
	$ for i in 1 2 3 4 5 6 7 8
	>>do
	>>	for j in 1 2 3 4 5 6 7 8
	>>	do
	>>		touch ${i}${j}
	>>	done
	>>done
	$ rm *
What this does is allocate real blocks to the directory itself.  Why you need
this is fsck cannot allocate blocks from the filesystem that's damaged.

> If you have more than one filesystem on your hard disk you need to make the
> lost+found directory in the root of each filesystem.

Hope this saves some of your files....

	Marty Shannon
	SF G-213 x6063
	sfsup!mjs