Hi Mark, Thanks - I didn't think of deleting zipl.conf - that's a great idea!
By the way, does anyone know if there are any known problems using zipl on RH 7.2 RC2 with an ext3 filesystem? I managed to create a boot disk last night but when I went to boot the new disk it complained loudly about the mount designation for '/' in /etc/fstab - which says to mount device "LABEL=/" - I've never seen a mount designated like that. So the new boot disk was bad, and when I went to boot my base system it's boot disk had become corrupted. Looks like part of the boot files went to my original boot disk (dasda) and some went to my new boot disk (dasdp). Michael Coffin, VM Systems Programmer Internal Revenue Service - Room�6030 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: Post, Mark K [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 15, 2002 11:11 PM To: [EMAIL PROTECTED] Subject: Re: zipl Command Format and Usage Mike, The help for the command is thus: # zipl --help z/IPL - the zSeries initial program loader Copyright (C) 2001 IBM Deutschland Entwicklung GmbH, IBM Corporation Author: Carsten Otte <[EMAIL PROTECTED]> Sypnosis: zipl [options] [configuration] Options: -h or --help prints this information -c <CONFIG-FILE> or --config=<CONFIG-FILE> <CONFIG-FILE> specifies the config file to be used. This option overrides the environment variable ZIPLCONF. The following options override settings in the config-file: -t <DIRECTORY> or --target=<DIRECTORY> <DIRECTORY> specifies the target directory where zipl installs some files needed for the ipl process -i <IMAGE[,ADDRESS]> or --image=<IMAGE[,ADDRESS]> <IMAGE> specifies the filename of the bootable image [ADDRESS] specifies the address, where the image will be loaded in memory -r <RAMDISK[,ADDRESS]> or --ramdisk=<RAMDISK[,ADDRESS]> <RAMDISK> specifies the filename of the ramdisk to be loaded [ADDRESS] specifies the address,where the ramdisk will be loaded in memory -p <PARMFILE[,ADDRESS]> or --parmfile=<PARMFILE[,ADDRESS]> <PARMFILE> specifies the filename of the parmfile to be loaded [ADDRESS] specifies the address, where the parmfile will be loaded in memory -d <PARTITION> or --dumpto <PARTITION> <PARTITION> specifies the device node of the partition on with the dump will be created. Example: /dev/dasdb1 or /devfs/dasd/0192/part1 Note: <ARG> means required argument [ARG] means optional argument Have you tried emptying out /etc/zipl.conf so that only what you specify on the command line has any relevance? Mark Post -----Original Message----- From: Coffin Michael C [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 15, 2002 5:25 PM To: [EMAIL PROTECTED] Subject: zipl Command Format and Usage Hi Folks, I'm trying to build an IPLable RedHat 7.2 RC2 boot disk. I've currently got the entire system on a very large 150/dasda disk. I've split /usr off onto a r/o 152/dasdc disk and everything else that was on 150/dasda has been copied to 15f/dasdp. I mount dasdp as /mnt/temp and now I want to run zipl (the replacement for silo) - but I can't figure out the parameters. It seems like I should just be able to execute: zipl -c /etc/zipl.conf -d /dasd/dasdp1 according to the online --help. But when I do this I get: Option error: You supplied both - image and dumpto parameters from configuration file or command-line. Please specify only one of these in one job. There doesn't seem to be an option to specify "do not use a configuration file" and take the operands from the command line. What is the exact command syntax to write the IPL records to /dev/dasdp1? -Thanks in advance, sorry if this has been covered already. I've looked everywhere for detailed zipl command reference and usage notes and can find practically nothing. Michael Coffin, VM Systems Programmer Internal Revenue Service - Room 6030 1111 Constitution Avenue, N.W. Washington, D.C. 20224 Voice: (202) 927-4188 FAX: (202) 622-6726 [EMAIL PROTECTED]
