OPS235 Lab 1 - CentOS7 - VMware

LAB PREPARATION

Purpose / Objectives of Lab 1

The centos1 Linux server will run virtualization software to install and run 3 virtual machines (installed in lab2).

You will learn how to use a popular Virtual Machine (VM) application called VMware Workstation in order to create and manage a virtual machine (Centos Linux - Full Install DVD). We will install three other Centos Linux VMs (using 3 different install methods) in lab2.

In order to save money and resources when learning to install, manage, and network various Linux machines for this course, we will be using virtualization for this course. In previous courses, students were required to purchase a removable hard disk drive to complete this course. You are NOT required (preferred) to use a removable hard-drive for this course. On the other hand, it is ESSENTIAL to have a USB key (minimum storage capacity of 16 GB) to save your Linux images in your temporary Seneca lab sessions and be able to work on your VM images on your notebook computer or desktop computer at home. You will learn during this lab how to obtain VMware Workstation 12 for your use for your notebook computer or desktop computer at home.

Main objectives:

• Use VMware Workstation 12 to create and manager Virtual Machines (VMs).

• Install the CentOS 7 FULL INSTALL DVD as a new VM.

• Get Acquainted Using the Installed Virtual Machine

• Issue commands and custom Bash shell scripts to obtain installed Linux OS information.

• Disable Linux Kernel security enhancements and perform Linux system updates.

Minimum Required Materials

CentOS 7 FULL INSTALL DVD

USB key for backups (Minimum size: 16 GB)

Lab Log Book (labs 1 & 2)

Access to Instructions for Lab1 Since you will performing a full install on your computer, you cannot use that computer to simultaneously view instructions while you perform the full install. Here are some suggestions to make this process easier: Printout Lab1 instructions at home prior to performing Lab1 Use a smart-phone, notebook, or netbook computer to view lab instructions (highly recommended) If lab space availability is not an issue, use another computer termimal to view lab instructions while performing install Follow step-by-step instructions from your OPS235 instructor (if demonstrated by instructor)

My Toolkit (CLI Reference)

Package Management rpm yum

System Information hostname uname ps lsblk

Networking ifconfig netstat route nslookup

Miscellaneous grep wc pwd ls more file wget chmod scp vi

Hands-on Linux Utility Tutorials (practice) The following online tutorial will allow you to practice Linux commands that you learned from ULI101 as well as essential shell scripting skills. Login to your Matrix account, and issue the pathnames to run the online tutorial in Matrix: Linux Basics: /home/murray.saul/linux-basics Shell Scripting - Part I (Scripting Basics): /home/murray.saul/scripting-1 Using the vi Text Editor: /home/murray.saul/vi-tutorial

INVESTIGATION 1: CREATE AND INSTALL FIRST VIRTUAL MACHINE (centos1)

In this lab, you will learn how to install your Centos Full DVD as a virtual machine using the VMware application. Make certain to record your observations of this install in the comparison chart for centos1 in your lab2 logbook.

Part 1: Using VMware Workstation 12 to Create a New Virtual Machine (VM)

centos1 VM Details:

• Name: centos1
• Boot media / Installation: CentOS7 Full Install DVD
• Memory: 16GB
• Disk space: 40GB
• CPUs: 1

Main WMware application window in order to create a new Virtual Machine (VM)
comparison chart in lab2 logbook.	The Installation Summary screen provides flexibly when configuring to install on your computer.

Before you can install your Centos Full Install DVD onto your Virtual Machine, you must first create a storage container which is the virtual machine that will provide a platform for you to install the Centos operating system.

Perform the Following Steps:

1. Refer to this listing of installation screenshots if you need a reference:
   [ installation screenshots ]
   
2. Power up the computer in your Seneca lab in Windows and insert the CentOS 7 Installation DVD into the DVD drive.
3. On your Seneca computer workstation, run the VMware Workstation 12 application.
4. Click on the item labelled Create a New Virtual Machine.
5. Accept the Typical (default) for the Virtual Machine Configuration setting and click Next.
6. Select your CD/DVD player (/dev/cdrom) as the default physical device to install operating system from and click Next.
7. Make certain that the Guest Operating System is set to Linux and then click Next.
8. Change the Virtual Machine Name to read centos1 and then click Next.
9. Change the Disk Size to 40 GB and accept the default to Split virtual disk into multiple files and then click Next.
10. Take a few moments to review the final summary screen to make certain that you make the correct configuration selections for your new virtual machine. If you notice an configuration problem, you can click the Back button to make corrections. If all is correct, then click Finish to complete the creation of your first virtual machine.

