Operating Systems 2019W: Tutorial 1 - Revision history

Soma: /* Function calls, library calls, and system calls */

2019-01-14T18:48:51Z

Function calls, library calls, and system calls

← Older revision		Revision as of 18:48, 14 January 2019
Line 30:		Line 30:
	# Compile the program prog.c using <tt>gcc -O2 prog.c -o prog-dyn</tt> and run prog-dyn. What does it do?		# Compile the program prog.c using <tt>gcc -O2 prog.c -o prog-dyn</tt> and run prog-dyn. What does it do?
	# Statically compile and optimize prog.c by running <tt>gcc -O2 -static prog.c -o prog-static</tt>. How does the size compare with <tt>prog</tt>?		# Statically compile and optimize prog.c by running <tt>gcc -O2 -static prog.c -o prog-static</tt>. How does the size compare with <tt>prog</tt>?
	# See what system calls prog-static produces by running <tt>strace -o syscalls-static.log ./prog-static</tt>. Do the same for <tt>prog-dyn</tt>. Which version generates more system calls?		# See what system calls prog-static produces by running <tt>strace -o syscalls-static.log ./prog-static</tt>. Do the same for <tt>prog-dyn</tt>. Which version generates more system calls? '''Note: system calls are saved in the log file syscalls-static.log. Feel free to save them in a different file.'''
	# See what library calls prog-static produces by running <tt>ltrace -o library-static.log ./prog-static</tt>. Do the same for <tt>prog-dyn</tt>. Which version generates more library calls? (If ltrace isn't installed, run <tt>sudo apt-get install ltrace</tt>)		# See what library calls prog-static produces by running <tt>ltrace -o library-static.log ./prog-static</tt>. Do the same for <tt>prog-dyn</tt>. Which version generates more library calls? (If ltrace isn't installed, run <tt>sudo apt-get install ltrace</tt>)
	# Use the command <tt>ls -l</tt> to see the metadata associated with prog.c and prog-dyn, and prog-static. Who owns these files? What group are they in? Do you notice any pattern with the permissions (rwx) associated with each file?		# Use the command <tt>ls -l</tt> to see the metadata associated with prog.c and prog-dyn, and prog-static. Who owns these files? What group are they in? Do you notice any pattern with the permissions (rwx) associated with each file?

Soma: /* Function calls, library calls, and system calls */

2019-01-14T18:45:31Z

Function calls, library calls, and system calls

