I had numerous problems with zipl and, specifically, it's use of the zipl.conf file. No matter how I tried to pass it parms, it kept referring to parms in the .conf file. I finally erased the zipl.conf file and zipl took all of my parameters (correctly, I might add) from the command line and finally worked properly.
Don't know if this is your problem, but try deleting zipl.conf and pass all parameters directly. Michael Coffin, VM Systems Programmer Internal Revenue Service - Room 6527 1111 Constitution Avenue, N.W. Washington, D.C. 20224 Voice: (202) 927-4188 FAX: (202) 622-6726 [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> -----Original Message----- From: Donghwa Kim [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 12, 2002 12:16 PM To: [EMAIL PROTECTED] Subject: zipl Hi list. I am having a small problem using zipl. When I type "zipl -i image-2.4.17 -p /boot/parmfile -t /boot/zipl", it doesn't take correct input from the parmfile. It produces a different parmfile with an entry that looks like "dasd=0150 root=/dev/dasda2 noinitrd" which is not what I specified in the original parmfile. I am running s/390 Debian system with 2.4.17 kernel. zipl came with debian package: "dpkg -l | grep s390\-tools ii s390-tools 0.0.20020226-1 A set of fundamental utilities for Linux on" Has anyone experienced this problem? Thanks in advance for any help. __________________________________________________ Do You Yahoo!? Try FREE Yahoo! Mail - the world's greatest free email! http://mail.yahoo.com/
