Subject: Re: fixing files after fsck -y
To: None <port-mac68k@netBSD.org>
From: Ken Hughes <hughes@interchange.ubc.ca>
List: port-mac68k
Date: 06/04/2000 22:17:29
Thank you much.
This was all straight 1.4.1 distribution, but I'll do a new install
with 1.4.2.

I was hoping to find out how to go after /lost+found inodes but I guess
that learning experience will have to wait for another day.

Best,
Ken Hughes

On Sun, 4 Jun 2000, T@W wrote:
> Ken Hughes chisseled:
     ...      ^^^      My dictionary and I do not know this word.

> >Hello everyone
> >[snip]I had repeated SCSI trouble during my current install,
> >debug >reboots,etc., and then found 60+ lost+found entries after
> >fsck(s) >(where I gave a "yes" to everything, fixing, adjusting,
> >reconnecting, [snipped]
> >but I would like to fix the following ...
> ># ls -ilF /lost+found
> [snipped rest]
> 
> What version are you using?.
> I recall to have the same problems with 1.4/1.4.1 and using mixed binaries
> and sources. Never really found a solution except for starting from scratch
> after tar-ring up all files I changed/configured (specially /etc) and
> backing  them up (many options possible, but cpout with your installer to
> your Mac disks the easiest).
> Try installing 1.4.2 from scratch and use the stable kernel (no current)
> 
> Does this help?