The first example shows a sles8 system SP3, the second example is a non
SP3 sles8.
John
James Melin <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[email protected]>
03/29/2005 11:05 AM
Please respond to
Linux on 390 Port
To
[email protected]
cc
Subject
zipl - one system giving different messages.... how can I verify it is
using zipl.conf?
This is on a SLES 8 SP 3 system.
All my systems save one show this kind of behaviour when I make a change
to
/etc/zipl.conf. save one:
phalen:/etc # zipl
Using config file '/etc/zipl.conf'
Building bootmap '/boot/zipl/bootmap'
Adding IPL section 'ipl' (default)
Preparing boot device: dasdb (0201).
Done.
That system returns:
pequot:/etc # zipl
building bootmap : /boot/zipl/bootmap
adding Kernel Image : /boot/kernel/image located at 0x00010000
adding Ramdisk : /boot/initrd located at 0x00800000
adding Parmline : /boot/zipl/parmfile located at 0x00001000
Bootloader for ECKD type devices with z/OS compatible layout installed.
Syncing disks....
...done
Should I be concerned?
If so how do I reconcile this? These should all be at the same level and
service pack but something is wrong
----------------------------------------------------------------------
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
