I just did a quick experiment with RHEL3, mkinitrd,
and zipl.

1) I updated /etc/modules.conf, then did the mkinitrd
using the same name for /boot/initrd.... When I
rebooted, the new dasd were NOT there.
2) I then did a zipl and rebooted. The new dasd was
picked up.

Bottom line - both the mkinitrd and zipl are required
to change the dasd addresses.

The "dasd=" is not placed in the boot record by zipl
or mkinitrd. Is it that the boot record has to be
updated by zipl to get to the new initrd module?

=====
Jim Sibley
RHCT, Implementor of Linux on zSeries

"Computer are useless.They can only give answers." Pablo Picasso

__________________________________
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html

Reply via email to