ZIPL(8) | System Manager's Manual | ZIPL(8) |
NAME¶
zipl - boot loader for IBM S/390 and zSeries architecturesSYNOPSIS¶
zipl [OPTION] [SECTION]DESCRIPTION¶
zipl is a boot loader tool for IBM S/390 and zSeries machines. It can be used to prepare devices for initial program load (IPL). The following functions are supported:- -
- booting a Linux kernel with optional ramdisk and kernel command line
- -
- taking a snapshot of the current system status (system dump)
- -
- loading a data file to initialize named saved segments (NSS)
- -
- command line: all parameters are provided through the command line switches described below. Using this mode, only a single boot configuration can be specified.
- -
- configuration file: parameters are provided by sections defined in a configuration file (see zipl.conf(5)). Using a configuration file, you can either specify a single boot configuration or a menu, i.e. a list of configurations from which users can choose at boot time.
- -
- display a list of available configurations
- -
- allow to choose a configuration
- -
- allow to specify additional kernel command line parameters
- -
- all boot relevant files (i.e. kernel, ramdisk and parameter files) must be located on a logical device which is mapped to a single physical disk of a type supported by zipl (i.e. DASD or SCSI disk)
- -
- adjacent data blocks on the logical device must correspond to adjacent blocks on the physical device
- -
- access to the first blocks (starting at block 0) of the physical device must be given
- -
- device characteristics of the underlying physical device: disk type and format (e.g. ECKD CDL or FCP SCSI), disk geometry in case of ECKD DASDs and block size
- -
- target device offset, i.e. the number of blocks between the physical device start and the start of the logical device containing the filesystem with all boot relevant files
- -
- a device node which provides access to the first blocks of the device
OPTIONS¶
- -h or --help
- Print usage information, then exit.
- -v or --version
- Print version information, then exit.
- -c <CONFIG FILE> or --config=<CONFIG FILE>
- Use the specified <CONFIG FILE>. If none is supplied,
the environment variable ZIPLCONF is evaluated if set, otherwise
/etc/zipl.conf is used.
- -t <TARGET DIRECTORY> or --target=<TARGET DIRECTORY>
- Use the specified <TARGET DIRECTORY>. zipl
uses this directory to store the bootmap, i.e. a file containing boot
data. The actual boot loader is installed onto the device containing the
target directory. Supported devices are DASD and SCSI disks.
- --targetbase=<BASE DEVICE>
- Install the actual boot loader on the device node specified
by BASE DEVICE.
- --targettype=<TARGET TYPE>
- Assume that the physical device is of the specified type. Valid values are:
- -
- CDL: DASD disk with ECKD/compatible disk layout
- -
- LDL: DASD disk with ECDK/linux disk layout
- -
- FBA: FBA disk DASD
- -
- SCSI: SCSI disk
- This option is required when working with logical devices
(see section "Logical devices" above).
- --targetgeometry=<CYLINDERS,HEADS,SECTORS>
- Assume that the physical device has the specified number of
cylinders, heads and sectors.
- --targetblocksize=<SIZE>
- Assume that blocks on the physical device are SIZE bytes
long.
- --targetoffset=<OFFSET>
- Assume that the logical device containing the directory
specified by the --target option is located on the physical device
starting at the block specified by OFFSET.
- -T <TAPE DEVICE> or --tape=<TAPE DEVICE>
- Install bootloader on the specified <TAPE DEVICE>.
Use this option instead of the 'target' option to prepare a tape device
for IPL.
- -i <IMAGE[,ADDRESS]> or --image=<IMAGE[,ADDRESS]>
- Use the Linux kernel image file <IMAGE>. An optional
hexadecimal ADDRESS may be provided to specify a non-standard load address
for the image file.
- -r <RAMDISK[,ADDRESS]> or --ramdisk=<RAMDISK[,ADDRESS]>
- Use the ramdisk image <RAMDISK>. An optional
hexadecimal ADDRESS may be provided to specify a non-standard load address
for the ramdisk file.
- -p <PARMFILE[,ADDRESS]> or --parmfile=<PARMFILE[,ADDRESS]>
- Use the kernel command line stored in file
<PARMFILE>. An optional hexadecimal ADDRESS may be provided to
specify a non-standard load address for the parameter file.
- -P <PARMLINE> or --parameters=<PARMLINE>
- When installing a kernel, use the kernel command line
<PARMLINE>. When --parmfile is specified as well, the contents of
the parmfile and <PARMLINE> are appended to form the resulting
command line.
- -s <SEGMENT,ADDRESS> or --segment=<SEGMENT,ADDRESS>
- Use the segment image <SEGMENT>. The mandatory
hexadecimal ADDRESS specifies the load address for the segment file.
- -d <DEVNODE[,SIZE]> or --dumpto=<DEVNODE[,SIZE]>
- Install a system dump record on the device identified by
DEVNODE. Supported devices are DASD ECKD or FBA disk partitions and IBM
3480/3490/3590/3592 tape devices.
- -D <DEVNODE[,SIZE]> or --dumptofs=<DEVNODE[,SIZE]>
- Install a dump record on the target device which writes
system dumps to the file system on the disk partition identified by
DEVNODE if supported by the hardware.
- -M <DUMPLIST[,SIZE]> or --mvdump=<DUMPLIST[,SIZE]>
- Install a multi-volume dump record on each device
associated with one of the partitions listed in file DUMPLIST. Supported
are DASD ECKD partitions formatted with the compatible disk layout.
- -m <MENU> or --menu=<MENU>
- Install the multi-boot configuration defined in menu
section <MENU> of the configuration file.
- -n or --noninteractive
- Answer all confirmation questions with 'yes'. This option
may be useful when zipl is called from within a shell script or in
other situations where no user interaction is possible.
- -V or --verbose
- Provide more verbose output.
- -a or --add-files
- Copy all specified files to the bootmap file instead of
just referencing them. This option allows specifying files in a boot
configuration which are not located on the target device.
- --dry-run
- Print the results of performing the specified action
without actually changing the IPL records. This option can be used to test
a configuration since all error-checking is still done.
- -f or --force
- Omit validity checking while producing a multi-volume dump.
Multi-volume dump partitions will be overwritten with dump data no matter
whether they contain a dump signature or not.
EXAMPLE¶
1. Scenario: prepare disk for booting a Linux kernel image using the following parameters:- the directory /boot is located on the boot device
- /boot/image contains the Linux kernel image
- /boot/ramdisk.img contains a ramdisk image
- /boot/parmfile contains the kernel parameter line
zipl -t /boot -i /boot/image -r /boot/ramdisk.img
-p /boot/parmfile
zipl -d /dev/dasda1
SEE ALSO¶
zipl.conf(5)Nov 2009 | s390-tools |