Difference between revisions of "OPS235 Lab 3 - CentOS7"
Line 34: | Line 34: | ||
|} | |} | ||
− | |||
− | |||
− | |||
− | |||
Revision as of 07:47, 28 March 2015
Contents
- 1 LAB PREPARATION
- 2 Software Package Management
- 3 Completing the lab
LAB PREPARATION
Purpose / Objectives of Lab3
In this lab, you are going to help conserve disk space by learning how to compress and decompress files that are stored on your computer server. In addition, you will learn alternative methods of how to install programs.
Topics include:
- Creating and using archive files (tar and tar.gz)
- Compiling software packages from source code
- Install applications using various methods:
- Decompressing source code archive, and compiling source code
- Use yum utility to install software from local programs (on DVD drive)
- Use yum utility to install software from repositories (online storage areas)
- Demonstrating the use of Bash Shell scripts to automate routine tasks
Required Materials / Lab Preparation
Linux Command Online Reference
Each Link below displays online manpages for each command (via http://linuxmanpages.com):
Archiving Utilities: | Service Management Utilities: | |
|
Software Package Management
Investigation 1: How do you query the RPM database?
RPM maintains a database of installed software. This information is very useful to system administrators. In the previous lab you queried that database using RPM with the -q argument. When you query the RPM database, you can separately specify:
- Do an operational task on one or more packages (like installing or removing a package), using a select-option
- What information you want about those packages, using a query-option
Perform the following steps:
(Perform investigations 1 - 3 in your host machine (c6host)
- Using information from the man page for
rpm
, fill in this information:
Option | Meaning | Select or query option? | Example command |
---|---|---|---|
-a | Select all packages | select-option | |
-l | |||
-i | Show the package information. | ||
-f filename | |||
packagename | Select just this package | select-option |
Answer the Investigation 1 observations / table contents in your lab log book.
Investigation 2: How do you install and remove software with RPM?
- Use the graphical file manager (Nautilus) to change to the directory on your Installation DVD. Go to the sub-directory called Packages. It should contain a file called:
lynx-2.8.6-27.el6.x86_64.rpm
- Execute the following command:
rpm -i lynx-2.8.6-27.el6.x86_64.rpm
- Issue an RPM query to check that lynx is installed. Record this command in your lab log-book.
- Issue the following command:
rpm -e lynx
- Issue an RPM query to verify that lynx is no longer installed. Record this command in your lab log-book.
- Issue the following command:
rpm -i elinks-0.12.rpm
. Did it work? Explain in your lab log-book why this command may not have worked.
Answer the Investigation 2 observations / questions in your lab log book.
Investigation 3: How do you install and remove software with yum?
- Change to your home directory.
- Issue the command:
yum install elinks
and answery
to the question about installation.- Where did yum get the elinks software?
- Why could yum install elinks when rpm couldn't?
- Issue an RPM query to verify that elinks is installed. Record this command in your lab log-book.
- Issue the command:
yum remove elinks
- Issue an RPM query to verify that elinks is no longer installed. Record this command in your lab log-book.
- Issue this command:
yum info cups
- Based on the result, do you think that cups is a useful package for your system? If not, try removing it.
- Unused and unneeded software can present a security risk and ties up disk space needlessly. Find at least 4 other packages (for example: games, sound & video, etc) that you're not using on your system, and remove them. Be careful to ensure that removing those packages does not also remove other software that you do need.
Answer the Investigation 3 observations / questions in your lab log book.
Archiving Files / Compiling Software from Source Code
Archive files are often used to contain source code for software; in this lab you will also be compiling software from a source code archive.
Investigation 1: How do you create an archive file?
- Boot up your centos3 VM.
- Change your working directory to
/usr/share/doc/sudo*
- Use the tar (tape archiver) command to create an archive file named
/tmp/archive1.tar
tar cvf /tmp/archive1.tar .
- What do the options c, v, and f mean?
- Record the archive file size.
- Compress the file using
gzip
:gzip /tmp/archive1.tar
- Record the archive file size after compression.
- Make sure you're still in
/usr/share/doc/sudo*
and then create a compressed archive:tar cvzf /tmp/archive2.tgz .
- What does the
z
option do? - Compare the sizes of
/tmp/archive1.tar.gz
and/tmp/archive2.tgz
. Why are they so close in size?
Answer the Investigation 1 observations / questions in your lab log book.
Investigation 2: How do you restore files from an archive?
- Create the directory
/tmp/extract1
- Change to the
/tmp/extract1
directory. - Move the file archive1.tar.gz to your current directory.
- Unzip the first archive you created:
gunzip archive1.tar.gz
- Extract the files from the first archive:
tar xvf archive1.tar
- Are all the files there?
- Compare
/tmp/extract1/README
and/usr/share/doc/sudo*/README
. Are they exactly the same? Why? - Create the directory
/tmp/extract2
- Move the file archive2.tgz to the
/tmp/extract2
directory. - Extract the files from the second archive:
tar xvzf /tmp/extract2/archive2.tgz
- Note that this time a separate
gunzip
command was not needed. Why? - Repeat the previous command, leaving out the option "z". Does it work? Why?
- Compare the
README
file in this directory with the original file. Are they exactly the same?
Answer the Investigation 2 observations / questions in your lab log book.
Investigation 3: How do you build software from source code?
Now that you know how to create and decompress "zipped tarball archives", we will demonstrate how to install applications from websites containing these types of archives. Although this method is not as "user-friendly" as using the yum or rpm command, this method is useful if the application is NOT contained in regular software repositories...
In order to build software from source code, you must have the appropriate software development tools (such as make and gcc) and libraries (such as GTK) installed. The required tools will vary depending on the computer languages used in the software being built.
- Issue the following command to install a basic set of development tools and libraries:
yum groupinstall "Development Tools" "Development Libraries"
- Go to the directory
/tmp
- Use the
wget
command to download the "tar ball" that contains the source code for the NLED text editor.wget
is a command-line tool to download files from the web using the http or ftp protocols. - Extract the files. Change to the newly-extracted directory (
/tmp/nled-2.52
) - Check to see if there is a file named
configure
. If so, run it; if not, skip this step. (Most but not all source code archives contain this file) - Check to see if there is a file named
Makefile
ormakefile
. If so, type the command:make
- Did the command work? Why? Use the
yum
command to install the package gcc. What do you think the package gcc does?
- Reissue the
make
command. Where you successful? What doesmake
do? - Issue the command as root:
yum list ncurses
. What do you see? Issue the command at root:yum search ncurses
. What do you observe? - In this case, you need to install the ncurses development libraries as well. Issue the following command as root:
yum install ncurses-devel.x86_64
. Now issue the command:make
- Some software distributed as source code can automatically install itself. Try this command:
make install
- Most but not all source code archives include the capability of installing themselves this way.
- If the command
make install
does not work (how can you tell? What command did you learn from ULI101 to confirm that this command cannot be run from the command line?), copy thenled
program manually:cp nled /usr/local/bin
- Test
nled
to make sure it works. - Why did copying the nled executable to /usr/local/bin allow the nled command to be run by name anywhere in the command prompt?
Answer the Investigation 3 observations / questions in your lab log book.
Completing the lab
Notes:
- rpm command options
- yum command options
- How to use pvs/vgs/lvs/df/pvcreate/vgextend/lvextend
- Answer to this question "What is the license of the nautilus package?"
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:
- elinks application removed on the host (disk pack - main system c6host).
- Unnecessary/unused packages have been deleted (list at least 4, and show that they are no longer installed).
- Fresh backup of the virtual machines.
Preparing for Quizzes
- What is the advantage of disabling services such as bluetooth?
- What is the difference between a .tgz file and a .tar.gz file? What do these stand for?
- What is the purpose of a repository?
- What is source code?
- How do you build software from source code?
- Which is preferred: installing from an RPM file, or installing from source code? Why?
- How do you use
service/init/chkconfig
to:- show/set current runlevel
- list services
- stop a service
- start a service
- Why is it important to learn how to manage services?
- Why is it important to stop certain services?