Gee, now that you've jogged my memory (it takes a few slaps
       up-side the head now and again) I seem to remember you can do
       the same with the RedHat rescue disk.  You give it the command
       "linux root=/dev/hda?" at the boot prompt.  Personally, I've
       just taken to making copies of the boot sector with "dd
       if=/dev/hda of=/dev/fd0 bs=512 count=1".  You just pop in the
       floppy if something goes wrong and usually your right back in.
       I keep an "emergency" LILO boot for my current kernel (it saved
       me hours a few hours a couple of months ago when my boot sector
       mysteriously got corrupted) as well as a couple older LILOs for
       accessing old kernels when I upgrade.  You can do the same to
       save off DOS/WinNT boot sectors during a new installation of
       Linux by switching VTs soon as the install boot image has
       loaded.

       Adrian




       From: [EMAIL PROTECTED] AT mime on 01/25/2000 01:17 AM PST

       To:   [EMAIL PROTECTED] AT mime@CCMAIL
       cc:    (bcc: Adrian D Jensen/RWS/Raytheon/US)

       Subject:  Re: Boot Record





       On Sun, 23 Jan 2000, [EMAIL PROTECTED] wrote:
       >
       >              The real question now is "Do you want to restore
        the original
       >              linux installation?"  Given the condition the
       Linux partition
       >              is probably in now, this is definately beyond
       the scope of a
       >              novice and several emails (and probably a few
       experts too.)
       >              Simply reinstalling DOS or something else
       probably won't work
       >              since it is the LILO boot loader that needs to
       be removed.
       >              Your best bet is to except your Linux loss and
       run the DOS
       >              command (from the good drive on the bad) "fdisk
       /mbr".  This
       >              rewrites the master boot record (block 0) with a
        standard DOS
       >              boot loader (load the first partition marked
       bootable).  From
       >              here your installation of DOS or OS/2 on the bad
        drive should
       >              work.  Alternatively you could just reinstall
       Linux from
       >              scratch on the bad drive, at the end of the
       installation it
       >              will write a new LILO to the master boot record.

        I have one other suggestion to offer, which I use every time I
       have to reinstall Windows (every six months or so). If you
       download a suse boot disk image, write it on an msdos formatted
       disk, and boot from it, thwere is an option under "Start
       Installation" to "Boot installed system". You have to specify
       the root partition, and it runs INIT, on the kernel already
       loaded from the floppy. That gets you in to what's left of your
       system. The rest is up to you ;-). Typing "lilo" will restore
       the boot record. If more than that is gone, you're on your own.

       Try under www.suse.de or www.suse.com



       --
                 Regards,

                 Declan Moriarty




       RFC-822-headers:
       Received: from CONVERSION-DAEMON by west.raytheon.com (PMDF
       V5.1-12 #D3246)
        id <[EMAIL PROTECTED]> for
        "adrian d jensen"@mime.west.raytheon.com; Tue, 25 Jan 2000
       10:49:04 -0800 (PST) Received: from PROCESS-DAEMON by
       west.raytheon.com (PMDF V5.1-12 #D3246)
        id <[EMAIL PROTECTED]> for
        "adrian d jensen"@mime.west.raytheon.com; Tue, 25 Jan 2000
        10:49:01 -0800 (PST)
       Received: from fw-ra05.ext.raytheon.com by west.raytheon.com
        (PMDF V5.1-12 #D3246) with ESMTP id
        <[EMAIL PROTECTED]> for "adrian d jensen"
        @mime.west.raytheon.com; Tue, 25 Jan 2000 10:48:59 -0800 (PST)
       Received: from nic.funet.fi ([193.166.0.145]) by
        fw-ra05.ext.raytheon.com (8.9.1/8.9.1) with ESMTP id BAA24494
        for <[EMAIL PROTECTED]>; Tue,
        25 Jan 2000 01:37:53 -0800 (PST)
       Received: from vger.rutgers.edu
        ([128.6.190.2]:23235 "EHLO vger.rutgers.edu" ident:
        "NO-IDENT-SERVICE[2]" smtp-auth: <none> TLS-CIPHER: <none>) by
        nic.funet.fi with ESMTP id
        <S3853AbQAYJft>; Tue, 25 Jan 2000 11:35:49 +0200
       Received: by vger.rutgers.edu via listexpand id
       <S153856AbQAYF3x>; Tue,
        25 Jan 2000 00:29:53 -0500
       Received: by vger.rutgers.edu id <S153851AbQAYF3n>; Tue,
        25 Jan 2000 00:29:43 -0500
       Received: from wonka.esatclear.ie
        ([194.145.128.5]:2591 "EHLO wonka.esatclear.ie")
        by vger.rutgers.edu with ESMTP id <S153872AbQAYF3e>; Tue,
        25 Jan 2000 00:29:34 -0500
       Received: from workhorse ([EMAIL PROTECTED]
        [194.145.134.112]) by wonka.esatclear.ie (8.9.3/8.9.3) with
        SMTP id JAA14216 for <[EMAIL PROTECTED]>; Tue, 25
        Jan 2000 09:34:30 +0000 (GMT)
       Date: Tue, 25 Jan 2000 09:17:18 +0000
       From: Declan Moriarty <[EMAIL PROTECTED]>
       Subject: Re: Boot Record
       Sender: [EMAIL PROTECTED]
       Message-id: <00012509195002.00182@workhorse>
       MIME-version: 1.0
       X-Mailer: KMail [version 1.0.17]
       Content-transfer-encoding: 7BIT
       Precedence: bulk
       X-Loop: [EMAIL PROTECTED]
       X-Orcpt: rfc822;linux-laptop-outgoing






Reply via email to