From owner-freebsd-current  Fri Mar 29 15:11:10 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id PAA29025
          for current-outgoing; Fri, 29 Mar 1996 15:11:10 -0800 (PST)
Received: from sxt2.space.lockheed.com (sxt2.space.lockheed.com [192.68.162.109])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA29013
          for <freebsd-current@freebsd.org>; Fri, 29 Mar 1996 15:11:07 -0800 (PST)
Received: by sxt2.space.lockheed.com (5.65/DEC-Ultrix/4.3)
	id AA18765; Fri, 29 Mar 1996 15:05:25 -0800
Date: Fri, 29 Mar 1996 15:05:24 -0800 (PST)
From: "Brian N. Handy" <handy@sxt2.space.lockheed.com>
To: freebsd-current@freebsd.org
Subject: Fixit Floppy Broken?
Message-Id: <Pine.ULT.3.91.960329150032.18461A-100000@sxt2.space.lockheed.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hi again,

I have a broken 2.2-960323-SNAP machine right now.  The owner managed to 
delete libc.so.3.0 from /usr/lib so things quickly deteriorated to where 
his machine wasn't working anymore!  

I had hoped we could fix this with the fixit floppy, but I'm having bad 
luck with these.  The fixit floppy seems broken.  I can boot from it 
once, but never really get anywhere.  If I try booting with it again it 
doesn't work.

I complained earlier about 'ls' not working on the floppy drive...but I 
haven't heard anything back on this.  Anyway, I think my only alternative 
is to use the boot floppy to do a custom sysinstall and re-install the 
libraries.  

Bottom line:  IS the fixit floppy currently broken, and is this probably 
the best way for me to fix this problem?

Thanks,

Brian