COMP 3000 Lab 1 2011 - Revision history

Saran: /* Processes */

2011-09-28T21:11:07Z

Processes

← Older revision		Revision as of 21:11, 28 September 2011
Line 157:		Line 157:
	}		}
	else {		else {
	sleep(10); //Make it a zombie		sleep(10); //Make it a zombie...look at ps
	wait(NULL);		wait(NULL); //Enough of zombie fun, collect it now.
	return 0;		return 0;
	}		}

Saran: /* Permissions */

2011-09-27T19:52:46Z

Permissions

← Older revision		Revision as of 19:52, 27 September 2011
Line 213:		Line 213:
	# Write doesn't allow deletion of files or subfolders where as Modify does.		# Write doesn't allow deletion of files or subfolders where as Modify does.
	# In Linux, when the sticky bit is set on a directory, files in that directory may only be unlinked or renamed by root or their owner.		# In Linux, when the sticky bit is set on a directory, files in that directory may only be unlinked or renamed by root or their owner.
			# Yes. For example, consider a file f and three groups each containing a single user assigned to f with read, write and read & execute permissions. In unix, this means that three different users should have three different permissions for a single file - which is impossible. Owner and others are fixed, and group can have a single octal permission.

	===Environment===		===Environment===

Saran: /* Permissions */

2011-09-27T12:45:59Z

Permissions

← Older revision		Revision as of 12:45, 27 September 2011
Line 212:		Line 212:
	# Read, Write, Read and Execute, List Folder Contents, Modify, Full Control		# Read, Write, Read and Execute, List Folder Contents, Modify, Full Control
	# Write doesn't allow deletion of files or subfolders where as Modify does.		# Write doesn't allow deletion of files or subfolders where as Modify does.
	# In Linux, when the sticky bit is set on a directory, files in that directory may only be unlinked or renamed by root or their owner.		# In Linux, when the sticky bit is set on a directory, files in that directory may only be unlinked or renamed by root or their owner.
	# No. Here's a dumb permission translator - for every file in Windows compute the union of all sets of users in its assigned groups, and for each union create a new unix group and assign the file to it.

	===Environment===		===Environment===

Saran: /* Permissions */

2011-09-26T21:27:21Z

Permissions

← Older revision		Revision as of 21:27, 26 September 2011
Line 213:		Line 213:
	# Write doesn't allow deletion of files or subfolders where as Modify does.		# Write doesn't allow deletion of files or subfolders where as Modify does.
	# In Linux, when the sticky bit is set on a directory, files in that directory may only be unlinked or renamed by root or their owner.		# In Linux, when the sticky bit is set on a directory, files in that directory may only be unlinked or renamed by root or their owner.
	# No. Here's a dumb permission translator - for every file in Windows compute the union of all sets of users in its assigned groups, and for each union create a new unix group and assign the file to it.		# No. Here's a dumb permission translator - for every file in Windows compute the union of all sets of users in its assigned groups, and for each union create a new unix group and assign the file to it.

	===Environment===		===Environment===

Saran: /* Dynamic Libraries */

2011-09-26T21:03:05Z

Dynamic Libraries

← Older revision		Revision as of 21:03, 26 September 2011
Line 133:		Line 133:

	===Dynamic Libraries===		===Dynamic Libraries===
	# (Your answers might vary a bit) linux-gate.so.1 => (0x00b26000) <br> libproc-3.2.8.so => /lib/libproc-3.2.8.so (0x00541000) <br> libncurses.so.5 => /lib/libncurses.so.5 (0x002a9000) <br> libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0x00c63000) <br> libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0x00e6c000) <br> /lib/ld-linux.so.2 (0x00a0c000) <br>		# (Your answers might vary a bit) <br> linux-gate.so.1 => (0x00b26000) <br> libproc-3.2.8.so => /lib/libproc-3.2.8.so (0x00541000) <br> libncurses.so.5 => /lib/libncurses.so.5 (0x002a9000) <br> libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0x00c63000) <br> libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0x00e6c000) <br> /lib/ld-linux.so.2 (0x00a0c000) <br>
	# (Your answers might vary a bit) /lib/libcrypt-2.11.1.so <br> /lib/ld-2.11.1.so <br> /usr/lib/gconv/gconv-modules.cache		# (Your answers might vary a bit) <br> /lib/libcrypt-2.11.1.so <br> /lib/ld-2.11.1.so <br> /usr/lib/gconv/gconv-modules.cache

	==Part B==		==Part B==

Saran: /* Dynamic Libraries */

2011-09-26T21:02:39Z

Dynamic Libraries

