From owner-freebsd-questions Wed Nov 13 15:54: 5 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6D6B37B401 for ; Wed, 13 Nov 2002 15:54:03 -0800 (PST) Received: from tomts17-srv.bellnexxia.net (tomts17.bellnexxia.net [209.226.175.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id D7A8D43E3B for ; Wed, 13 Nov 2002 15:54:02 -0800 (PST) (envelope-from matt@gsicomp.on.ca) Received: from xena.gsicomp.on.ca ([65.95.184.186]) by tomts17-srv.bellnexxia.net (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with ESMTP id <20021113235402.GYCZ1531.tomts17-srv.bellnexxia.net@xena.gsicomp.on.ca>; Wed, 13 Nov 2002 18:54:02 -0500 Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.3/8.11.3) with SMTP id gADNvJU12019; Wed, 13 Nov 2002 18:57:20 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <020901c28b6f$f0b241c0$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "R. Zoontjens" , References: Subject: Re: restore question Date: Wed, 13 Nov 2002 18:54:00 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > On Wed, 13 Nov 2002, Mark wrote: > > > > > Worse even, how do I safely restore the "/" filesystem? (should it ever > > > become corrupted). > > > > The last time I needed to do that, I booted to the Fixit system > > on CD2 and used the tools there to newfs/restore from backup. > > But what to do if you did your dumps to tape and the fixit disk does not > have the right tapedriver? > one would like to be able to restore the tape-dumps... I've run into a problem like this before. What I ended up doing was just doing a bare-bones network install on the system without newfs'ing the file systems, brought the system up and built a custom kernel with the right drivers, rebooted and then was able to clean up from the mess. > You build a custom boot disk with a custom kernel (Handbook). That's what I > tried. But: the MINI kernel doesn't fit on the disk, and I stripped it > a -lot- :( (my 4.7 MINI kernel is still about 1.2M with ATA-tape drivers) If you post your MINI kernel, I'm sure someone could find something to remove that would save space. Making a general statement, I've seen people trying to make custom boot disks for rescue purposes but keeping things like usb support, smp support, or netgraph stuff around. Although this stuff may normally be in the custom kernel used on the machine, it's usually never neccessary for rescue purposes. -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message