Operating Systems 2014F Final Exam Review: Difference between revisions

Revision as of 18:54, 9 December 2014

Concepts

file sizes (logical versus blocks consumed)
mounting a fs
- changes in filesystem hierarchy
- concept of a "root" filesystem
- privileges required
loopback mounts and files
- /dev/loopX
holes in files
stat on files

Sample Questions

If a program "seek"'s on a zero length file to position 100,000 and then writes one byte, what would you expect the file's logical length to be? What about its physical size (space consumed on disk)?
You download a CD image (ISO 9660), but you only want one file that is on the CD. Note the file is encoded with the standard ISO filesystem (that your computer already knows how to process). One way to get that file would be to burn the CD and then read the file off of it. How could you get the file WITHOUT burning a CD? (Would doing this require the use of a block device?)

@@ Line 6: / Line 6: @@
 ** privileges required
 * loopback mounts and files
+** /dev/loopX
 * holes in files
 * stat on files
@@ Line 12: / Line 13: @@
 Sample Questions
 * If a program "seek"'s on a zero length file to position 100,000 and then writes one byte, what would you expect the file's logical length to be?  What about its physical size (space consumed on disk)?
+* You download a CD image (ISO 9660), but you only want one file that is on the CD.  Note the file is encoded with the standard ISO filesystem (that your computer already knows how to process).  One way to get that file would be to burn the CD and then read the file off of it.  How could you get the file WITHOUT burning a CD?  (Would doing this require the use of a block device?)