715
edits
Changes
→Part 3: Installing from a Network using a Kickstart File
:::You'll notice something when you go to set '''SElinux''' to '''permissive'''. The kickstart file already did that for you. It could even have performed the switch from firewalld to nftables for you (but it didn't).
# Remember that rhel3 is text-based interface only (no graphics). To recover from a blank screen, press a key (like the SPACE key) to return to the screen display.
# Issue the following command to obtain and record your rhel3 IPADDR in your lab2 logbook: <b><code><span style="backgroundcolor:#3366CC;font-colorsize:yellow1.2em;">ip address show</span></code></b># Perform a <code><span style="backgroundcolor:#3366CC;font-colorsize:yellow1.2em;">'''dnf update'''</span></code>. Notice you receive a message telling you the system is not registered with an entitlement server. That is because the kickstart file did not attach a subscription for you.
# Attach a subscription using the subscription-manager cli tool. This will register your system with Red Hat (using your Red Hat account) like we did in the installation for r9host, rhel1 and rhel2; just as a post installation task. Issue the following commands to set the system purpose (just like we did graphically through the installer):
## <code><span style="color:#3366CC;font-size:1.2em;">sudo subscription-manager syspurpose role --set "Red Hat Enterprise Linux Server"</code></span>## <code><span style="color:#3366CC;font-size:1.2em;">sudo subscription-manager syspurpose service-level --set Self-Support</code></span>## <code><span style="color:#3366CC;font-size:1.2em;">sudo subscription-manager syspurpose usage --set Development/Test</code></span>
# Now use the following command to register your system and attach your subscription. Enter your Red Hat account credentials (which you created in Lab 1) when prompted:
## <code><span style="color:#3366CC;font-size:1.2em;">sudo subscription-manager register</code></span>## <code><span style="color:#3366CC;font-size:1.2em;">sudo subscription-manager attach</code></span>
# Try updating your system again with dnf. This time it should succeed.
# Record the time taken to install, and compare this to the time taken by the previous installations in your lab2 logbook.