Part 2: Install Centos on your Newly-Created VM

The next step is to perform a custom installation for your Centos7 virtual machine using the Centos7 Full DVD. Upon creation of your centos1 virtual machine, The VMware Workstation application will automatically simulate a "boot" to allow you to complete the installation process to create the Centos7 operating system on that virtual machine.

Perform the following steps:

1. Select from the installation menu: Install Centos7.
   
   Note: If you experience unreadable display after you boot into your installed system, you can redo the install, but select from the install menu: Troubleshooting and then select Install in Basic Graphics Mode.# Next, you will be prompted for a language. In the first screen, select language English with subselection English-Canada and then click the Continue button on the bottom right-hand screen.
2. The Install Summary should now appear. This screen allows the installer to customize their Centos7 system prior to installation.
3. Configure the following installation settings from the Install Summary Screen:
   
   

DATE & TIME:

• Click on the Map to select Toronto area (you may also select from the drop-down menu section)
• Click the DONE button at the top-left corner to finish and return to the Installation Summary screen.

NETWORK & HOSTNAME:

• Select the default Ethernet connection and click the button on the top right-hand side to change the setting from OFF to ON.
• At the bottom left-hand corner type the hostname: centos1 (all lowercase letters)
• Review your settings, then click the DONE button at the top-left corner to finish and return to the Installation Summary screen.

SOFTWARE SELECTION:

• Select the software packages labelled: Gnome Desktop
• Click the DONE button at the top-left corner to finish and return to the Installation Summary screen.
  
  

Mount Points and Linux File System Types Similar to other Operating Systems like windows fat / vfat / ntfs file system types, it is good to know a few common file system types in Linux for comparison: xfs:   Newer filesystem (fast transfer rates for large files, Journaling) ext4:   Newer filesystem supporting large files and Journaling (used in for this lab) ext2:   Stable filesystem popular for databases (no journaling)

Carefully verify partition mount-names and sizes prior to proceeding with install. Check installation screenshots link for verification.

INSTALLATION DESTINATION:

• From the installation summary screen, click Installation Destination.
• In the installation destination screen, select the destination option: I will configure partitioning and then click Done.
• The manual partitioning screen should appear.
• If you have used your hard disk for previous Linux (Centos) distributions, you should remove them. Click on the distribution, and for each partition, select the partition and click the remove button (minus sign) and confirm deletion.
• Change the option New mount points will use the following partition scheme from LVM to Standard Partition (you will not be using LVM for your centos1 machine).
• Before you proceed with creating partitions, let's see the partitions that we need to create for our virtual machine:
  • Primary Partitions (ext4):
    • 20GB for / (i.e. "root")
    • 10GB for /home
    • Swap Partition:
      • 16GB (Note: "swap" must be selected from the drop down menu)
    
    NOTE: Remember that the sizes are recorded in MB (eg. 30 GB = 30000 MB) and you should multiply GB by a factor of 1024 to get the correct size.
    (eg. 20 GB x 1024 = 20480 MB)
    
    

4. We will now create the root (/) partition. Click on the add button (plus) sign.
   
5. In the Add a New Mount Point screen, select / as the mount-point (either by typing or selecting from drop-down menu), and enter 20480 in for partition size and click Add Mount Point button.
6. You will return to the previous dialog box.
   For the / partition, change the file-system type from xfs to ext4 and make certain that the Device Type is set to Standard Partition (not LVM). You need to repeat this procedure for the /home and /var/lib/libvirt/images partitions as well).
7. Repeat the same steps above for the /home partition.
8. Recheck each of the created partitions, and make certain that the file-system type is set to ext4 and the Device Type is set to Standard Partition.
9. Finally, add a swap partition (Mount Point: swap) for 16 GB.
10. Check that your partition settings are correct (you can ask your instructor or lab monitor to confirm), and then click Done (possibly twice) in order to proceed
    
    NOTE: If there is an error message associated with your created partitions, you may need to add a /boot/efi partition (as a new mount). The capacity should be: 2954MB (i.e. 2,954 MB). Once finished, click Done.
    
    
11. A Summary of Changes screen will appear to show the partitioning operations that will be created. Click the Accept Changes and click Begin Installation in the Installation Summary screen to proceed with the installation.
12. Start timing your centos1 virtual machine installation.

