COMP 3000 Lab 4 2012 - Revision history

Soma: /* Answers */

2012-11-12T06:01:46Z

Answers

← Older revision		Revision as of 06:01, 12 November 2012
Line 40:		Line 40:

	Part B		Part B
	#See code.		#See code for hello-world-nulls.c below.
	#See code for mycopy-blocks.c below.		#See code for mycopy-blocks.c below.
	#Loopback mounts could be useful to mount the VM filesystem on the hosts physical disk as a block device. To be able to do this, the VM software must use the same format for its disk images as that of an actual physical disk (i.e., just a sequence of blocks). The QEMU "raw" disk type satisfies these requirements. VMware and Virtualbox default disks do not. (Some VM disk formats are raw device dumps preceded by a header. On those, you just need to specify an offset value to the loopback mount so that it ignores the first part of the file.)		#Loopback mounts could be useful to mount the VM filesystem on the hosts physical disk as a block device. To be able to do this, the VM software must use the same format for its disk images as that of an actual physical disk (i.e., just a sequence of blocks). The QEMU "raw" disk type satisfies these requirements. VMware and Virtualbox default disks do not. (Some VM disk formats are raw device dumps preceded by a header. On those, you just need to specify an offset value to the loopback mount so that it ignores the first part of the file.)
			<br>
			<source lang="c">
			/* hello-world-nulls.c */

	~~<source lang="c">~~
	#include <stdio.h>		#include <stdio.h>
	#include <fcntl.h>		#include <fcntl.h>
Line 69:		Line 71:
	return 0;		return 0;
	}		}
	~~</source>~~

	~~<source lang="c">~~
	/* mycopy-blocks.c */		/* mycopy-blocks.c */
	/* Usage: mycopy-blocks <block-size> <source> <dest>		/* Usage: mycopy-blocks <block-size> <source> <dest>

Soma: /* Answers */

2012-11-12T05:59:58Z

Answers

@@ Line 41: / Line 41: @@
 Part B
 #See code.
-#<pre>
+#See code for mycopy-blocks.c below.
 /* mycopy-blocks.c */
 /* Usage: mycopy-blocks <block-size> <source> <dest>
@@ Line 141: / Line 171: @@
          return(0);
+}
-</pre>
+</source>

Soma: /* Answers */

2012-11-12T05:50:47Z

Answers

@@ Line 41: / Line 41: @@
 Part B
 #See code.
-#See code.
+#<pre>
 #Loopback mounts could be useful to mount the VM filesystem on the hosts physical disk as a block device.  To be able to do this, the VM software must use the same format for its disk images as that of an actual physical disk (i.e., just a sequence of blocks).  The QEMU "raw" disk type satisfies these requirements.  VMware and Virtualbox default disks do not.  (Some VM disk formats are raw device dumps preceded by a header.  On those, you just need to specify an offset value to the loopback mount so that it ignores the first part of the file.)

Soma: /* Answers */

2012-10-24T20:16:40Z

Answers

← Older revision		Revision as of 20:16, 24 October 2012
Line 42:		Line 42:
	#See code.		#See code.
	#See code.		#See code.
	#Loopback mounts could be useful to mount the VM filesystem on the hosts physical disk as a block device. To be able to do this, the VM software must use the same format for its ~~filesystem~~ as ~~the host's~~ physical disk, ~~or block~~ device.		#Loopback mounts could be useful to mount the VM filesystem on the hosts physical disk as a block device. To be able to do this, the VM software must use the same format for its disk images as that of an actual physical disk (i.e., just a sequence of blocks). The QEMU "raw" disk type satisfies these requirements. VMware and Virtualbox default disks do not. (Some VM disk formats are raw device dumps preceded by a header. On those, you just need to specify an offset value to the loopback mount so that it ignores the first part of the file.)

	1.		1.

Soma: /* Answers */

2012-10-24T20:13:03Z

Answers

@@ Line 53: / Line 53: @@
   	write(file, "Hello", 5);
   	int i;
   	for(i=0; i<1000; i++)
@@ Line 71: / Line 70: @@
+  }
-.
+.  Will be here soon!

Jbeltram at 15:32, 24 October 2012

2012-10-24T15:32:28Z

← Older revision		Revision as of 15:32, 24 October 2012
Line 108:		Line 108:
	putc(0, writeF);		putc(0, writeF);
	}		}
	~~outSize = ftell(writeF);~~
	~~printf("%d\n", outSize%blockSize);~~

	fclose(readF);		fclose(readF);

Jbeltram at 15:31, 24 October 2012

2012-10-24T15:31:44Z

← Older revision		Revision as of 15:31, 24 October 2012
Line 82:		Line 82:
	char *inFile = argv[2];		char *inFile = argv[2];
	char *outFile = argv[3];		char *outFile = argv[3];

	~~//char *buf;~~
	int buf;		int buf;

	FILE *readF = fopen(inFile, "r");		FILE *readF = fopen(inFile, "r");
	FILE *writeF = fopen(outFile, "w");		FILE *writeF = fopen(outFile, "w");

Jbeltram at 15:31, 24 October 2012

2012-10-24T15:31:24Z

@@ Line 68: / Line 68: @@
   	close(file);
   	return 0;
+  }

Jbeltram at 15:29, 24 October 2012

2012-10-24T15:29:15Z

← Older revision		Revision as of 15:29, 24 October 2012
Line 47:		Line 47:
	#include <stdio.h>		#include <stdio.h>
	#include <fcntl.h>		#include <fcntl.h>

	int main(int argc, char *argv[])		int main(int argc, char *argv[])
	{		{

Jbeltram at 15:29, 24 October 2012

2012-10-24T15:29:01Z

← Older revision		Revision as of 15:29, 24 October 2012
Line 43:		Line 43:
	#See code.		#See code.
	#Loopback mounts could be useful to mount the VM filesystem on the hosts physical disk as a block device. To be able to do this, the VM software must use the same format for its filesystem as the host's physical disk, or block device.		#Loopback mounts could be useful to mount the VM filesystem on the hosts physical disk as a block device. To be able to do this, the VM software must use the same format for its filesystem as the host's physical disk, or block device.

			1.
			#include <stdio.h>
			#include <fcntl.h>

			int main(int argc, char *argv[])
			{
			int file = open("helloworld", O_RDWR \| O_CREAT);

			write(file, "Hello", 5);

			//Could also use lseek() to do this
			int i;
			for(i=0; i<1000; i++)
			{
			write(file, "\0", 1);
			}

			write(file, "world\n", 6);

			for(i=0; i<1000; i++)
			{
			write(file, "\0", 1);
			}

			close(file);
			return 0;
			}