You should duplicate the sections as Rob mentioned, but instead of
adding multiple dasd=, you'll need to use multiple initrd images based
on different values in modprobe.conf. For example,
1) edit /etc/modprobe.conf for the original dasd range:
options dasd_mod dasd=xxx,xxx-xxx
2) generate an initrd with:
# mkinitrd -v /boot/initrd-primary-`uname -r`.img `uname -r`
(note, you can probably skip the first 2 steps since this is identical
to what you have in /boot already)
3) edit /etc/modprobe.conf for the second dasd range:
options dasd_mod dasd=yyy,yyy-yyy
4) generate an initrd with:
# mkinitrd -v /boot/initrd-backup-`uname -r`.img `uname -r`
5) Now add the multiple entries to zipl.conf (same kernel image,
different initrd images); something like this:
[defaultboot]
default=2.6.9-42.0.3.EL
target=/boot/
[2.6.9-42.0.3.EL]
image=/boot/vmlinuz-2.6.9-42.0.3.EL
ramdisk=/boot/initrd-2.6.9-42.0.3.EL.img
parameters="root=/dev/VolGroup00/LogVol00"
[backup]
image=/boot/vmlinuz-2.6.9-42.0.3.EL
ramdisk=/boot/initrd-backup-2.6.9-42.0.3.EL.img
parameters="root=/dev/VolGroup00/LogVol00"
(...)
I would also run /sbin/zipl after making changes zipl.conf.
On Fri, 2006-12-01 at 14:28 +0100, Rob van der Heij wrote:
> On 12/1/06, Fuhrmann Anna <[EMAIL PROTECTED]> wrote:
>
> > Thank you Rob, this more verbose second answer seems to help me a lot.
>
> I often get obscure when I try to be brief :-)
>
> I would suggest to duplicate the section for your current kernel and
> ramdisk with a section title like [2.6.9-42.0.3.EL-Backup] with
> modified dasd= and add that to your boot menu as well. So you would
> also have the option to IPL with the set of alternate devices. If you
> really are paranoid you would keep also the alternate of your old
> kernel...
> So in the case of disaster, you IPL from the mirror of your original
> IPL volume. And you'll have to know that only the alternate menu
> entries would work.
>
> > I just did not know what these boot varieties mean, and thought
> > that the different image= and ramdisk= parms imply different kernel
> > versions -
> > do they? Because if yes, then I think I should implement the *default*
> > "ramdisk"/"image"
> > options with different "parameters", that could work. Is it the right way
> > to think about it?
>
> Looks like you have Red Hat rather than SuSE. I don't know how Red Hat
> does this. I believe SuSE allow the dasd= from the zipl.conf to
> override what's in the ramdisk. Give it a try.
>
> And you would need to remember to do this again when you upgrade your kernel.
>
> Rob
> --
> Rob van der Heij
> Velocity Software, Inc
> http://velocitysoftware.com/
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
--
Brad Hinson <[EMAIL PROTECTED]>
Technical Account Manager
Red Hat, Inc.
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