Part 3: Completing the Installation

This screen indicates that installation is complete. You should remove the install DVD and confirm Centos7 boots from your removable hard drive.

Perform the Following Steps:

1. During the installation process, you will required to create a root password (for administration access) and create a regular user account. Click on Root Password and enter your root password. Think of an appropriate password and record that password somewhere in case you forget! An indicator will appear to show you how secure your password is. Retype your root password and click Done (you may have to click Done twice if your password is not considered to be a strong password).
2. You need to create a regular user account. This account will be used to graphical log into your host machine. It is never recommended to graphically log into a graphical Linux/Unix system as root. It is better to log into a regular user account, then run a command to login as root (you will learn how to do this later in this lab).
3. Click User Creation and enter your full name, username, and an appropriate password (and confirm password). Click Done to finish (click twice if password is not considered to be a strong password).
4. Remember to record this host installation information in the installation comparison chart in the lab2 logbook.
5. When installation is complete, you will notice a message at the bottom of the screen stating: CentOS is now successfully installed and ready for you to use!
6. Click the Reboot button. Your DVD will briefly open in the DVD drive bay. Make certain to remove this installation DVD so that Centos will boot from your hard drive.
7. After the system reboots, a boot menu should briefly appear, then prompt the user to accept the License Information (this is only a one-time occurrence).
   In order to accept the license agreement, issue the following keystrokes:
   
   1 followed by ENTER (to select the license agreement prompt
   2 followed by ENTER (to accept the license agreement)
   c followed by ENTER (to save the selection)
   c followed by ENTER (a second time to continue booting into the system)
   
   
8. The system should then graphically prompt the user to login with their regular user account. Click on your regular user account name and enter your regular user password.
   
   
9. The last phase of the installation process should now run:
   • Confirm English as the default input source and click Next.
   • Skip the creation of online accounts by clicking Next.
   • Start using your installed Linux system by clicking Start Using CentOS Linux.
   
   
10. Stop timing your installation and note the amount of time that your installation took to perform. Also take the time to fill in the centos1 section of the installation comparison chart in your lab2 logbook.
11. Open a web-browser and check to see if you can connect to the Internet.

Part 4: Backing up Virtual Machines to a USB Key

VMs MUST be Backed up to USB key before Leaving Seneca Labs
It is absolutely essential that you backup your virtual machine image to USB key after completing your virtual machine session at Seneca Labs, or you will lose your work! Make certain to PROPERLY follow the instructions to copy and archive the required files to your USB key as opposed to using your USB key directly, which can cause problems.

Perform the following Steps:

1. x
2. Proceed to Investigation 2 to obtain basic information from your newly installed Centos Host machine.

Answer Investigation 1 observations (all parts and questions) in your lab log book.

INVESTIGATION 2: GETTING ACQUAINTED WITH YOUR VM & CREATING SHELL SCRIPTS

For the remainder of this lab, we will be using the centos1 virtual machine that we installed in Investigation 1.

First, we will focus on using the virtual machine and become familiar with some command VM operations like switching between the full-screen and window modes. We will also learn to turn-off the screen-saver settings so you do NOT have to periodically re-issue passwords to gain access to your account (although it is a good security feature to consider in the future beyond this lab). We will also show you how to temporarily log in as the root account in order to perform tasks that are only allows for a Linux administrator.

Finally, we will continue using Shell Scripting to help automate routine tasks. For lab1, this will be creating shell scripts in order to generate information regarding the Linux system that we just installed. It would make sense that not only should a system administrator have access to hardware specifications for the computers that they support, but also information regarding the Linux operating system.

Part 1: Managing your Virtual Machine

VMware Workstation Toolbar

The VM Workstation taskbar is useful when in full-screen mode to perform common virtual machine management tasks.

The VM Workstation application allows virtual machines to run in windows or full screen mode (which is toggled by pressing the key combination: ALT-CTRL-ENTER). You can press the key-combination ALT-CTRL in order to return to your host computer system (i.e. running the VM Workstation application. The VM Workstation Toolbar (displayed on right-hand side) can be accessed while in full screen mode when the mouse pointer is at the top of the virtual machine display.

Below is a table with some useful toolbar buttons and their purpose:

Button(s)	Purpose
	Toggle between auto-hide and always show toolbar
	Text-based menu for common operations
	Common Guest VM Operations (Left to Right):Shutdown, Suspend, Start, Restart
	Snapshot (i.e. Restore Points) (left to Right): Take new Snapshot, Revert to Parent Snapshot, Manage Snapshots
	Exit Full Screen mode
	Running Virtual Machines

Take a few minutes acquainting yourself with toggling into Full Screen mode, using the VM Workstation Tool-bar in auto-hide and always-show mode.

We will not be using the other features in this lab, but it is a good idea to make appropriate notes of these Tool-bar buttons and purposes in your lab logbook.

Turning Off Locked Screen-saver

Your system automatically enables a screen-saver application which is a useful security tool to prevent unauthorized viewing of information on a terminal after a certain amount of inactivity. Turning-off the locked screen-saver for this (and other) virtual machine can be useful when waiting for your instructor to come over to "sign-off" your computer lab without having to re-issue user passwords.

If you find this feature annoying and want to turn it off or adjust the idle time perform the following steps:

• Click on your username at the top right-hand screen
• Select Settings from the drop-down menu.
• Click the Power icon located in the Settings Dialog Box
• Change the amount of time in the Power Saving section to Never or a longer period of time
• Close the Settings Dialog box.

Part 2: Common Post-Install Tasks & Automating Routine Tasks with Shell Scripts

Accessing the Administration Account (root) Many administrative tasks require the root administrative account. There are many ways to access this administration account: Login: root (enter root password) Switch User to root (without login): su: Remains in regular user's directory, does not run root's startup script(s). su - : Changes to root's home directory (/root) and runs root's start script(s).

Accessing Administrative Priviledges

Navigate through your Graphical CentOS system, locate and run a terminal program (in order to issue Linux commands).

Issue and record the commands used and the output generated in each of the following steps:

1. With older (ancient) versions of Linux, a user once may have been allowed to login to their graphical Linux system using root as their user-name and their root password. This has been determined to be a security risk and that option has been removed with many or all Linux operating systems.
2. Therefore, from this point onwards, you will be logging into your regular user account instead and issuing a command to login as the root user.
3. Refer to the Information box regarding how to access the admin account from the command line.
4. Issue the command su Issue the pwd and whoami commands to confirm your directory pathname. When finished logout of this account.
5. Issue the command su - Issue the pwd and whoami commands to confirm your directory pathname. What do you notice are the main differences between using su versus using su - ?
6. An installation log file called /var/log/anaconda/packaging.log has been created to record the installation of your centos1 machine. This file is an ASCII file which can be viewed with the more command.
7. 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 that are labelled "Installing" in the installation log file:

grep -i packaging /var/log/anaconda/packaging.log | wc -l

Using Bash Shell Scripts

Bash Shell Reference Guide: She-bang line: #!/bin/bash Shell scripts have evolved of the past 40 years. To avoid running a newer shell script on an older shell, it is recommended to force running the shell script in the correct shell. In order to do this, on the first line at the very beginning of the shell script, you add the #! (# as in "shhhh" - a comment, and ! is referred to as "bang" run a commmand: in this case, run the command: /bin/bash). You can issue the Linux command which bash to get the correct location. If there is no bash shell on that machine, the shell script will not run (as a precaution - the Linux admin will know how to make a fix to the shell script if required). Variables: There are 3 types of variables that can be used in shell scripting: ENVIRONMENT (eg. $USER), user-defined ($varName), and positional parameters (eg. $1, $2... containing arguments after shell script or by using set command (eg. set $(ls) ). Using dollar sign ($) in front of variable expands the value assigned. Command Substitution: A very useful trick to take output from a command to be used as an argument for another command. Examples include: file $(ls) set $(ls);echo $#;echo $* echo "hostname: $(hostname)" Logic Control Flow Statements: The test command can be used to see if a condition is true or false (i.e. test $USER = "root") . The $? special shell variable stores the result (zero if true, non-zero if false). Square brackets [ ] can be used to represent the test command with the condition inside the brackets (spaces separating brackets).Can use if / if-else / if-elif-else statements with brackets. The exit command can be used to terminate the shell script with a false value. Examples if [ $USER = "root" ] then  echo "You must be root" >&2  exit1 fi # For number comparison: use: # -gt,-ge, -lt, -le, -eq, -ne if [ $age -gt 65 ] then  echo "retire" else  echo "don't retire" fi if [ $grade -gt 79 ] then  echo "You get Good Mark" elif [ $grade -gt 49 ] then  echo "You pass" else  echo "You fail" fi

Perform the Following Steps:

1. Issue that command displayed above. Does it work? If not, what account do you think you should be in? When you get the command working record this important information regarding commands and the admin account in your lab logbook.
2. Using the rpm command: you can also use the following commands to list all the installed packages, and the total number of packages installed:

rpm -q -a

rpm -q -a | wc -l

rpm -qa | wc -l

10. The -q option means query, and the -a option means all (in other words, query all installed software packages). Did you get the same number of packages from the above two methods?
11. 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 packaging.log), you can list all the files that were installed from the package by using the following command:

rpm -q -l gedit

12. Issue the following command to obtain the total number of files installed for gedit:
    
    

rpm -ql gedit | wc -l

13. Using what you learned in steps 3, 4, and 7, get a count of the total number of files installed by all of the software packages on your system.
14. How can you explain why this number is a lot larger than the total number of packages installed? Record your answer in your lab logbook.

Pathname for USB Stick The default mount location has been changed in linux distributions newer than CentOS. So while we will get /media/usb-device-name, in newer distributions you'll see /run/media/userloginid/usb-device-name

1. To find out the name that you have assigned to your Linux system, enter the command: hostname
2. To find out the kernel version of your GNU/Linux workstation and the date it was created, enter the command:
   uname -rv
3. To find out all the system processes running on your GNU/Linux workstation, enter the command: ps -ef
4. We will now collect networking information for your installed system.
5. To check the network configuration settings obtained from the DHCP server, run the following commands, describing the output in your log book:

ifconfig

route -n

nslookup (at the nslookup prompt, enter the word server and record the output. Type exit to leave nslookup).

8. Find the following information in the output of the above commands:

MAC address of the ethernet network interface

Subnet mask

The IP address (assigned to you by the DHCP server)

The default gateway

The DNS nameserver

9. Run the commands hostname, uname -rv, ps -ef, ifconfig, and route -n redirecting the output to add to a file in root's home directory called system.txt.
10. Copy the installation log file /var/log/anaconda/packaging.log and the file system.txt to a USB memory key, or scp to your matrix account as a backup.

You may have learned about creating and running Bash Shell Scripts in your ULI101 course. Shell scripts help Linux users and system administrators to automate repetitive tasks to become more efficient and to help them save time. You will be reviewing and building a basic Bash Shell script to generate information reports for your newly-installed Linux host machine. Take time to view Shell Scripting Tips which are located on the right-hand side.

If you require additional practice in creating shell scripts and using the vi text editor, run the commands in your Matrix account:

• /home/murray.saul/vi-tutorial
• /home/murray.saul/scripting-1

Perform the following steps:

1. Make certain to log out of your root account and remain as a regular user.
2. Open a Shell terminal and use a text editor (such as vi or nano) to create a Bash Shell script called: myreport.bash in your current directory.
3. Copy and paste the text below into your vi editing session for your file report.bash
   (how do you copy and paste efficiently in Linux?)
   


#!/bin/bash

# Author: *** INSERT YOUR NAME ***
# Date: *** CURRENT DATE ***
#
# Purpose: Creates system info report
#
# USAGE: ./myreport.bash

if [ $USER != "root" ] # only runs if logged in as root
then
 echo "You must be logged in as root." >&2
 exit 1
fi


4. Save your editing session, assign the myreport.bash file read and execute permissions (at least for the owner) and run by typing:
   ./myreport.bash
5. Did it run? If not what do you think you need to do in order to run the Bash Shell Script?
6. Issue the command su - and run the script from the regular user's home directory (not root's home directory):
   ~regularuserid/myreport.bash
