Specifying variables for future use
You can extend a zipl environment file to include keywords that are not used yet, but can be in the future.
About this task
You can add keywords for future use by setting them to empty strings. Using such reserved keywords helps you avoid boot record re-installation in the future, when you want to add more parameters to the kernel command line.
Procedure
Results
# zipl-editenv --set MYVARIABLE_1=console=ttyS1
# zipl-editenv --list
root=/dev/dasda1
panic=9
MYVARIABLE_1=console=ttyS1
MYVARIABLE_2=
The value for a reserved keyword must be the complete kernel parameter
specification. For many kernel parameters this is a
<parameter>=<parameter_value>
pair, for
example panic=9
.
After rebooting, you can see that the new value was applied
to the installation as it shows up in the command line:
# cat /proc/cmdline
root=/dev/dasda1 panic=9 console=ttyS1 ...