Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!ux1.cso.uiuc.edu!howland.reston.ans.net!noc.near.net!uunet!math.fu-berlin.de!uni-paderborn.de!urmel.informatik.rwth-aachen.de!acds.physik.rwth-aachen.de!kuku From: kuku@acds.physik.rwth-aachen.de (Christoph Kukulies) Newsgroups: comp.os.386bsd.bugs Subject: accesing rfd0a bombs (386bsd w 0.2.4) Date: 28 Jun 1993 18:21:28 GMT Organization: I.Physikalisches Institut RWTH-Aachen Lines: 23 Distribution: world Message-ID: <20ncr8$nb9@urmel.informatik.rwth-aachen.de> Reply-To: kuku@acds.physik.rwth-aachen.de NNTP-Posting-Host: acds.physik.rwth-aachen.de Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 486/33 16MB, AH1542A (!) 2GB Seagate, 660 MB CDC Wren6, DAT Tape TLZ04 (DEC), 5.25", 3.5" FD, XFree86 server running. Two xterms open. 386bsd + 0.2.3 + 0.2.4 (BTW, how do we write that in the future - just as long 386bsd-0.2 isn't out yet ? :-) 386bsd-0.2.4 ? Booted with fd inserted - folks, is this quirk still in the floppy code, that when you boot a system with floppy inserted and door open, afterwards the floppy is not recognized by the autoconfigure code?. I had this fixed with an extra long DELAY in fd_probe, I also posted it last year in October but why do my posts not find their way into the patchkits? Is there a special way you have to post fixes? bugfiler? GNATS? Anyway, once again, I inadvertently left a disk in the 5.25 drive, booted, the disk was not recognized. Later - meanwhile forgotten about that fact - I wanted to access the drive (either mount or tar - don't remember) - SOFT RESET, black screen, reboot, no panic message, just as if someone has hit the reset button. -- --Chris Christoph P. U. Kukulies kuku@acds.physik.rwth-aachen.de *** Error code 1 Stop.