7. Did it work?
8. Reopen your text-editing session for ~regularuserid/myreport.bash and add the following lines of code to the bottom of the shell script file:

# Create report title

echo "SYSTEM REPORT" > /root/report.txt
echo "Date: $(date +'%A %B %d, %Y (%H:%M:%p)')" >> /root/report.txt
echo >> /root/report.txt


8. Save and run the bash shell script. View the contents of the file called report.txt that was generated (I hope you are using the up arrow key to issue previously issued commands in order to save time!). Notice how the redirection symbol > is used at the beginning of the report, and then the other redirection symbol >> is used to help "grow" the report with the other content.
9. The only remaining content of the report would be the system information. We can use a shell scripting trick called "command substitution" $( .. ) in order place results from an command to be used by another command (like echo). Re-edit the shell script and add the following code at the bottom of the shell script file:

echo >> /root/report.txt
echo "Hostname: $(hostname)" >> /root/report.txt
echo >> /root/report.txt
echo "Kernel Version: $(uname -rv)" >> /root/report.txt
echo >> /root/report.txt


10. Save, run the script, and view the report.txt contents (are you using tip that was given to save time?).
11. Edit the shell script and include output from the ps aux and ifconfig commands (with appropriate titles). Remember to redirect that output to add to the bottom of the file!
12. Save, run and confirm that the shell script is working correctly.
13. What would be the use of keeping this shell script as a Linux system administrator?

