Difference between revisions of "OPS235 Lab 1 - CentOS7"
Line 161: | Line 161: | ||
#Exit your current account. Which account are you now using? | #Exit your current account. Which account are you now using? | ||
#Refer to the Information box regarding how to access the admin account from the command line. | #Refer to the Information box regarding how to access the admin account from the command line. | ||
− | #Issue the command <b><code><span style="color:#3366CC;">su </span></code></b> Issue the '''pwd''' and '''whoami''' commands to confirm your directory pathname. When finished logout of this account. | + | #Issue the command <b><code><span style="color:#3366CC;font-size:1.2em;">su </span></code></b> Issue the '''pwd''' and '''whoami''' commands to confirm your directory pathname. When finished logout of this account. |
− | #Issue the command <b><code><span style="color:#3366CC;">su - </span></code></b> Issue the '''pwd''' and '''whoami''' commands to confirm your directory pathname. Remain in this account for the remainder of this lab. | + | #Issue the command <b><code><span style="color:#3366CC;font-size:1.2em;">su - </span></code></b> Issue the '''pwd''' and '''whoami''' commands to confirm your directory pathname. Remain in this account for the remainder of this lab. |
# An installation log file called <code>'''/var/log/anaconda/anaconda.packaging.log'''</code> has been created to record the installation of your c7host machine. This file is an ASCII file which can be viewed with the <code>'''more'''</code> command. | # An installation log file called <code>'''/var/log/anaconda/anaconda.packaging.log'''</code> has been created to record the installation of your c7host machine. This file is an ASCII file which can be viewed with the <code>'''more'''</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 that are labelled "Installing" in the installation log file: | # 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: | ||
− | :: <b><code><span style="color:#3366CC;">grep ________________ ________________ | wc -l'''</span></code></b> | + | :: <b><code><span style="color:#3366CC;font-size:1.2em;">grep ________________ ________________ | wc -l'''</span></code></b> |
<ol> | <ol> | ||
<li value="3">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 installed:</li> | <li value="3">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 installed:</li> | ||
</ol> | </ol> | ||
− | ::<b><code><span style="color:#3366CC;">rpm -q -a'''</span></code></b> | + | ::<b><code><span style="color:#3366CC;font-size:1.2em;">rpm -q -a'''</span></code></b> |
− | ::<b><code><span style="color:#3366CC;">rpm -q -a | wc -l'''</span></code></b> | + | ::<b><code><span style="color:#3366CC;font-size:1.2em;">rpm -q -a | wc -l'''</span></code></b> |
− | ::<b><code><span style="color:#3366CC;">rpm -qa | wc -l'''</span></code></b> | + | ::<b><code><span style="color:#3366CC;font-size:1.2em;">rpm -qa | wc -l'''</span></code></b> |
<ol> | <ol> | ||
<li value="4">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?</li> | <li value="4">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?</li> | ||
<li>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 command:</li> | <li>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 command:</li> | ||
</ol> | </ol> | ||
− | ::<b><code><span style=" pointer-events:none;cursor:default;color:#3366CC;">rpm -q -l package_name</span></code></b><br />(where '''package_name''' represents the name of the ''application'' or ''package'') | + | ::<b><code><span style=" pointer-events:none;cursor:default;color:#3366CC;font-size:1.2em;">rpm -q -l package_name</span></code></b><br />(where '''package_name''' represents the name of the ''application'' or ''package'') |
<ol> | <ol> | ||
<li value="6">This combines the <code>'''-q'''</code> (query) option with the <code>'''-l'''</code> (list filenames) option</li> | <li value="6">This combines the <code>'''-q'''</code> (query) option with the <code>'''-l'''</code> (list filenames) option</li> | ||
<li>You can pipe the outupt through <code>'''wc -l'''</code> to count the number of lines:</li> | <li>You can pipe the outupt through <code>'''wc -l'''</code> to count the number of lines:</li> | ||
</ol> | </ol> | ||
− | ::<b><code><span style=" pointer-events:none;cursor:default;color:#3366CC;">rpm -ql package_name| wc -l</span></code></b> | + | ::<b><code><span style=" pointer-events:none;cursor:default;color:#3366CC;font-size:1.2em;">rpm -ql package_name| wc -l</span></code></b> |
<ol> | <ol> | ||
<li value="8">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.</li> | <li value="8">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.</li> | ||
Line 196: | Line 196: | ||
| | | | ||
− | #To find out the name that you have assigned to your Linux system, enter the command: <b><code><span style="color:#3366CC;">hostname</span></code></b> | + | #To find out the name that you have assigned to your Linux system, enter the command: <b><code><span style="color:#3366CC;font-size:1.2em;">hostname</span></code></b> |
− | #To find out the kernel version of your GNU/Linux workstation and the date it was created, enter the command:<br><b><code><span style="color:#3366CC;">uname -rv</span></code></b> | + | #To find out the kernel version of your GNU/Linux workstation and the date it was created, enter the command:<br><b><code><span style="color:#3366CC;font-size:1.2em;">uname -rv</span></code></b> |
− | #To find out all the system processes running on your GNU/Linux workstation, enter the command: <b><code><span style="color:#3366CC;">ps -ef</span></code></b> | + | #To find out all the system processes running on your GNU/Linux workstation, enter the command: <b><code><span style="color:#3366CC;font-size:1.2em;">ps -ef</span></code></b> |
#We will now collect networking information for your installed system. Your system may not be automatically connected to Seneca's network. Locate the network icon (on top right-hand panel). Click on that icon, and select: '''system eth0''' | #We will now collect networking information for your installed system. Your system may not be automatically connected to Seneca's network. Locate the network icon (on top right-hand panel). Click on that icon, and select: '''system eth0''' | ||
# Open a web-browser and log into Seneca's wired network. You will need to perform this set every time you start a new session with your computer to perform future labs. | # Open a web-browser and log into Seneca's wired network. You will need to perform this set every time you start a new session with your computer to perform future labs. | ||
#Open a shell terminal. | #Open a shell terminal. | ||
#To check the network configuration settings obtained from the DHCP server, run the following commands, describing the output in your log book: | #To check the network configuration settings obtained from the DHCP server, run the following commands, describing the output in your log book: | ||
− | ::: <b><code><span style="pointer-events: none;cursor: default;color:#3366CC;">ifconfig</span></code></b> | + | ::: <b><code><span style="pointer-events: none;cursor: default;color:#3366CC;font-size:1.2em;">ifconfig</span></code></b> |
− | ::: <b><code><span style="pointer-events: none;cursor: default;color:#3366CC;">route -n</span></code></b> | + | ::: <b><code><span style="pointer-events: none;cursor: default;color:#3366CC;font-size:1.2em;">route -n</span></code></b> |
− | :::<b><code><span style="pointer-events: none;cursor: default;color:#3366CC;">nslookup</span></code></b> (at the > prompt, enter the word "server" (do not type the quotes) and record the output. Type exit to leave nslookup). | + | :::<b><code><span style="pointer-events: none;cursor: default;color:#3366CC;font-size:1.2em;">nslookup</span></code></b> (at the > prompt, enter the word "server" (do not type the quotes) and record the output. Type exit to leave nslookup). |
<ol><li value="8">Find the following information in the output of the above commands:</li></ol> | <ol><li value="8">Find the following information in the output of the above commands:</li></ol> | ||
− | ::: <b><code><span style="pointer-events: none;cursor: default;color:#3366CC;">MAC address</span></code></b> of the ethernet network interface | + | ::: <b><code><span style="pointer-events: none;cursor: default;color:#3366CC;font-size:1.2em;">MAC address</span></code></b> of the ethernet network interface |
− | :::<b><code><span style="pointer-events: none;cursor: default;color:#3366CC;">Subnet mask</span></code></b> | + | :::<b><code><span style="pointer-events: none;cursor: default;color:#3366CC;font-size:1.2em;">Subnet mask</span></code></b> |
− | ::: <b><code><span style="pointer-events: none;cursor: default;color:#3366CC;">The IP address </span></code></b> (assigned to you by the DHCP server) | + | ::: <b><code><span style="pointer-events: none;cursor: default;color:#3366CC;font-size:1.2em;">The IP address </span></code></b> (assigned to you by the DHCP server) |
− | ::: <b><code><span style="pointer-events: none;cursor: default;color:#3366CC;">The default gateway</span></code></b> | + | ::: <b><code><span style="pointer-events: none;cursor: default;color:#3366CC;font-size:1.2em;">The default gateway</span></code></b> |
− | ::: <b><code><span style="pointer-events: none;cursor: default;color:#3366CC;">The DNS nameserver</span></code></b> | + | ::: <b><code><span style="pointer-events: none;cursor: default;color:#3366CC;font-size:1.2em;">The DNS nameserver</span></code></b> |
<ol><li value="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'''.</li><li>Copy the installation log file <code>'''/var/log/anaconda/anaconda.packaging.log'''</code> and the file '''system.txt''' to a USB memory key, or '''scp''' to your matrix account as a backup.</li></ol> | <ol><li value="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'''.</li><li>Copy the installation log file <code>'''/var/log/anaconda/anaconda.packaging.log'''</code> and the file '''system.txt''' to a USB memory key, or '''scp''' to your matrix account as a backup.</li></ol> | ||
Line 234: | Line 234: | ||
# Add additional text regarding disabling SELinux<br><br> | # Add additional text regarding disabling SELinux<br><br> | ||
#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. | #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. | ||
− | #Open a terminal and type <b><code>su</code></b> to start a shell as root. Enter the command <b><code><span style=" pointer-events:none;cursor:default;color:#3366CC;">yum update</span></code></b> 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). | + | #Open a terminal and type <b><code>su</code></b> to start a shell as root. Enter the command <b><code><span style=" pointer-events:none;cursor:default;color:#3366CC;font-size:1.2em;">yum update</span></code></b> 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). |
|width="40%" |{{Admon/important|SELinux|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.}} | |width="40%" |{{Admon/important|SELinux|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.}} | ||
Line 243: | Line 243: | ||
[[Image:lab1-script-1.png|thumb|right|175px|When executed as '''root''' or using '''sudo''' command, allows for automatically performing routine tasks such as generating information of a newly installed Linux server]] | [[Image:lab1-script-1.png|thumb|right|175px|When executed as '''root''' or using '''sudo''' command, allows for automatically performing routine tasks such as generating information of a newly installed Linux server]] | ||
#You may have learned about creating and running Bash Shell Scripts in your ULI101 course. Shell scripts help Linux users and system administrators to automatic repetitive tasks to become more efficient and to help them save time. | #You may have learned about creating and running Bash Shell Scripts in your ULI101 course. Shell scripts help Linux users and system administrators to automatic repetitive tasks to become more efficient and to help them save time. | ||
− | #The <b><code>wget</code></b> command can be used to quickly download files from the Internet. Issue the following command:<blockquote><b><code><span style="pointer-events: none;cursor: default;color:#3366CC;">wget https://scs.senecac.on.ca/~murray.saul/text-report.bash</span></code></b></blockquote> | + | #The <b><code>wget</code></b> command can be used to quickly download files from the Internet. Issue the following command:<blockquote><b><code><span style="pointer-events: none;cursor: default;color:#3366CC;font-size:1.2em;">wget https://scs.senecac.on.ca/~murray.saul/text-report.bash</span></code></b></blockquote> |
#Verify that the file '''text-report.bash''' was downloaded to your current directory. | #Verify that the file '''text-report.bash''' was downloaded to your current directory. | ||
#Assign read and execute permissions for this file by issuing the command: <b><code>chmod u+rx text-report.bash</code></b> | #Assign read and execute permissions for this file by issuing the command: <b><code>chmod u+rx text-report.bash</code></b> | ||
Line 249: | Line 249: | ||
#Check to see if it created a report in your current directory. What is the purpose of the report? | #Check to see if it created a report in your current directory. What is the purpose of the report? | ||
#Use the <b>vi</b> text editor to view the contents of the file <b>text-report.bash</b>. Can you understand how this script works?<br><br> | #Use the <b>vi</b> text editor to view the contents of the file <b>text-report.bash</b>. Can you understand how this script works?<br><br> | ||
− | #Use the <b><code>wget</code></b> command to download, study, and run the following shell scripts on-line:<blockquote><b><code><span style=" pointer-events:none;cursor:default;color:#3366CC;">https://scs.senecac.on.ca/~murray.saul/report.bash<br>https://scs.senecac.on.ca/~murray.saul/report3.bash</span></code></b></blockquote> | + | #Use the <b><code>wget</code></b> command to download, study, and run the following shell scripts on-line:<blockquote><b><code><span style=" pointer-events:none;cursor:default;color:#3366CC;font-size:1.2em;">https://scs.senecac.on.ca/~murray.saul/report.bash<br>https://scs.senecac.on.ca/~murray.saul/report3.bash</span></code></b></blockquote> |
#Try to understand what these Bash Shell scripts do. | #Try to understand what these Bash Shell scripts do. | ||
#You have completed lab1. Proceed to Completing The Lab, and follow the instructions for "lab sign-off". | #You have completed lab1. Proceed to Completing The Lab, and follow the instructions for "lab sign-off". |
Revision as of 07:41, 29 March 2015
Contents
LAB PREPARATION
Purpose / Objectives of Lab 1
You need to install a Linux OS to be a host or "platform" to install and use other Linux VMs (Virtual Machines) during this course.
The Linux OS you will be installing in this lab will be a Host Machine (hostname: c7host) that will allow you to run Virtualization Software to create 3 separate virtual machines (to be performed in lab2). It is important to install this host machine correctly since other labs will depend on the stability of this host machine.
Main objectives:
- Correctly install the CentOS 7 FULL INSTALL DVD (not LIVE DVD) on your removable hard disk.
- Record installation characteristics of CentOS 7 FULL INSTALL in a chart (contained in lab2 logbook chart) to compare with other installation methods performed in lab2.
- Verify correct settings prior to proceeding with host installation stages.
- Obtain Linux server information after installation to create a software asset report for later access.
- Disable Linux Kernel security enhancements to allow easier internal networking connections (to be reactivated in a later lab).
- Observe that Bash Shell Scripts can automate routine tasks.
Required Materials / Lab Preparation
My Toolkit (CLI Reference)
Package Management | System Information | Networking | Miscellaneous
grep
|
INVESTIGATION 1: CREATE HOST MACHINE (c7host)
For the next 3 investigations, you will learn how to install your Centos Full DVD onto your removable hard disk. You will customize your install to setup several separate partitions: root (/), /home, /var/lib/libvirt/images (to store virtual machine images to be created in lab2), and a swap partition.
Make certain to record your observations of this install in the comparison chart for c7host in your lab2 logbook.
Part 1: Start Installation
|
Part 2: Custom Partitioning
|
Part 3: Completing the Installation
- 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 strong).
- 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 regualr user account, then run a command to login as root (you will learn how to do this later in this lab.
- Click User Creation and enter your full name, username, and an appropriate password (and confirm password). Click Done to finish.
- Remember to record this host installation information in the comparison chart in lab2.
- 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!
- 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.
- After the system reboots, login by clicking on your account name and entering the regular user password.
- The last phase of the installation process should now run:
- Click Accept to confirm you will abide by the License and click Done.
- Accept defaults to participate running KDump application that will report errors to developers for improvements to Centos7.
- Select English as the default input source.
- Quickly view Getting Started Resources, then close the help window.
- 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: OBTAINING HOST MACHINE SYSTEM INFORMATION
Part 1: Obtaining Package Management / Package Information
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:
|
Part2: Obtaining System Information
|
Answer the Investigation 3 observations / questions in your lab log book.
INVESTIGATION 3: LOOKING AHEAD
Part 1: Disable SELinux and Perform Software Updates
|
Part 2: Automating Routine Tasks (Shell Scripting)
- You may have learned about creating and running Bash Shell Scripts in your ULI101 course. Shell scripts help Linux users and system administrators to automatic repetitive tasks to become more efficient and to help them save time.
- 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
- Verify that the file text-report.bash was downloaded to your current directory.
- Assign read and execute permissions for this file by issuing the command:
chmod u+rx text-report.bash
- Run this Bash Shell script by issuing the command:
./text-report.bash
- Check to see if it created a report in your current directory. What is the purpose of the report?
- Use the vi text editor to view the contents of the file text-report.bash. Can you understand how this script works?
- 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 - Try to understand what these Bash Shell scripts do.
- You have completed lab1. Proceed to Completing The Lab, and follow the instructions for "lab sign-off".
COMPLETING THE LAB / INSTRUCTOR SIGN-OFF
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:
- ✓ Installed package count
- ✓ Output of lsblk command showing correct partition names and sizes
- ✓ Correct IP address and MAC address
- ✓ Default route (gateway)
- ✓ DNS name server IP Address
- ✓ lab1 notes and first column of Comparison Chart in lab2.
ADDITIONAL PRACTICE
- How many packages were installed?
- How many files (correct to the nearest hundred) were installed?
- How many users were created automatically on your system (do not count your learn account)?
- What is your learn account's UID and GID?
- What is your learn account's home directory?
- What is the home directory for the user "root"?
- How do you determine the host name of your GNU/Linux workstation?
- What command can display the NIC's MAC address?