Changes

OPS235 Lab 3 - CentOS7

2,020 bytes added, 13:12, 29 March 2015

no edit summary

#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~~b>/tmp/archive1.tar</~~code~~b>#*<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.}}

<li>Compress the file using <code>gzip</code>:

<ul>

<li><code>gzip /tmp/archive1.tar</code></li>

</ul>

</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~~span style="color:#3366CC;font-size:1.2em;">/tmp/archive2.tgz</code>. Why are they so close in size?</li>

</ol>

===Part 2: Restoring 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~~span style="color:#3366CC;font-size:1.2em;">/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~~b>/tmp/extract2</~~code~~b> 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.'''

<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>

<ol>

<li value="2">Issue the command: <code>yum install elinks</code> and answer <code>y</code> to the question about installation.

<li>Where did ''yum'' get the elinks software?</li>

</li>

<li>Issue an RPM query to verify that elinks is installed. Record this command in your lab log-book.</li>

<li>Issue the command: <code>yum remove elinks</code></li>

<li>Issue an RPM query to verify that elinks is no longer installed. Record this command in your lab log-book.</li>

<li>Issue this command: <code>yum info cups</code></li>

</ol>

::* Based on the result, do you think that cups is a useful package for your system? If not, try removing it.

Msaul

Administrators

13,420

edits

CDOT Wiki β

Changes

OPS235 Lab 3 - CentOS7

CDOT Wiki ^β