← Older revision		Revision as of 18:45, 14 January 2019
Line 25:		Line 25:

	For [http://homeostasis.scs.carleton.ca/~soma/os-2017f/code/tut1/hello.c hello.c] and [http://homeostasis.scs.carleton.ca/~soma/os-2017f/code/tut1/syscall-hello.c syscall-hello.c] do the following (substituting the appropriate source file for prog.c). To download programs to your VM, use the wget command, e.g.		For [http://homeostasis.scs.carleton.ca/~soma/os-2017f/code/tut1/hello.c hello.c] and [http://homeostasis.scs.carleton.ca/~soma/os-2017f/code/tut1/syscall-hello.c syscall-hello.c] do the following (substituting the appropriate source file for prog.c). To download programs to your VM, use the wget command, e.g.
			<pre>
	wget https://homeostasis.scs.carleton.ca/~soma/os-2017f/code/tut1/hello.c		wget https://homeostasis.scs.carleton.ca/~soma/os-2017f/code/tut1/hello.c
			</pre>
	# Compile the program prog.c using <tt>gcc -O2 prog.c -o prog-dyn</tt> and run prog-dyn. What does it do?		# Compile the program prog.c using <tt>gcc -O2 prog.c -o prog-dyn</tt> and run prog-dyn. What does it do?
	# Statically compile and optimize prog.c by running <tt>gcc -O2 -static prog.c -o prog-static</tt>. How does the size compare with <tt>prog</tt>?		# Statically compile and optimize prog.c by running <tt>gcc -O2 -static prog.c -o prog-static</tt>. How does the size compare with <tt>prog</tt>?

Soma: /* Function calls, library calls, and system calls */

2019-01-14T18:44:56Z

Function calls, library calls, and system calls

← Older revision		Revision as of 18:44, 14 January 2019
Line 25:		Line 25:

	For [http://homeostasis.scs.carleton.ca/~soma/os-2017f/code/tut1/hello.c hello.c] and [http://homeostasis.scs.carleton.ca/~soma/os-2017f/code/tut1/syscall-hello.c syscall-hello.c] do the following (substituting the appropriate source file for prog.c). To download programs to your VM, use the wget command, e.g.		For [http://homeostasis.scs.carleton.ca/~soma/os-2017f/code/tut1/hello.c hello.c] and [http://homeostasis.scs.carleton.ca/~soma/os-2017f/code/tut1/syscall-hello.c syscall-hello.c] do the following (substituting the appropriate source file for prog.c). To download programs to your VM, use the wget command, e.g.
	wget https://homeostasis.scs.carleton.ca/~soma/os-2017f/code/tut1/~~syscall-hello.c syscall-~~hello.c		wget https://homeostasis.scs.carleton.ca/~soma/os-2017f/code/tut1/hello.c
	# Compile the program prog.c using <tt>gcc -O2 prog.c -o prog-dyn</tt> and run prog-dyn. What does it do?		# Compile the program prog.c using <tt>gcc -O2 prog.c -o prog-dyn</tt> and run prog-dyn. What does it do?
	# Statically compile and optimize prog.c by running <tt>gcc -O2 -static prog.c -o prog-static</tt>. How does the size compare with <tt>prog</tt>?		# Statically compile and optimize prog.c by running <tt>gcc -O2 -static prog.c -o prog-static</tt>. How does the size compare with <tt>prog</tt>?

Soma: /* Setting up Openstack */

2019-01-14T18:36:05Z

Setting up Openstack

← Older revision		Revision as of 18:36, 14 January 2019
Line 15:		Line 15:
	Once you log in, create a VM by going to Images and select Launch Instance for "ubuntu_18.04_lightapps_desktop_2019-01-04". In the resulting dialog, give your instance a name and select the right security groups, then launch the image.		Once you log in, create a VM by going to Images and select Launch Instance for "ubuntu_18.04_lightapps_desktop_2019-01-04". In the resulting dialog, give your instance a name and select the right security groups, then launch the image.
	* Please name your VM <username-X>. Thus if your username is alicehacker, name your first VM "alicehacker-1". If you need more VMs, just increment the name!		* Please name your VM <username-X>. Thus if your username is alicehacker, name your first VM "alicehacker-1". If you need more VMs, just increment the name!
	* Under "Access & Security", ~~check off~~ the "ping-ssh-egress" option. Don't specify a key pair, it isn't supported by our image.		* Under "Access & Security", select the "ping-ssh-egress" option. Don't specify a key pair, it isn't supported by our image.
	Once you've launched the image, while it is spawning select "Associate Floating IP" in button menu associated with the launching VM. You may select any IP address that is available.		Once you've launched the image, while it is spawning select "Associate Floating IP" in button menu associated with the launching VM. You may select any IP address that is available.

Soma: /* Setting up Openstack */

2019-01-14T18:34:17Z

Setting up Openstack

← Older revision		Revision as of 18:34, 14 January 2019
Line 11:		Line 11:
	To login, visit [https://openstack.scs.carleton.ca openstack.scs.carleton.ca]. Note that you can only access this page when on the Carleton network. To get on the Carleton network when off campus, please connect using [https://carleton.ca/its/help-centre/remote-access/ Carleton's VPN service].		To login, visit [https://openstack.scs.carleton.ca openstack.scs.carleton.ca]. Note that you can only access this page when on the Carleton network. To get on the Carleton network when off campus, please connect using [https://carleton.ca/its/help-centre/remote-access/ Carleton's VPN service].

	You should login using your MyCarletonOne username and your SCS password. These are the same credentials you use to login to the Windows machines in the lab or the SCS linux machines. If your password doesn't work, you should change your password on the SCS [http://www.scs.carleton.ca/webacct/ account management page] ([https://service.scs.carleton.ca/technical-support/account-creation instructions are here]).		You should login using your MyCarletonOne username and your SCS password. These are the same credentials you use to login to the Windows machines in the lab or the SCS linux machines. '''If your password doesn't work or you can't access the COMP 3000B project''', you should change your password on the SCS [http://www.scs.carleton.ca/webacct/ account management page] ([https://service.scs.carleton.ca/technical-support/account-creation instructions are here]).

	Once you log in, create a VM by going to Images and select Launch Instance for "ubuntu_18.04_lightapps_desktop_2019-01-04". In the resulting dialog, give your instance a name and select the right security groups, then launch the image.		Once you log in, create a VM by going to Images and select Launch Instance for "ubuntu_18.04_lightapps_desktop_2019-01-04". In the resulting dialog, give your instance a name and select the right security groups, then launch the image.
Line 18:		Line 18:
	Once you've launched the image, while it is spawning select "Associate Floating IP" in button menu associated with the launching VM. You may select any IP address that is available.		Once you've launched the image, while it is spawning select "Associate Floating IP" in button menu associated with the launching VM. You may select any IP address that is available.

	Once the VM is fully spawned, connect via ssh to your VM (using putty or similar) at the IP address you specified, using the username "student" and the password "student". As you first command, '''type "passwd" to change your password.'''.		Once the VM is fully spawned, connect via ssh to your VM (using putty or similar) at the IP address you specified, using the username "student" and the password "student". As you first command, '''type "passwd" to change your password.'''. On Linux, the ssh client is "ssh". '''On Windows, use PuTTY.'''

	You can get more information on how to use the SCS Openstack cluster at the [https://carleton.ca/scs/technical-support/scs-open-stack/openstack-technical-support/ SCS support page]. Note this page includes videos!		You can get more information on how to use the SCS Openstack cluster at the [https://carleton.ca/scs/technical-support/scs-open-stack/openstack-technical-support/ SCS support page]. Note this page includes videos!

Soma: /* Function calls, library calls, and system calls */

2019-01-14T18:19:25Z

Function calls, library calls, and system calls

← Older revision		Revision as of 18:19, 14 January 2019
Line 24:		Line 24:
	==Function calls, library calls, and system calls==		==Function calls, library calls, and system calls==

	For [http://homeostasis.scs.carleton.ca/~soma/os-2017f/code/tut1/hello.c hello.c] and [http://homeostasis.scs.carleton.ca/~soma/os-2017f/code/tut1/syscall-hello.c syscall-hello.c] do the following (substituting the appropriate source file for prog.c):		For [http://homeostasis.scs.carleton.ca/~soma/os-2017f/code/tut1/hello.c hello.c] and [http://homeostasis.scs.carleton.ca/~soma/os-2017f/code/tut1/syscall-hello.c syscall-hello.c] do the following (substituting the appropriate source file for prog.c). To download programs to your VM, use the wget command, e.g.
			wget https://homeostasis.scs.carleton.ca/~soma/os-2017f/code/tut1/syscall-hello.c syscall-hello.c
	# Compile the program prog.c using <tt>gcc -O2 prog.c -o prog-dyn</tt> and run prog-dyn. What does it do?		# Compile the program prog.c using <tt>gcc -O2 prog.c -o prog-dyn</tt> and run prog-dyn. What does it do?
	# Statically compile and optimize prog.c by running <tt>gcc -O2 -static prog.c -o prog-static</tt>. How does the size compare with <tt>prog</tt>?		# Statically compile and optimize prog.c by running <tt>gcc -O2 -static prog.c -o prog-static</tt>. How does the size compare with <tt>prog</tt>?

Soma: /* Setting up Openstack */

2019-01-14T13:57:46Z

Setting up Openstack

← Older revision		Revision as of 13:57, 14 January 2019
Line 10:		Line 10:

	To login, visit [https://openstack.scs.carleton.ca openstack.scs.carleton.ca]. Note that you can only access this page when on the Carleton network. To get on the Carleton network when off campus, please connect using [https://carleton.ca/its/help-centre/remote-access/ Carleton's VPN service].		To login, visit [https://openstack.scs.carleton.ca openstack.scs.carleton.ca]. Note that you can only access this page when on the Carleton network. To get on the Carleton network when off campus, please connect using [https://carleton.ca/its/help-centre/remote-access/ Carleton's VPN service].

			You should login using your MyCarletonOne username and your SCS password. These are the same credentials you use to login to the Windows machines in the lab or the SCS linux machines. If your password doesn't work, you should change your password on the SCS [http://www.scs.carleton.ca/webacct/ account management page] ([https://service.scs.carleton.ca/technical-support/account-creation instructions are here]).

	Once you log in, create a VM by going to Images and select Launch Instance for "ubuntu_18.04_lightapps_desktop_2019-01-04". In the resulting dialog, give your instance a name and select the right security groups, then launch the image.		Once you log in, create a VM by going to Images and select Launch Instance for "ubuntu_18.04_lightapps_desktop_2019-01-04". In the resulting dialog, give your instance a name and select the right security groups, then launch the image.

Soma at 20:56, 12 January 2019

2019-01-12T20:56:07Z

← Older revision		Revision as of 20:56, 12 January 2019
Line 1:		Line 1:
	~~'''This tutorial is not yet finalized.'''~~

	In this tutorial you will be learning about 1) the difference between system calls, function calls, and library calls, 2) how C is translated into assembly, and 3) how processes are created.		In this tutorial you will be learning about 1) the difference between system calls, function calls, and library calls, 2) how C is translated into assembly, and 3) how processes are created.

Soma at 20:19, 12 January 2019

2019-01-12T20:19:06Z

← Older revision		Revision as of 20:19, 12 January 2019
Line 1:		Line 1:
	'''This tutorial is not yet finalized.'''		'''This tutorial is not yet finalized.'''

	In this tutorial you will be learning about 1) the difference between system calls, function calls, and library calls and 2) how processes are created.		In this tutorial you will be learning about 1) the difference between system calls, function calls, and library calls, 2) how C is translated into assembly, and 3) how processes are created.

	==Getting started==		==Getting started==

Soma: /* Creating processes, running executables */

2019-01-12T20:03:01Z

Creating processes, running executables

← Older revision		Revision as of 20:03, 12 January 2019
Line 57:		Line 57:
	==Creating processes, running executables==		==Creating processes, running executables==

	For this part you will be playing with and modifying [http://homeostasis.scs.carleton.ca/~soma/os-~~2017f~~/code~~/tut1~~/csimpleshell.c csimpleshell.c] by [https://web.archive.org/web/20170223203852/http://rik0.altervista.org/snippets/csimpleshell.html Enrico Franchi], as well as looking at the files from the previous section. The source is also listed below.		For this part you will be playing with and modifying [http://homeostasis.scs.carleton.ca/~soma/os-2019w/code/csimpleshell.c csimpleshell.c] by [https://web.archive.org/web/20170223203852/http://rik0.altervista.org/snippets/csimpleshell.html Enrico Franchi], as well as looking at the files from the previous section. The source is also listed below.

	# Compile and run csimpleshell. Try running some commands in csimpleshell as you did with the regular shell (bash). How similar is their behavior?		# Compile and run csimpleshell. Try running some commands in csimpleshell as you did with the regular shell (bash). How similar is their behavior?