from localhost (localhost [127.0.0.1])
	by phobos.labs.netnoteinc.com (Postfix) with ESMTP id BC1024410E
	for <jm@localhost>; Wed, 31 Jul 2002 13:33:20 -0400 (EDT)
from lugh.tuatha.org (root@lugh.tuatha.org [194.125.145.45]) by
    dogma.slashnull.org (8.11.6/8.11.6) with ESMTP id g6VHZD203399 for
    <jm-ilug@jmason.org>; Wed, 31 Jul 2002 18:35:13 +0100
from lugh (root@localhost [127.0.0.1]) by lugh.tuatha.org
    (8.9.3/8.9.3) with ESMTP id SAA19781; Wed, 31 Jul 2002 18:32:47 +0100
from dialup138-b.ts551.cwt.esat.net ([193.203.141.138]
    helo=Hobbiton.cod.ie) by mail2.mail.iol.ie with esmtp (Exim 3.35 #1) id
    17ZxE1-0000ZA-00; Wed, 31 Jul 2002 18:25:29 +0100
ilug@linux.ie, Niall O Broin <niall@linux.ie>
From ilug-admin@linux.ie  Wed Jul 31 18:34:00 2002

On Tue, Jul 30, 2002 at 03:47:40PM +0100 or so it is rumoured hereabouts,
> So, in the event of finger slips we can mount the relevant partition and
> retrieve the banjaxed file. In the case of a disk crash, the plan is that
> we'll put the standby disk in place of the main disk and the workstation
> will be back up ASAP. Then we can deal with replacing the disk without the
> However, I'm stumped as to how to install LILO on the backup disk. Let's say
> the master disk is /dev/hda and the backup disk is /dev/hdb. lilo.conf
> There are a couple more boot stanzas, but they're not germane. As you can
> see, / is on /dev/hda3 and /boot is on /dev/hda1. So if for instance I had
> booted from a CD and wanted to re-install LILO on this disk I'd do something
> which is OK because I'm installing lilo on /dev/hda and I want it to boot
> from /dev/hda so it'll plug in all the right numbers.
> However, in the case of the standby disk, I'll have to do something like
> But I'm obviously going to have to do something different here because I
> want to install onto /dev/hdb in such a way that the disk will boot when it
> becomes /dev/hda after a disaster (like the one I had this morning :-( -
> shutting the stable door was on the to-do list, but the bloody horse decided
> to do a bunk early). The machine already has its spare disk - just hadn't
> I thought perhaps I should just do   lilo -b /dev/hdb -r /mnt  but I think
> that -b is analogous to the boot keyword in lilo.conf. Or will this just
> work automagically ?  i.e. boot = /dev/hda tells lilo what numbers to poke
> where, and it figures out where the disk is from the -r ?
(Thanks to Rick Masters for helping with this.)
We're  assuming  that LILO is installed on the hard disk's Master Boot
Record (MBR); this seems to be the most common configuration. You want
to  install  LILO  on  what's  presently the second hard disk but will
Edit the file /new-disk/etc/lilo.conf as follows:
disk=/dev/hdb bios=0x80       # Tell LILO to treat the second
boot=/dev/hdb                 # Install LILO on second hard
map=/new-disk/boot/map        # Location of "map file".
install=/new-disk/boot/boot.b # File to copy to hard disk's
prompt                        # Have LILO show "LILO boot:"
timeout=50                    # Boot default system after 5
image=/new-disk/boot/vmlinuz  # Location of Linux kernel. The
label=linux               # Label for Linux system.
root=/dev/hda1            # Location of root partition on
read-only                 # Mount partition read-only at