14. Here are some more "complex" Bash Shell scripts, that perform the same task. Although you are not require to understand some of these other tricks, it is recommended that you view the contents of the scripts and save them for future consideration or exmaples.
15. The wget command can be used to quickly download files from the Internet. Issue the following command:
    wget https://scs.senecac.on.ca/~murray.saul/text-report.bash
16. Verify that the file text-report.bash was downloaded to your current directory.
17. Assign read and execute permissions for this file by issuing the command: chmod u+rx text-report.bash
18. Run this Bash Shell script by issuing the command: ./text-report.bash
19. Check to see if it created a report in your current directory. What is the purpose of the report?
20. Use the vi text editor to view the contents of the file text-report.bash. Can you understand how this script works?
    
    
21. Use the wget command to download, study, and run the following shell scripts on-line:

    https://scs.senecac.on.ca/~murray.saul/report.bash
https://scs.senecac.on.ca/~murray.saul/report3.bash

22. Try to understand what these Bash Shell scripts do.
23. You have completed lab1. Proceed to Completing The Lab, and follow the instructions for "lab sign-off".

Disable SELinux and Perform Software Updates

SELinux stands for Security-Enhanced Linux. It is a component that helps to better secure the system to protect against intrusion (hackers). SELinux is enabled upon the default install of CentOS. SELinux can be a good thing, if you take care of it and know how it works. For this course it is strongly recommended that you disable SELinux by default because we won't have the time to reconfigure it every time the labs make it necessary.

