Operating Systems 2014F Final Exam Review - Revision history

Soma at 21:43, 9 December 2014

2014-12-09T21:43:32Z

← Older revision		Revision as of 21:43, 9 December 2014
Line 1:		Line 1:
			The audio from the review session (held December 9, 2014) [http://homeostasis.scs.carleton.ca/~soma/os-2014f/lectures/comp3000-2014f-finalreview-09Dec2014.mp3 is now available].

			==Notes==
	Concepts		Concepts
	* file sizes (logical versus blocks consumed)		* file sizes (logical versus blocks consumed)

Soma at 19:10, 9 December 2014

2014-12-09T19:10:44Z

← Older revision		Revision as of 19:10, 9 December 2014
Line 14:		Line 14:
	* 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)?		* 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?)		* 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?)
			* There are many restrictions on mounting filesystems (which users, what devices, etc). How could you fundamentally change the running of a system using an unrestricted mount?

Soma at 18:54, 9 December 2014

2014-12-09T18:54:49Z

← Older revision		Revision as of 18:54, 9 December 2014
Line 6:		Line 6:
	** privileges required		** privileges required
	* loopback mounts and files		* loopback mounts and files
			** /dev/loopX
	* holes in files		* holes in files
	* stat on files		* stat on files
Line 12:		Line 13:
	Sample Questions		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)?		* 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?)

Soma at 18:36, 9 December 2014

2014-12-09T18:36:16Z

← Older revision		Revision as of 18:36, 9 December 2014
Line 11:		Line 11:

	Sample Questions		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)?

Soma: Created page with "Concepts * file sizes (logical versus blocks consumed) * mounting a fs changes in filesystem hierarchy concept of a "root" filesystem ** privileges required * loopback m..."

2014-12-09T18:30:37Z

Created page with "Concepts * file sizes (logical versus blocks consumed) * mounting a fs ** changes in filesystem hierarchy ** concept of a "root" filesystem ** privileges required * loopback m..."

New page