|
|
| Line 56: |
Line 56: |
| | * [https://www.centos.org/docs/5/html/5.2/Installation_Guide/s2-init-boot-shutdown-rl.html Runlevels] | | * [https://www.centos.org/docs/5/html/5.2/Installation_Guide/s2-init-boot-shutdown-rl.html Runlevels] |
| | | | |
| − | ==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.
| |
| − |
| |
| − | {{Admon/note|Do not Shut-Down VMs Until Instructed|You will be running all 3 VMs eventually when performing this tutorial, Leave all VMs running until you are instructed to shut them down at the end of this lab.|}}
| |
| − |
| |
| − | ===Investigation 1: How do you create an archive file?===
| |
| − | {{Admon/note|Use centos3|Perform these steps in the '''centos3''' virtual machine.}}
| |
| − |
| |
| − | #Boot up your '''centos3''' VM.
| |
| − | #Change your working directory to <code>/usr/share/doc/sudo*</code>
| |
| − | #Use the tar (tape archiver) command to create an archive file named <code>/tmp/archive1.tar</code>
| |
| − | #*<code>tar cvf /tmp/archive1.tar .</code>
| |
| − |
| |
| − | {{Admon/important | Warning! | Don't miss the '''.''' at the end of the <code>tar</code> commands below! It specifies what should go into the archive: the contents of the current directory.}}
| |
| − |
| |
| − | <ol>
| |
| − | <li value="4">What do the options c, v, and f mean?</li>
| |
| − | <li>Record the archive file size.</li>
| |
| − | <li>Compress the file using <code>gzip</code>:
| |
| − | <ul>
| |
| − | <li><code>gzip /tmp/archive1.tar</code></li>
| |
| − | </ul>
| |
| − | </li>
| |
| − | <li>Record the archive file size after compression.</li>
| |
| − | <li>Make sure you're still in <code>/usr/share/doc/sudo*</code> and then create a compressed archive:
| |
| − | <ul>
| |
| − | <li><code>tar cvzf /tmp/archive2.tgz .</code></li>
| |
| − | </ul>
| |
| − | </li>
| |
| − | <li>What does the <code>z</code> option do?</li>
| |
| − | <li>Compare the sizes of <code>/tmp/archive1.tar.gz</code> and <code>/tmp/archive2.tgz</code>. Why are they so close in size?</li>
| |
| − | </ol>
| |
| − |
| |
| − | '''Answer the Investigation 1 observations / questions in your lab log book.'''
| |
| − |
| |
| − | ===Investigation 2: How do you restore files from an archive?===
| |
| − | {{Admon/note|Remain in your centos3 VM|Perform these steps in the '''centos3''' virtual machine.}}
| |
| − | #Create the directory <code>/tmp/extract1</code>
| |
| − | #Change to the <code>/tmp/extract1</code> directory.
| |
| − | #Move the file archive1.tar.gz to your current directory.
| |
| − | #Unzip the first archive you created:
| |
| − | #*<code>gunzip archive1.tar.gz</code>
| |
| − | #Extract the files from the first archive:
| |
| − | #*<code>tar xvf archive1.tar</code>
| |
| − | #Are all the files there?
| |
| − | #Compare <code>/tmp/extract1/README</code> and <code>/usr/share/doc/sudo*/README</code>. Are they exactly the same? Why?
| |
| − | #Create the directory <code>/tmp/extract2</code>
| |
| − | #Move the file archive2.tgz to the <code>/tmp/extract2</code> directory.
| |
| − | #Extract the files from the second archive:
| |
| − | #*<code>tar xvzf /tmp/extract2/archive2.tgz</code>
| |
| − | #Note that this time a separate <code>gunzip</code> command was not needed. Why?
| |
| − | #Repeat the previous command, leaving out the option "z". Does it work? Why?
| |
| − | #Compare the <code>README</code> 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...
| |
| − | {{Admon/note|Use centos2|Perform these steps in the '''centos2''' virtual machine.}}
| |
| − |
| |
| − | 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:<br /><code>yum groupinstall "Development Tools" "Development Libraries"</code>
| |
| − |
| |
| − | {{Admon/note|Installing Development Libraries|In the future, remember the above procedure whenever installing software from source. Sometimes, you need to install additional tools or libraries in order to compile a particular software package}}
| |
| − |
| |
| − | <ol>
| |
| − | <li value="3">Go to the directory <code>/tmp</code></li>
| |
| − | <li>Use the <code>wget</code> command to download the "tar ball" that contains the source code for the NLED text editor. <code>wget</code> is a command-line tool to download files from the web using the http or ftp protocols.
| |
| − | <ul>
| |
| − | <li><code>wget http://cdot.senecac.on.ca/software/nled/nled_2_52_src.tgz</code></li>
| |
| − | </ul>
| |
| − | </li>
| |
| − | <li>Extract the files. Change to the newly-extracted directory (<code>/tmp/nled-2.52</code>)</li>
| |
| − | <li>Check to see if there is a file named <code>configure</code>. If so, run it; if not, skip this step. (Most but not all source code archives contain this file)</li>
| |
| − | <li>Check to see if there is a file named <code>Makefile</code> or <code>makefile</code>. If so, type the command:
| |
| − | <ul>
| |
| − | <li><code>make</code></li>
| |
| − | <li>Did the command work? Why? Use the <code>yum</code> command to install the package '''gcc'''. What do you think the package ''gcc'' does?</li>
| |
| − | </ul>
| |
| − | <li>Reissue the <code>make</code> command. Where you successful? What does <code>make</code> do?</li>
| |
| − | <li>Issue the command as root: <code>yum list ncurses</code>. What do you see? Issue the command at root: <code>yum search ncurses</code>. What do you observe?</li>
| |
| − | <li>In this case, you need to install the ncurses development libraries as well. Issue the following command as root: <code>yum install ncurses-devel.x86_64</code>. Now issue the command: <code>make</code></li>
| |
| − | <li>Some software distributed as source code can automatically install itself. Try this command:
| |
| − | <ul>
| |
| − | <li><code>make install</code></li>
| |
| − | </ul>
| |
| − | </li>
| |
| − | <li>Most but not all source code archives include the capability of installing themselves this way.</li>
| |
| − | <li>If the command <code>make install</code> 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 the <code>nled</code> program manually:
| |
| − | <ul>
| |
| − | <li><code>cp nled /usr/local/bin</code></li>
| |
| − | </ul>
| |
| − | </li>
| |
| − | <li>Test <code>nled</code> to make sure it works.</li>
| |
| − | <li>Why did copying the nled executable to /usr/local/bin allow the nled command to be run by name anywhere in the command prompt?</li>
| |
| − | </ol>
| |
| − |
| |
| − | '''Answer the Investigation 3 observations / questions in your lab log book.'''
| |
| | | | |
| | ==Managing Run-Levels and System Services== | | ==Managing Run-Levels and System Services== |
Archiving Files, Compiling Software Packages from Source, Managing Services
Overview
- 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 (decompressing zipped tarball archives and then compiling source code).
- In addition, you will learn about how certain processes (services) work, and how the system administrator can manage these services (i.e. turn "on" and "off").
Objectives
- To create and use archive files (tar and tar.gz)
- Compiling software packages from source code
- Install an application from software development repositories using the bit utility
- Customising file-system start-up
Required Materials (Bring to All Labs)
- CentOS 6.5 x86_64 Live DVD
- CentOS 6.5 x86_64 Installation DVD1
- SATA Hard Disk (in removable disk tray)
- USB Memory Stick
- Lab Logbook
Prerequisites
Linux Command Online Reference
Each Link below displays online manpages for each command (via http://linuxmanpages.com):
| Archiving Utilities:
|
Service Management Utilities:
|
|
|
|
|
Resources on the web
Additional links to tutorials and HOWTOs:
Managing Run-Levels and System Services
Investigation 4: How do we Manage Runlevels?
Use centos2 and centos3
Perform these steps in both of these virtual machines.
The runlevel command is now deprecated in Fedora, and will likely be deprecated in RHEL/CentOS at some point as well, but for now this is what the industry is using.
- Issue the following Linux command:
- Note the difference in output between centos2 and centos3.
- You can use the
init command to change the current runlevel. See a list of runlevels here. Use the man command to learn how to use the
- Change the default runlevel on centos2 to 3. What happens now after you reboot?
- Issue the following Linux command:
- What happens?
- Log-off your graphical system. You should return to your shell prompt.
- Change the default runlevel for centos2 back to 5 and reboot to make sure it works.
Answer the Investigation 4 observations / questions in your lab log book.
Investigation 5: How do we Manage System Services?
Remain in your centos2 VM
Perform these steps in the centos2 virtual machine.
We have seen that maintaining unneeded packages can be a security risk due to the unnecessary increase in the complexity of your system. Similarly, it is also unnecessarily hazardous, and even more so, to leave unneeded services running. In this investigation, we will learn how to control services, and turn off those services that we think are not necessary to help reduce security risks.}}
- Issue the following Linux command:
- Note the services that are currently running.
- Use the
service command to stop the service named iptables
- Issue the
service command to verify that this service has stopped.
- If you reboot now - the iptables service will be turned back on. We don't want it on though, it causes students headaches. To turn it off permanently we need to use the chkconfig command:
chkconfig iptables off
- Reboot and confirm that it's no longer running.
Answer the Investigation 5 observations / questions in your lab log book.
Completing the Lab
Arrange evidence for each of these items on your screen, then ask your instructor to check each item:
- Compressed files:
/tmp/archive1.tar.gz and /tmp/archive2.tgz
nled application is installed- Lab5 notes how to use service/chkconfig commands
- VMs backed-up
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?
Backup your work
Backup your disk images for centos2 and centos3 Virtual Machines.