Perform the following Steps:

1. Disabling SELinux is quite simple, just edit the file /etc/selinux/config and set SELINUX to disabled.
2. Add additional text regarding disabling SELinux.
3. The CentOS software is updated frequently to add features, fix bugs, and upgrade security. Perform a system update to get the latest versions of the packages installed: Start the Firefox web browser, turn off popup window blocking (select Edit, Preferences, then select the Content tab and uncheck the box to Block Popups), then return to your web-browser, load a page, and when prompted, login to SeneNET.
4. Make certain that you have at least 30 minutes available in your lab-time prior to performing a system update. Never abort a system update since it may damage your system files and render your host mahcine inoperable!
5. Open a terminal and type su to start a shell as root. Enter the command yum update This will download and install all of the packages that have been updated since the installation DVD image was created. If you complete this command at Seneca it should run quite fast as Seneca College hosts a CentOS Repository mirror (a copy of all of the current CentOS packages, on a local web server).

Download and Run Lab1 Checking Script

x

Perform the Following Steps:

Answer Investigation 2 observations (all parts and questions) in your lab log book.

LAB 1 SIGN-OFF (SHOW INSTRUCTOR)

Students should be prepared with all required commands (system information) displayed in a terminal (or multiple terminals) prior to calling the instructor for signoff.

Arrange evidence (command output) for each of these items on your screen, then ask your instructor to review them and sign off on the lab's completion:

✓ Output of lsblk command showing correct partition names and sizes

✓ Contents of /etc/fstab file confirming partitions file types are ext4

✓ Correct IP address and MAC address

✓ Default route (gateway)

✓ DNS name server IP Address

✓ Contents of your report.bash shell script

✓ proof of yum update performed on centos1

✓ SELinux is disabled on centos1

✓ lab1 notes and first column of Comparison Chart in lab2.

Practice For Quizzes, Tests, Midterm & Final Exam

1. How many packages were installed?
2. How many files (correct to the nearest hundred) were installed?
3. How many users were created automatically on your system (regular, admin)?
4. List 2 ways that you can access your root account
5. What is the difference between the commands su and su -  ?
6. What is the home directory for the user "root"?
7. How do you determine the host name of your GNU/Linux workstation?
8. What command can display the NIC's MAC address?
9. What command is used to get a list of running processes on your newly-installed system?
10. What is the command to copy files to your USB key?
11. How can Shell Scripts be used to help automate a task performed in lab1?