Show Table of Contents
33.11. Post-Installation Script
Figure 33.14. Post-Installation Script
You can also add commands to execute on the system after the installation is completed. If the network is properly configured in the kickstart file, the network is enabled, and the script can include commands to access resources on the network. To include a post-installation script, type it in the text area.
Important
The version of anaconda in previous releases of Red Hat Enterprise Linux included a version of busybox that provided shell commands in the pre-installation and post-installation environments. The version of anaconda in Red Hat Enterprise Linux 6 no longer includes busybox, and uses GNU bash commands instead.
Refer to Appendix G, Alternatives to busybox commands for more information.
Important
Do not include the
%post command. It is added for you.
For example, to change the message of the day for the newly installed system, add the following command to the
%post section:
echo "Welcome!" > /etc/motdNote
More examples can be found in Section 32.8, “Kickstart Examples”.
33.11.1. Chroot Environment
To run the post-installation script outside of the chroot environment, click the checkbox next to this option on the top of the Post-Installation window. This is equivalent to using the
--nochroot option in the %post section.
To make changes to the newly installed file system, within the post-installation section, but outside of the chroot environment, you must prepend the directory name with
/mnt/sysimage/.
For example, if you select Run outside of the chroot environment, the previous example must be changed to the following:
echo "Welcome!" > /mnt/sysimage/etc/motd
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.