Changes

===Investigation 1: How do you install Fedora?==={{Admon/important tip| Logical Volume Management Update your Fedora Installation| Fedora uses It's a type of storage management called Logical Volume Management (LVM). In LVM, disk partitions are called Physical Volumes (PVs) and provide storage good idea to a Volume Group (VG). This storage is then split into various Logical Volumes (LVs). The advantage to this scheme is ensure that you can change LV size and you can add and remove PVs after your Fedora installationis fully updated before proceeding. For example, you You can add a new disk to update your system and then increase with the graphical tool located on the menu at >System>Administration>Software Update (or type the size command <code>gpk-update-view</code>), or by typing either of your existing filesystems using that extra disk space. ''Please be careful to enter all LVM information accurately, including the VG and LV names.'' We will investigate and manipulate LVM in future labs.these commands: <code>pkcon update</code> or <code>yum update</code>}}

{{Admon# Install the Fedora virtualization software: <code>yum groupinstall "Virtualization"</code> or <code>pkcon install @virtualization</note | Installation Time | code> The installation process will take about 15 minutes to complete when using DVDvirtualization software installed is in three parts:## A system service named ''libvirtd'' that manages the VMs. Click the Reboot button on the screen ## Tools to reboot manage virtualization, including the system after <code>virt-manager</code> graphical tool and the installation is complete<code>virsh</code> command-line tool.## The actual virtual machines themselves. There # Start the virtualization service: <code>service libvirtd start</code># The firewall configuration is a post installation setup after bootaltered by the addition of the virtualization software.}}Restart the firewall so that these changes become active: <code>service iptables restart</code># Start the graphical tool by selecting the menu option Applications>System Tools>Virtual Machine Manager or by typing the command <code>virt-manager</code>

# After booting from the Installation DVD, at the Welcome Screen choose "Install or upgrade an existing system" to launch the Graphical installation program and select the following options (you can use the media test to verify that {{Admon/caution|Reboot your DVD burned correctly -- It will take some time -- otherwise, skip it):#* Language - English#* Keyboard Configuration - U.S. English#* Type of devices: Basic Storage Devices#* fedora host|There should only be one storage drive listed - select it#* If you get a warning that the drive may need appears to be initialized, it is because an issue with supplying your drive is new and contains no partitition table. Select "Re-Initialize"#* Set your hostname to - f13host (one word, no space, all lowercase)#* Root Password: enter VM's with a password of your own choosing. Pick one that is really, really hard to guess to protect your system. (Recommendation: use the first letter and all dynamic IP unless the punctuation from a favorite phrase or song verse. For example, "To be or not to be, that host is the question!" could become the password restarted after installing "Tbontb,titq!Virtualization").#* Disk Partition Setup - Specify a Custom Layout, and then set up the installation with this configuration:#** Find your existing 300MB partition (/dev/sda1). Edit this entry so that the mountpoint is /boot and is formatted as an ext3 filesystem.#** Don't touch the other existing 300M partition (/dev/sda5).#** Create 4 new LVM Physical Volumes that are 25000 MB in size. Set the File System Type to Physical Volume (LVM). Should be /dev/sda6 to /dev/sda9.#** Create an LVM Volume Group. Set the Volume Group Name to '''vg_main''' and set the Physical Extent size Reboot now to '''4MB'''avoid this problem.#** Click on the Add button (within the "Make LVM Volume Group" window) to create a logical volume within that volume group:#*** Mount point / (root), filesystem type ext4, logical volume name '''root''', size 90000MB.#* Say yes to continue without a swap partition.#* Say yes to format /dev/sda1.#* Accept Boot Loader defaults.#* Accept Graphical Desktop and repository defaults.# Proceed with the installation. '''Note how long it takes to perform the installation.'''# Reboot using the controls on the screen. When the system starts, it will ask you some final configuration questions.#* Check the License Agreement. What license is used for the Fedora distribution? What activities do have restrictions and obligations?#* Create a user account for yourself using the same name as your learn account.#* Set date and time. Normally, you would want to enable Network Time Protocol, but since we will be experimenting with the networking turned off in later labs, leave it disabled.#* Click on Do Not Send Hardware Profile.#* Finish the post-installation customization, wait for the login screen to appear, and then login to your Learn account.}}

Answer the === Investigation 1 question in your lab log book.: Installing from a Live Disc ===

{{Admon/tip|Forcing the Resolution on the Projector|The podium computers in the lab rooms are connected to a video splitter. This splitter then connects to both the LCD screen on the podium and the projector at the front Using an Image instead of the room. However, the splitter prevents the computer from successfully querying the LCD or screen to find the supported resolutions, and Fedora therefore selects a very low (safe) resolution. Live Disc|If you are using do not have a podium systemLive Disc available, you can force download the native 1680x1050 resolution of the LCD display using [.iso image file from http://matrixbelmont.senecac.on.ca/~chris.tylerfedora/releases/13/Live/x86_64/fedoraFedora-13-x86_64-scripts/1680x1050 this script]Live.iso and then use the iso image file in place of the physical disk.}}

===Investigation 2: How many files packages and files are installed on the system?= Introduction ====

For the rest of the tasks in In this labinvestigation, you must login to your system using your Learn account and execute all commands under will install Fedora from your learn account. If you get a Permission Denied message when trying to execute a commandlive disc, then switch to the superuser account by running the command su - and type in observe the password for "root". Once the intended command is executed, differences between this type "exit" to exit from of installation and the superuser account and return to your regular Learn accountDVD installation previously performed.

# To find all the mount points, enter the command* Name: <code>mount</code>fedora1#* Study the output and record all the mount points in your log book.# The name of the installation log file is <code>/root/install.log</code> -- It is an ASCII file (how can you be sure?) and can be viewed with the <code>less</code> command. # You can make use of this file to determine how many packages have been installed: complete the following command to count the number of packages listed in the installation log fileBoot media:Fedora Live CD#* <code>grep ________________ /root/install.log | wc -l</code># Using the <code>rpm</code> command: you can also use the following commands to list all the installed packages, and the total number of packages installedInstallation source:Fedora Live CD#* <code>rpm -q -a</code>#* <code>rpm -q -a | wc -l</code>#* <code>rpm -qa | wc -l</code># The <code>-q</code> option means query, and the <code>-a</code> option means all (in other words, query all installed software packages). Did you get the same number of packages from the above two methods?# Some of the files on your system were installed with the software packages, and some were created by system activity (for example, by creating your Learn account and by logging in). If you know the package name (from the <code>install.log</code>), you can list all the files that were installed from the package by using the following commandMemory:512MB#* <code>rpm -q -l package_name</code># This combines the <code>-q</code> (query) option with the <code>-l</code> (list filenames) option.# You can pipe the outupt through <code>wc -l</code> to count the number of linesDisk space:10GB#* <code>rpm -ql package_name| wc -l</code># Using what you learned in steps 3, 4, and 8, get a count of the total number of files installed by all of the software packages on your system.# To find out the name that you have assigned to your Linux system, enter the commandCPUs: <code>hostname</code># To find out the kernel version of your GNU/Linux workstation and the date it was created, enter the command: <code>uname -r</code># To find out all the system processes running on your GNU/Linux workstation, enter the command: <code>ps -ef</code># To capture the list of all the system processes to a file called <code>ps.lst</code>, enter the command: <code>ps -ef > ps.lst''</code># Copy the installation log file <code>/root/install.log</code> and the file ps.lst to a USB memory key, or scp to your matrix account as a backup.1

=== Investigation 3: What is {{Admon/note|Fedora 12 Screen Shots|The following screen shots are from Fedora 12. The Fedora 13 version of virt-manager varies slightly -- there are a runlevel? ===few extra controls on some dialogs which may be ignored.}}

After # In the kernel bootsVirtual Machine Manger, it starts click on the icon to ''Create a single program, called Virtual Machine'' in the upper-left corner: <br />[[Image:Virt-manager1.png]]# A window will appear with the title ''New VM''. There are five steps to be completed; click Forward after each step:# Step 1 of 5: Enter the virtual machine name and select ''Local install media''.<codebr />init[[Image:Virt-manager2.png]]# Step 2 of 5: Insert the CDROM or DVD containing the Fedora Live Disc image. Wait a moment for the disc to be recognized, then select it as the install media. Set the ''OS type'' to Linux and the ''Version'' to Fedora 13.<br /code>[[Image:Virt-manager3. A running instance png]]<!-- {{Admon/tip|Using an ISO image|Instead of using a program is called physical CD or DVD, you can use an ISO image of a CD or DVD. The virtualization software will make this ISO image appear like an actual CD within the virtual machine. Because hard disks are faster then optical discs, this will work faster than an actual CD/DVD.}}{{Admon/note|Choosing the operating system type and version|The purpose of the ''OS type''processand ''Version'' fields is to fine-tune some of the virtual machine settings for best performance. The VM will work even if these are set incorrectly.}} --># Step 3 of 5: Set the memory to 512 MB and the number of CPUs to 1.<br />[[Image:Virt-manager4.png]]# Step 4 of 5: This next step creates a disk file that will be used to simulate the virtual machine's disk drive. Select a size of 10 GB and checkmark the box labeled ''Allocate entire disk now''.<br />[[Image:Virt- manager5.png]]# Step 5 of 5: Review the options that you have selected. '''Make a note of the init process always has storage location.''' If anything needs to be changed, use the ''Back'' button to go back and edit it; otherwise, click ''Finish''.<br />[[Image:Virt-manager6.png]]# The virtual machine will now start. You will see a process ID window which displays the virtual video card from the VM. It's important to note that the VM can (PIDand often will) run even when this display is not present. The virtual machine is running from the live disc at this point, and no software has been installed on the ''hard drive'' of 1the virtual machine.# Login to the VM and double-click on the ''Install to Hard Drive'' icon. The installation program, similar to the one used when installing Fedora in Lab 2, will appear. You will get a warning at one point during the installation process that the disk "may need to be re-initialized" -- this is simply a warning that the virtual disk is completely blank, and it is safe to select ''Re-initialize drive''. # During the installation process, when prompted for the drive, select "Virtio Block Device", when prompted for the hostname, enter "fedora1", when prompted for the timezone, select ''America/Toronto'', and when asked about storage, select ''Use All Space''. '''Use the default values for all other processes on fields.''' Notice that the installer does not ask you what software should be installed; compare the installation time to the amount of time it took to do your Lab 2 installation.# When the installation is complete, select the menu option System>Shutdown to stop the Live Disc.# Start the system are started VM from its disk image by initselecting Virtual Machine>Run from the virtual machine menu. You will get the ''Firstboot'' configuration questions during the boot process (asking you to create a user, set the date and time, or they are started by processes started by initand optionally send the hardware profile to the Fedora Project). Create a user with the same name as your Matrix account.# Login using the new user account.# Enable SSH access to your virtual machine with these commands: <code>service sshd start; chkconfig sshd on</code># Find out the IP address of your virtual machine: <code>ifconfig eth0</code># Enter the following command on your virtual machine to create a firewall exception to allow ssh traffic into the machine: <code>iptables -I INPUT -p tcp -s0/0 -d0/0 --dport 22 -j ACCEPT</code># Confirm that you can ssh to your virtual machine from the host (your main Fedora installation): <code>ssh ''IPaddress''</code>

Most current Linux systems use some variation of === Investigation 2: Installing from the init system originally developed for Unix System V (called "sysvinit") or a newer version called "upstart".Network ===

These systems employ {{Admon/tip|Authenticate to the concept network|The rest of "runlevels" -- groups of software that can be selected, so that this lab uses network access. Be sure to authenticate to the system can be run in various modesnetwork using your browser before proceeding. In Fedora systems, these runlevels are used:}}

==== Introduction ==== It is possible to install Fedora entirely from the network. In this investigation, you will install Fedora from a webserver on Seneca's LAN. ==== VM details ==== * Name: fedora2* Boot media: Network installation* Installation source: http://belmont.senecac.on.ca/fedora/releases/13/Fedora/x86_64/os/* Memory: 512MB* Disk space: 15GB* CPUs: 1 ==== Steps ====# Create the VM as you did with the ''fedora1'' virtual machine, except:#* In step 1 of 5, set the installation type to "Network Install (HTTP, FTP, or NFS)"#* In step 2 of 5, provide the URL http://belmont.senecac.on.ca/fedora/releases/13/Fedora/x86_64/os/#* In step 2 of 5, set the ''OS Type'' to "Linux" and ''Version'' to "Fedora 13" # Observe the boot process. How is it different from booting from an optical disc (CD/DVD)?# Start the installation process. When you get to the disk partitioning step, enable the checkbox labelled ''Review and modify partition layout''. On the next screen, change the logical volumes as follows:#* Reduce the size of the root LV to 8000 MB.#* Add a logical volume with a size of 2000 MB and a mountpoint of /home (you can name it whatever you want, and use ext3 or ext4 as the filesystem type).# On the software selection screen, select ''Graphical Desktop''.# On the same screen, select the "Fedora 13 - x86_64" and the "Fedora 13 - x86_64 - Updates". Leave "Installation Repo" selected. ''DO NOT'' enable the "Test Updates" repository.# Complete the installation. Record the time taken to install, and compare this to the time taken by the previous installations. === Investigation 3: Installing from the Network using Kickstart === ==== Introduction ==== When Fedora is installed using the techniques you have used so far, the user is asked a number of questions. In some situations, it is better to provide the answers to these questions in a file rather than answer them individually. This type of file is called a ''kickstart'' file. In this investigation, a kickstart file is provided for you. You can also create or modify a kickstart file using a regular text editor or a graphical tool. ==== VM details ==== * Name: fedora3* Boot media: Network installation* Installation source: http://belmont.senecac.on.ca/fedora/releases/13/Fedora/x86_64/os/* Kickstart location: http://zenit.senecac.on.ca/~chris.tyler/fedora13-vda-ks.cfg* Memory: 512MB* Disk space: 10GB* CPUs: 1 ==== Steps ====# Create the VM as you did with the ''fedora2'' virtual machine, specifying a network install as before, except:#* In step 2 of 5, after entering the URL for the installation source, click on the ''URL Options'' control.#* Enter the Kickstart URL: http://zenit.senecac.on.ca/~chris.tyler/fedora13-vda-ks.cfg # Observe the installation. How is it different from booting from an optical disc (CD/DVD)?# Complete the installation. Record the time taken to install, and compare this to the time taken by the previous installations. # What happens when the installation is finished?# Take a look at the kickstart file (using the URL you entered) to determine the root password as well as the name and password for the first user account.# Boot the virtual machine and log in (use the user ID and password information from the previous step). Compare the experience to the first time you booted the other virtual machines. === Investigation 4: Updating and Comparing the VMs === # In each VM, run this command: <code>yum update</code># Record the answers to these questions in your log book:#* How long did it take to run on each VM? How many packages were updated?#* Why does it take longer in some VMs than others? Complete the following table: {|classborder="mediawiki1" borderwidth="1100%"|-!Runlevel||f13host||fedora1||fedora2||fedora3!Description|-|'''Installation Method'''||Installation Disc||Live Disc||Network Installation||Network Installation + Kickstart|-|'''Packages Installed'''|| || || |||-|'''Updates Installed immediately after installation'''|| || || |||-|'''Software could be selected during installation'''|| || || |||-|'''Disk layout could be selected during installation'''|| || || ||

|0'''No questions asked during installation'''|| || || ||Halt (powers off the system)

|1'''Total installation time''' (after installation questions)|| || || ||Single-user maintenance mode, network not running, character-mode display

|2|''Not normally 'Amount of disk space used - originally meant: Multi-user mode, network not running, character-mode display'''|| || || ||

|3'''Questions asked during first boot'''|| || || ||Multi-user mode, network running, character-mode display

|4|''Not normally used'Advantages of this type of installation'''|| || || ||

|5'''Disadvantages of this type of installation'''|| || || ||Multi-user mode, network running, graphical user interface

|6'''This type of installation is recommended for...'''|| || || ||Reboot

{{Admon/note|Different runlevel systems|Various Linux distributions may use === Investigation 5: Managing Virtual Machines from the runlevel numbers differently. For example, on some Debian/Ubuntu systems, the default (standard) runlevel is 2.}} In order to implement runlevels, init uses a configuration file and a number of script files:Command Line ===

* <code>{{Admon/etc/inittab</code> is note|Manage virtual machines from the configuration file, which sets host|The commands used to manage virtual machines must be executed on the default runlevel.* <code>/etc/rc.d/init.d</code> is host (your disk pack) and not inside a directory of scriptsvirtual machine.}}

In order to determine which of # Start the startup scripts should be executed in each runlevel''fedora1'' virtual machine, and stop the ''fedora2'' and ''fedora3'' virtual machines.# Enter these commands and note the one directory per runlevel is created (result:#* <code>virsh list</etccode>#* <code>virsh list --all</rc.dcode>#* <code>virsh list --inactive</rccode># Start the ''fedora3'X' virtual machine from the command line: <code>virsh start fedora3</code># Repeat the commands from step 2 and notice any changes.# Stop the ''fedora3'.d' virtual machine: <code>virsh shutdown fedora3</code>, where # Confirm that '''X'fedora3'' has been shut down.# Execute this command: <code>virsh dumpxml fedora3 >fedora3.xml</code># Examine the file <code>fedora3.xml</code>. What does it contain? What format is it in?# Edit the runlevel)file fedora3. This directory is filled with symbolic links xml, making the following changes:#* Change the name to <code>fedora3a</code>#* Change at least one of the startup scripts hexadecimal characters in the UUID. Do not change the length of the UUID. Valid hexadecimal characters are 0-9 and a-f.# Issue this command: <code>virsh define fedora3a.xml</etccode># Issue the command <code>virsh list --all</rccode> and record any changes.d/init.d# Issue the command: <code>virsh undefine fedora3a</code># List all of the virtual machines again, and note any changes.

# To find out the value of the runlevel your GNU/Linux system goes into after boot, enter the command=== Investigation 6: <code>grep initdefault /etc/inittab</code># You should get a single line containing ":" as the field delimiter. The second field stores the value of the runlevel the init process will use after a reboot. Record the output in your log book.# A list of processes that should be running at a given runlevel can be found in the directory <code>/etc/rc.d/rc'''X'''.d</code> where '''X''' is the runlevel. Do a directory listing of that directory and study what files are in there. Pay attention to the first three characters of each file name. They have special meaning to the system. Record your observation in your log book.# Make a How do I backup of the file /etc/inittab with the command: <code>cp /etc/inittab /etc/inittab.original</code># Edit the file <code>/etc/inittab</code> and change the default runlevel to 3. Save the change and reboot your system.# After the reboot, you should get a "Text Login Screen". Login with your Learn account and type startx at the command prompt. Describe what happens in your log book.# Enter the command: <code>runlevel</code> -- this shows the previous and current runlevel. Record the values in your book.virtual machine? ===

Answer {{Admon/important|Backing up VMs|It's a good idea to back up your VMs at the Investigation 3 questionend of each lab, so you can easily restore them if something goes wrong in the next lab.}}

=== Investigation 4: What is {{Admon/tip|Shutting Down the network configuration? ===Host while Virtual Machines are Running|If you shut down your host system while virtual machines are running, they will be suspended, and will resume the next time you boot your host system.}}

# To check the network configuration settings obtained from the DHCP server, run the following commands, describing the output in your log book=== Investigation 7:#* ifconfig#* route#* netstat -rn#* nslookup (at the > prompt, enter the word "server" (do not type the quotes) and record the output. Type exit to leave nslookup).# Find the following information in the output of the above commands:#* MAC address (physical or hardware address) of the ethernet network interface#* The IP address (logical address) assigned by the DHCP server#* The default route (gateway)#* The DNS nameserverKickstart Files ===

Answer {{Admon/tip|SSHD and Firewall|If you have restarted your virtual machine ''fedora1'', the Investigation 4 questionsshd server you started in section 1-16 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.}}

=== Investigation 5: How do You Secure When you perform a non-Kickstart installation, the Grub Boot Loader? ===installation program creates a Kickstart file in the <code>/root</code> directory for reference.

{{Admon/caution|Duplicate UUIDs|Before proceeding, use the <code>mount</code> command to check to see which filesystem is mounted on the mount point <code>/boot</code>. If it is <code>/dev/sda5</code>, it is # Obtain the wrong filesystem. This may be caused by a duplication of serial numbers which is the result of Lab 1; you can fix this problem with this series of commands: mkdir /media/sda5 /tmp/sda5-files umount /dev/sda5 mount /dev/sda5 /media/sda5 cp -v -R /media/sda5/* /tmp/sda5-files umount /dev/sda5 mkfs -t ext3 /dev/sda5 mount /dev/sda5 /media/sda5 cp -v -R /tmp/sda5-kickstart files/* /media/sda5 rm -rf /tmp/sda5-files mount -a}} By default, the Grub boot loader allows anyone with access to the computer at boot time to set the runlevel, or change the boot parameters, which can allow them to influence the init process and which kernel image is loaded. Anyone with access to the boot prompt can therefore bypass security controls and control which software is loaded. For example, rebooting to runlevel 1, known as single user mode, gives the user root priveleges without the need for a password! Obviously, giving a non-administrator this much control can be dangerous, and it is wise to protect the boot loader with a secure password.  We will need to choose a password, encrypt with the grub programs hash utility all four of your installations (called md5crypt), and add the encrypted hash of your password to the grub configuration filedisk pack ''f13host'', /etc/grub.conf {{Admon/important|Do not lose plus the GRUB password|If you lose the GRUB password you will not be able to change boot parameters when you boot the system. If you need to write it down''fedora1'', put it in a safe place, where no one will be able to tell what it is for.}} # Choose a suitable password. # Open the grub program by typing the command: <code>grub</code># At the grub prompt, type in the command: <code>md5crypt</code># When prompted for a password, carefully type in your password. The program will display the encrypted hash of your password. Carefully write down that encrypted hash generated by the program.# Type the command: <code>quit</code> to exit the grub program.# Open the grub configuration file, <code>/etc/grub.conf</code> for editing. (This file is actually linked to /boot/grub/grub.conf).# Carefully add the line: <code>password --md5 ''password-hashfedora2''</code> (note: , and ''password-hashfedora3'' is the hash you generated with md5cryptvirtual machines) Place this line between the splashimage line and the title line. If there are other lines there, there is no need Copy them all to remove them. Just insert your password line as a new line.# Make sure you have not made a mistake. What you type in must match exactly the output from the md5crypt command.# While you are editing the file you should also increase the timeout for grub to automatically boot the default OS. Edit the line f13host system (tip: use <code>timeout=0scp</code> to <code>timeout=5</code> to give us more time to interrupt the process).# You should also ensure that Compare these files. What are the grub boot menu is not hidden. Add a hash sign differences? Similarities? (Tip: you may want to use tools such as <code>#sdiff</code>) to help with the start of the line which reads: <code>hiddenmenu</code>comparison).# Save How could you use the kickstart file and exit. Your Grub boot loader is now password protected.# Find produced by the section of [http://fedorasolved.org/post-install-solutions/runlevel this article] that explains how installation program to change the runlevel at boot time, and read it. Reboot your systemperform additional, trying to change to runlevel 1 from the boot prompt, and see if the password protection worked.# From now on, when you want to change boot parameters when you boot, you must type lowercase <code>p</code> at the boot prompt and enter the required password.identical installations?

Check off {{Admon/important | Important! | Arrange evidence of each of the following items before asking on the screen, and then ask your instructor professor or lab monitor to check your labthem:}}

* Task 1 - Install GNU/Linux Workstation using Fedora # Three working virtual machines created.* Task 2 - Collect system information after installation# Four kickstart files.* Task 3 - Customize and configure boot time environment# All virtual machines fully updated.* Task 4 - Collect network information* Task 5 - Password protect Grub Bootloader Arrange evidence for each of these items on your screen, then ask your instructor to review them and sign off on the lab's completion: * Grub is password protected# All virtual machines backed up.* Can login with your "learn" account name* Has all the mount points* Has the package count* Has edited the default runlevel* Has the correct IP address and MAC address* Find out the default route (gateway)* IP of the DNS name server* '''Name and contact information on your disk pack''' {{Admon/tip|Runlevel|Feel free to change your default runlevel to 3 or 5 according to your own personal preference. Note that later labs may assume a particular runlevel# Installation comparison table filled in.}}

# How many packages were installedWhat is the name of the Fedora installation program?# How many files Which factors recorded in your table (correct above) were due to the nearest hundred) type of installation performed, and which factors were due to the amount of software installed?# How many mount points were usedWhich type of installation works best for confirming compatibility with hardware before installation? Why?# How many users were created automatically on your system (do not count your learn account)Which type of installation works best for installing large numbers of computers? Why?# What is your learn account's UID and GIDfactors affect installation time?# How can you reduce the number of software updates required immediately after installation?# What is your learn account's home directoryWhy would you enable additional repositories during installation?# What is does the home directory for the user "file <code>/root"/anaconda-ks.cfg</code> contain, and how is it created?# How do you determine the host name of start and stop virtual machines?# How do you SSH into your GNU/Linux workstationvirtual machines?# What command can display is the NIC's MAC addresspurpose of and relationship between these pieces of software?# Which file contains the default "runlevel" value for your GNU/Linux workstation?* libvirt#* libvirtd#* virsh#* virt-manager#* virt-install#* vncviewer{{Admon/important|Unbind your MAC address|Before moving your disk pack to another system, [[Unbinding MAC Addresses on Fedora|unbind your MAC address]].}}#* kvm