Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!clyde!cbatt!ihnp4!inuxc!pur-ee!j.cc.purdue.edu!h.cc.purdue.edu!pur-phy!mrstve!rjk
From: rjk@mrstve.UUCP (Richard Kuhns)
Newsgroups: comp.sys.att
Subject: No lost+found directory on the 3B1
Message-ID: <541@mrstve.UUCP>
Date: Sun, 16-Nov-86 21:34:20 EST
Article-I.D.: mrstve.541
Posted: Sun Nov 16 21:34:20 1986
Date-Received: Mon, 17-Nov-86 22:27:06 EST
Organization: Mr sTVe's, Lafayette IN
Lines: 26


I've gotten bitten by this, and I haven't seen it mentioned yet, so here
goes:  There is no lost+found directory on a distribution 7300/3B1.

When you boot a 3B1, it automatically runs an `fsck -p'.  If any (severe)
problems are found, it then runs an `fsck -y'.  Well and good, since the
machine is apparently aimed at people who are not familiar with UNIX.
HOWEVER, since there is no lost+found directory, any files which are not
referenced simply vanish, since fsck can't put them in /lost+found.
EXTREMELY annoying.

I can't see any reason for this.  Granted, the (non-technical) user this
machine is aimed at probably wouldn't know how to go about finding
(and fixing/replacing) a file that ended up in /lost+found, but it
wouldn't be too difficult to find someone (at the software Hotline, say)
who would know how to fix it.

My solution?  I created a /lost+found directory (with 25 empty slots).
I then edited /etc/rc so I now have an interactive fsck running when
my machine reboots.  Gives me a much greater feeling of security.

By the way, you can look at /etc/lastfsck if you want to see what
fsck did the last time it found a severe error.  Too late to do anything
about it, but...
-- 
Rich Kuhns		{ihnp4, decvax, etc...}!pur-ee!pur-phy!mrstve!rjk