Difference between revisions of "OPS235 Lab 5 - Fedora17"
Brian.gray (talk | contribs) |
Brian.gray (talk | contribs) |
||
Line 52: | Line 52: | ||
#Change your working directory to <code>/usr/share/doc/sudo*</code> | #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> | #Use the tar (tape archiver) command to create an archive file named <code>/tmp/archive1.tar</code> | ||
− | Don't miss the . at the end of the next command! It specifies what should go into the archive: the contents of the current directory. | + | |
+ | {{Admon/important | Warning! | Don't miss the '''.''' at the end of the next command! It specifies what should go into the archive: the contents of the current directory.}} | ||
tar cvf /tmp/archive1.tar . | tar cvf /tmp/archive1.tar . |
Revision as of 09:53, 13 February 2010
Contents
OPS235 Lab 5 - Loopback Filesystems, Archives, Compiling from Source
Objectives
- To create and use loopback filesystems in read-write mode
- To create and use archive files (tar and tar.gz)
- Compiling software from source code
- Customizing system startup
References
- man pages for mount, fstab, tar, gzip, make, chkconfig, dd, service
- Resources on the web:
Required Material
- SATA Hard Disk with Fedora 12 (the same one used for Lab 3 and 4)
- Lab log book
Prerequisites
- Completion of Labs 1-4
Introduction
There are two techniques used to place multiple files within one file: the first is to create a filesystem within a file, and the second is to use an archive program to create an archive file. 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. Finally, you will modify your system startup to eliminate unnecessary services and configure your system to automatically mount a partition.
Investigation 1: How do you create and use a filesystem in a regular file?
- Login using your Learn ID
- Create an empty file that is exactly 3 MB in size:
dd if=/dev/zero of=/tmp/fstest bs=1k count=3072
- How does this command ensure that the file is 3 MB in size? What is in the file at first?
- Create an ext3 filesystem within the newly-created file
/tmp/fstest
. Note the warning message/question that appears - Mount the filesystem (remember to use the loopback option; refer to Lab 1 if required). Use a mountpoint of your choosing.
- Copy the files
/etc/services
and/etc/protocols
to the filesystem mounted in the previous step - Unmount the filesystem
- Test your filesystem to be sure that the files
/etc/services
and/etc/protocols
were in fact copied into the filesystem within the file named/tmp/fstest
. - How much space is left in that filesystem? (Hint:
df -h
).
Make sure that your lab notes answer the Investigation 1 question.
Investigation 2: How do you create an archive file?
- 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? 3. Record the archive file size. 4. Compress the file using gzip:
gzip /tmp/archive1.tar
5. Record the archive file size after compression. 6. Make sure you're still in /usr/share/doc/bash-3.2 and then create a compressed archive:
tar cvzf /tmp/archive2.tgz .
What does the z option do? 7. Compare the sizes of /tmp/archive1.tar.gz and /tmp/archive2.tgz. Why are they so close in size?
Answer the Investigation 2 question.