← Older revision		Revision as of 21:02, 26 September 2011
Line 133:		Line 133:

	===Dynamic Libraries===		===Dynamic Libraries===
	#linux-gate.so.1 => (0x00b26000) <br> libproc-3.2.8.so => /lib/libproc-3.2.8.so (0x00541000) <br> libncurses.so.5 => /lib/libncurses.so.5 (0x002a9000) <br> libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0x00c63000) <br> libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0x00e6c000) <br> /lib/ld-linux.so.2 (0x00a0c000) <br>		# (Your answers might vary a bit) linux-gate.so.1 => (0x00b26000) <br> libproc-3.2.8.so => /lib/libproc-3.2.8.so (0x00541000) <br> libncurses.so.5 => /lib/libncurses.so.5 (0x002a9000) <br> libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0x00c63000) <br> libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0x00e6c000) <br> /lib/ld-linux.so.2 (0x00a0c000) <br>
	# /lib/libcrypt-2.11.1.so <br> /lib/ld-2.11.1.so <br> /usr/lib/gconv/gconv-modules.cache		# (Your answers might vary a bit) /lib/libcrypt-2.11.1.so <br> /lib/ld-2.11.1.so <br> /usr/lib/gconv/gconv-modules.cache

	==Part B==		==Part B==

Saran: /* Permissions */

2011-09-26T21:01:35Z

Permissions

← Older revision		Revision as of 21:01, 26 September 2011
Line 209:		Line 209:
	===Permissions===		===Permissions===
	# read, write, execute		# read, write, execute
	# You can 'cd' to that directory or list contents in it.		# You can 'cd' to that directory and list contents in it.
	# Read, Write, Read and Execute, List Folder Contents, Modify, Full Control		# Read, Write, Read and Execute, List Folder Contents, Modify, Full Control
	# Write doesn't allow deletion of files or subfolders where as Modify does.		# Write doesn't allow deletion of files or subfolders where as Modify does.

Afry: /* Answers */

2011-09-26T20:53:32Z

Answers

← Older revision		Revision as of 20:53, 26 September 2011
Line 134:		Line 134:
	===Dynamic Libraries===		===Dynamic Libraries===
	#linux-gate.so.1 => (0x00b26000) <br> libproc-3.2.8.so => /lib/libproc-3.2.8.so (0x00541000) <br> libncurses.so.5 => /lib/libncurses.so.5 (0x002a9000) <br> libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0x00c63000) <br> libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0x00e6c000) <br> /lib/ld-linux.so.2 (0x00a0c000) <br>		#linux-gate.so.1 => (0x00b26000) <br> libproc-3.2.8.so => /lib/libproc-3.2.8.so (0x00541000) <br> libncurses.so.5 => /lib/libncurses.so.5 (0x002a9000) <br> libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0x00c63000) <br> libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0x00e6c000) <br> /lib/ld-linux.so.2 (0x00a0c000) <br>
	#		# /lib/libcrypt-2.11.1.so <br> /lib/ld-2.11.1.so <br> /usr/lib/gconv/gconv-modules.cache

	==Part B==		==Part B==

Saran: /* Part B */

2011-09-26T20:51:18Z

Part B

← Older revision		Revision as of 20:51, 26 September 2011
Line 165:		Line 165:
	4. nozombie.c		4. nozombie.c

	/* Most of you are just waiting in the parent process with wait(~~NULL~~) ~~or something like that~~.		/* Most of you are just waiting in the parent process with wait().
	* But that means you cannot do anything else in that process.		* But that means you cannot do anything else in that process - wait() is a blocking system call.
	* A better idea would be to use signal handler, where the parent registers for a signal if a child dies (SIGCHILD)		* A better idea would be to use signal handler, where the parent registers for a signal if a child dies (SIGCHILD)
	* ~~And~~ then ~~waits~~ to collect the exit code.		* and then use wait() to collect the exit code.
	*/		*/
	#include <sys/wait.h>		#include <sys/wait.h>

Saran: /* Part B */

2011-09-26T20:50:14Z

Part B

← Older revision		Revision as of 20:50, 26 September 2011
Line 164:		Line 164:

	4. nozombie.c		4. nozombie.c

			/* Most of you are just waiting in the parent process with wait(NULL) or something like that.
			* But that means you cannot do anything else in that process.
			* A better idea would be to use signal handler, where the parent registers for a signal if a child dies (SIGCHILD)
			* And then waits to collect the exit code.
			*/
	#include <sys/wait.h>		#include <sys/wait.h>
	#include <stdlib.h>		#include <stdlib.h>