English Sinhala
You can specify a device to be activated in any of the following ways:
You can specify a package group or environment using either its ID (the `<id>` tag) or name (the `<name>` tag).
You can specify packages by _environment_, _group_, or by their package names. Several environments and groups that contain related packages are defined. See the `repodata/comps.xml` file in your installation source for environment and group definitions.
You can specify that ports be allowed through the firewall using the port:protocol format. For example, to allow IMAP access through your firewall, specify `imap:tcp`. Numeric ports can also be specified explicitly; for example, to allow UDP packets on port 1234 through, specify `1234:udp`. To specify multiple ports, separate them by commas.
You could use an entry similar to one of the following:
You have the option of adding commands to run on the system once the installation is complete, but before the system is rebooted for the first time. This section must be placed towards the end of the Kickstart file, after the actual Kickstart commands, and must start with [command]#%post# and end with [command]#%end#. If your Kickstart file also includes a [command]#%pre# section, the order of the [command]#%pre# and [command]#%post# sections does not matter.
You should always use a password to protect your boot loader. An unprotected boot loader can allow a potential attacker to modify the system's boot options and gain unauthorized access to the system.
You should configure iSCSI storage in the system BIOS or firmware (iBFT for Intel systems) rather than use the [command]#iscsi# command if possible. If you do so, [application]*Anaconda* automatically detects and uses disks configured in BIOS or firmware and no special configuration is necessary in the Kickstart file.
zerombr (optional) - Reinitialize Partition Tables
zfcp (optional) - Configure Fibre Channel Device