Thank you Rob, this more verbose second answer seems to help me a lot.
My zipl.conf looks 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"
[2.6.9-42.0.2.EL]
image=/boot/vmlinuz-2.6.9-42.0.2.EL
ramdisk=/boot/initrd-2.6.9-42.0.2.EL.img
parameters="root=/dev/VolGroup00/LogVol00"
[linux]
image=/boot/vmlinuz-2.6.9-22.EL
ramdisk=/boot/initrd-2.6.9-22.EL.img
parameters="root=/dev/VolGroup00/LogVol00"
[EMAIL PROTECTED] sys]#
and there *is* a small menü when booting, asking exactly
if I want to boot [2.6.9-42.0.3.EL],[2.6.9-42.0.2.EL]or [linux],
or else it takes the default.
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?
regards Anna
>
>It's in your /etc/zipl.conf The way YaST generates it, there
>probably is no menu.
The documentation is in the Device
>Drivers documentation:
>http://download.boulder.ibm.com/ibmdl/pub/software/dw/linux390/
>docu/l26cdd02.pdf
>
>You could do something like this (assuming devices 0205-020F
>are primary, 1205-120F are alternate).
>
>[defaultboot]
> defaultmenu = menu1
>
>[ipl]
> target = /boot/zipl
> image = /boot/image
> ramdisk = /boot/initrd
> parameters = "root=/dev/dasdb1 selinux=0 TERM=dumb
>elevator=cfq"
>
>[suse-1]
> target = /boot/zipl
> image = /boot/image-2.6.5-7.276-s390x
> ramdisk = /boot/initrd-2.6.5-7.276-s390x
> parameters = "dasd=0.0.0205-0.0.020F root=/dev/dasdb1
>selinux=0 TERM=dumb elevator=cfq"
>
>[suse-2]
> target = /boot/zipl
> image = /boot/image-2.6.5-7.276-s390x
> ramdisk = /boot/initrd-2.6.5-7.276-s390x
> parameters = "dasd=0.0.1205-0.0.120F root=/dev/dasdb1
>selinux=0 TERM=dumb elevator=cfq"
>
>
>:menu1
>1 = ipl
>2 = suse-1
>3 = suse-2
>3 = rmh1
>target = /boot
>default = 2
>
>prompt = 1
>timeout = 10
>
>With this scheme it will prompt on the HMC to select another
>entry than the default 2.
>
>> >I trust z/OS will already have broken your mirror before you try to
>> >IPL the Linux LPAR.
>> >
>> What do you mean?
>> I specified the mirror DASD at the console, and zLinux took instead
>> the original DASD and was up and running.
>
>I mean that an active alternate volume is not "visible" by the LPAR.
>You could not have the DASD subsystem maintain a copy in the
>background and also have the LPAR be able to write to copy
>too... And the LPAR would also see a duplicate volser, that's
>why the alternate volume is not visible while the mirror is active.
>If your primary device is gone, someone needs to tell the DASD
>subsystem to break the mirror and allow access to the
>alternate volume. That could be through z/OS or through the
>Storage HMC.
>
>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
>
----------------------------------------------------------------------
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
