Path: utzoo!utgpu!watserv1!watmath!att!att!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!samsung!uunet!virtech!cpcahil
From: cpcahil@virtech.uucp (Conor P. Cahill)
Newsgroups: comp.unix.sysv386
Subject: Re: corrupt floppy driver?
Message-ID: <1990Nov22.125742.484@virtech.uucp>
Date: 22 Nov 90 12:57:42 GMT
References: <1990Nov20.160931.22784@mercury.cair.du.edu>
Reply-To: cpcahil@virtech.UUCP (Conor P. Cahill)
Organization: Virtual Technologies Inc., Sterling VA
Lines: 23

In article <1990Nov20.160931.22784@mercury.cair.du.edu> tjreynol@zephyr.cair.du.edu (Tim) writes:
>We have reason to believe our floopy driver is bogus.

What are the reasons?  I tend to doubt that you really have a floppy
driver problem and without an explanation I couldn't tell you what the 
problem might be.

>can some one using Interactive Unix 2.2 send me a copy of
>/dev/rdsk/f1q15dt

First off, that would be a violation of ISCs copyright, but disregarding 
that, the /dev entry is not the floppy driver.  The floppy driver is in an
entry under /etc/conf/pack.d and if one of those portions of you system is
corrupted, then you should treat the entire installation as corrupted and
restore from backup.

If you think that your kernel has taken a hit, rebuild it.  If the floppy
driver is really trashed, your rebuild will *probably* fail.

-- 
Conor P. Cahill            (703)430-9247        Virtual Technologies, Inc.,
uunet!virtech!cpcahil                           46030 Manekin Plaza, Suite 160
                                                Sterling, VA 22170