== Investigation 7: Kickstart Files ==
{{Admon/tip|SSHD and Firewall|If Even when you have restarted your virtual machine ''fedora1''perform a non-Kickstart installation, the sshd server you started installation program creates a Kickstart file in investigation 1 (step 15) will no longer be running. In addition, the firewall will have reverted to its original state. In order to use '''scp''', below, you will need to restart ssh and adjust the firewall again.<br code>/>root<br /code>If students cannot backup their kickstart files using the '''scp''' command, they can use a web-browser to access their Seneca e-mail with attachment (copy kickstart file to their home directory first!). For the text-based Linux system "fedora3", students can use the '''mail''' command (refer to the man command to learn how to send e-mail attachments)for reference. }}
When you perform a non-Kickstart installation, the installation program creates a Kickstart file in the <code>/root</code> directory for reference. # Obtain the kickstart files for all four of your installations (your disk pack ''f17hostc6host'', plus the ''fedora1centos1'', ''fedora2centos2'', and ''fedora3centos3'' virtual machines).# To prevent confusion, copy your kickstart files to kickstart filenames that describe their purpose (eg. kickstart_host, kickstart_fedora1kickstart_centos1, kickstart_fedora2kickstart_centos2, etc...)# Copy them all to your f17host c6host system (tip: use <code>scp</code>), or use the hint in the tip box above to send via e-mail.
# Compare these files. What are the differences? Similarities? (Tip: you may want to use tools such as <code>sdiff</code> to help with the comparison).
# How could you use the kickstart file produced by the installation program to perform additional, identical installations?