From owner-freebsd-current Wed Mar 8 07:17:54 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA03050 for current-outgoing; Wed, 8 Mar 1995 07:17:54 -0800 Received: from ns1.win.net (ns1.win.net [204.215.209.3]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA02975; Wed, 8 Mar 1995 07:15:09 -0800 Received: (from bugs@localhost) by ns1.win.net (8.6.9/8.6.9) id KAA11626; Wed, 8 Mar 1995 10:16:04 -0500 From: Mark Hittinger Message-Id: <199503081516.KAA11626@ns1.win.net> Subject: Re: Repair floppies - what should we have? (fwd) To: current@FreeBSD.org, hackers@FreeBSD.org Date: Wed, 8 Mar 1995 10:16:03 -0500 (EST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 814 Sender: current-owner@FreeBSD.org Precedence: bulk > > Remounting of a different floppy on the same drive doesn't work, so the > prompt would have to be given before mounting root. > On another platform that had two floppies I was able to construct a recovery floppy pair. One had the kernel, /dev, and enough to mount the other floppy. The second floppy had the other goodies. > > >Anybody else got ideas? And, how do I persuade something to boot a kernel off > >one floppy and prompt me to insert a root fs? > How about a RAM disk technique? I've used this before on other platforms. Everything could be loaded onto a RAM disk from multiple floppies prior to setting root device. Then you could play WITHOUT the slow floppy access times. This would also be good for making a solid backup of your root partition. Regards, Mark Hittinger bugs@win.net