COMP3000 Operating Systems W23: Tutorial 1 - Revision history

Lianyingzhao: /* Getting Started */

2023-01-10T02:35:49Z

Getting Started

← Older revision		Revision as of 02:35, 10 January 2023
Line 19:		Line 19:

	==Getting Started==		==Getting Started==
	For the tutorials, you need to get access to a Linux machine. We strongly suggest you use an SCS Openstack instance (see the instructions below). Alternatively, if you have resource available and prefer to work offline with your desktop/laptop, you can also download <b>this VirtualBox image</b> ~~-to be updated-~~ (which is the same with the Openstack image). You will need access to a system for the entire semester, ideally the same one.		For the tutorials, you need to get access to a Linux machine. We strongly suggest you use an SCS Openstack instance (see the instructions below). Alternatively, if you have resource available and prefer to work offline with your desktop/laptop, you can also download [https://git.scs.carleton.ca/downloads/CourseVirtualMachines/2022F-2023W/COMP3000-W23.ova <b>this VirtualBox image</b>] (which is the same with the Openstack image). You will need access to a system for the entire semester, ideally the same one.

	The concepts covered below are mostly part of standard UNIX/Linux tutorials. Feel free to consult one or more of them. However, remember that you are trying to build a conceptual model of how things work. Thus, don't memorize commands; instead, try to understand how things fit together, learn how to find out the answer with that model, and ask questions when things don't work as expected!		The concepts covered below are mostly part of standard UNIX/Linux tutorials. Feel free to consult one or more of them. However, remember that you are trying to build a conceptual model of how things work. Thus, don't memorize commands; instead, try to understand how things fit together, learn how to find out the answer with that model, and ask questions when things don't work as expected!

Lianyingzhao: /* Getting Started */

2023-01-08T05:22:03Z

Getting Started

← Older revision		Revision as of 05:22, 8 January 2023
Line 19:		Line 19:

	==Getting Started==		==Getting Started==
	For the tutorials, you need to get access to a Linux machine. We strongly suggest you use an SCS Openstack instance (see the instructions below). Alternatively, if you have resource available and prefer to work offline with your desktop/laptop, you can also download ~~the~~ VirtualBox image (which is the same with the Openstack image). You will need access to a system for the entire semester, ideally the same one.		For the tutorials, you need to get access to a Linux machine. We strongly suggest you use an SCS Openstack instance (see the instructions below). Alternatively, if you have resource available and prefer to work offline with your desktop/laptop, you can also download <b>this VirtualBox image</b> -to be updated- (which is the same with the Openstack image). You will need access to a system for the entire semester, ideally the same one.

	The concepts covered below are mostly part of standard UNIX/Linux tutorials. Feel free to consult one or more of them. However, remember that you are trying to build a conceptual model of how things work. Thus, don't memorize commands; instead, try to understand how things fit together, learn how to find out the answer with that model, and ask questions when things don't work as expected!		The concepts covered below are mostly part of standard UNIX/Linux tutorials. Feel free to consult one or more of them. However, remember that you are trying to build a conceptual model of how things work. Thus, don't memorize commands; instead, try to understand how things fit together, learn how to find out the answer with that model, and ask questions when things don't work as expected!

Lianyingzhao: /* Openstack */

2023-01-06T04:24:10Z

Openstack

← Older revision		Revision as of 04:24, 6 January 2023
Line 30:		Line 30:
	You can create a VM on the SCS openstack by following [[COMP3000 Operating Systems W23: Openstack Instructions \| '''these steps''']]. If you encouter any issue and would like more reading, SCS already has [https://carleton.ca/scs/tech-support/scs-open-stack/openstack-technical-support/ lots of documentation on openstack], including a [https://carleton.ca/scs/tech-support/scs-open-stack/openstack-technical-support/openstack-step-by-step-guide/ step-by-step guide].		You can create a VM on the SCS openstack by following [[COMP3000 Operating Systems W23: Openstack Instructions \| '''these steps''']]. If you encouter any issue and would like more reading, SCS already has [https://carleton.ca/scs/tech-support/scs-open-stack/openstack-technical-support/ lots of documentation on openstack], including a [https://carleton.ca/scs/tech-support/scs-open-stack/openstack-technical-support/openstack-step-by-step-guide/ step-by-step guide].

	Make sure of the key steps: ①Carleton VPN, ②refresh your SCS account if needed, ③the COMP3000-W23 project, ④the COMP3000-W23~~-image~~ '''snapshot''' image, ⑤adding the ping-ssh-egress security group, and ⑥associating a floating IP address.		Make sure of the key steps: ①Carleton VPN, ②refresh your SCS account if needed, ③the COMP3000-W23 project, ④the COMP3000-W23 '''snapshot''' image, ⑤adding the ping-ssh-egress security group, and ⑥associating a floating IP address.

	The 192.168.X.X IP addresses are private (and cannot be accessed outside of '''the Openstack cluster'''), the 134.117.X.X floating IP addresses can be accessed from '''the Carleton network''' and will allow you to access the wider Internet.		The 192.168.X.X IP addresses are private (and cannot be accessed outside of '''the Openstack cluster'''), the 134.117.X.X floating IP addresses can be accessed from '''the Carleton network''' and will allow you to access the wider Internet.

Lianyingzhao at 23:52, 29 December 2022

2022-12-29T23:52:42Z

← Older revision		Revision as of 23:52, 29 December 2022
Line 28:		Line 28:
	'''For emphasis: do not take snapshots!''' (see below)		'''For emphasis: do not take snapshots!''' (see below)

	You can create a VM on the SCS openstack by following [[COMP3000 Operating Systems ~~W22~~: Openstack Instructions \| '''these steps''']]. If you encouter any issue and would like more reading, SCS already has [https://carleton.ca/scs/tech-support/scs-open-stack/openstack-technical-support/ lots of documentation on openstack], including a [https://carleton.ca/scs/tech-support/scs-open-stack/openstack-technical-support/openstack-step-by-step-guide/ step-by-step guide].		You can create a VM on the SCS openstack by following [[COMP3000 Operating Systems W23: Openstack Instructions \| '''these steps''']]. If you encouter any issue and would like more reading, SCS already has [https://carleton.ca/scs/tech-support/scs-open-stack/openstack-technical-support/ lots of documentation on openstack], including a [https://carleton.ca/scs/tech-support/scs-open-stack/openstack-technical-support/openstack-step-by-step-guide/ step-by-step guide].

	Make sure of the key steps: ①Carleton VPN, ②refresh your SCS account if needed, ③the COMP3000-W23 project, ④the COMP3000-W23-image '''snapshot''' image, ⑤adding the ping-ssh-egress security group, and ⑥associating a floating IP address.		Make sure of the key steps: ①Carleton VPN, ②refresh your SCS account if needed, ③the COMP3000-W23 project, ④the COMP3000-W23-image '''snapshot''' image, ⑤adding the ping-ssh-egress security group, and ⑥associating a floating IP address.

Lianyingzhao: /* Tasks/Questions */

2022-12-29T07:31:58Z

Tasks/Questions

← Older revision		Revision as of 07:31, 29 December 2022
Line 129:		Line 129:
	# What does it mean to have execute permission on a directory?		# What does it mean to have execute permission on a directory?
	# The <tt>ls</tt> command can be used to get a listing of the files in a directory. What options are passed to <tt>ls</tt> to see: the permission bits above; all the files within a directory (including hidden files)? How to make a file hidden?		# The <tt>ls</tt> command can be used to get a listing of the files in a directory. What options are passed to <tt>ls</tt> to see: the permission bits above; all the files within a directory (including hidden files)? How to make a file hidden?
	# Compile and run [https://people.scs.carleton.ca/~lianyingzhao/comp3000/~~w22~~/tut1/csimpleshell.c <tt>csimpleshell.c</tt>]. <u>How does its functionality compare to that of <tt>bash</tt></u>? List at least 3 differences.		# Compile and run [https://people.scs.carleton.ca/~lianyingzhao/comp3000/w23/tut1/csimpleshell.c <tt>csimpleshell.c</tt>]. <u>How does its functionality compare to that of <tt>bash</tt></u>? List at least 3 differences.

Lianyingzhao: /* Tasks/Questions */

2022-12-29T07:30:16Z

Tasks/Questions

← Older revision		Revision as of 07:30, 29 December 2022
Line 123:		Line 123:
	#* For the program you just compiled above, what if you used <tt>hello</tt> to run it instead of <tt>./hello</tt> (and why)?		#* For the program you just compiled above, what if you used <tt>hello</tt> to run it instead of <tt>./hello</tt> (and why)?
	#* Figure out where at least three external commands reside on the system.		#* Figure out where at least three external commands reside on the system.
	# Making your own commands: the <tt>PATH</tt> environment variable lists the directories the shell uses to search for external commands. Where can you find documentation on it? How can you add the current directory (whichever directory you are currently in) to PATH? Then, how to make that change permanent? Try to identify multiple ways.		# Making your own commands: the <tt>PATH</tt> environment variable lists the directories the shell uses to search for external commands. Where can you find documentation on it? How can you add the current directory (whichever directory you are currently in) to PATH? Then, how to make that change permanent? Try to identify multiple ways. You can now revisit the question about "hello" above.
	You can now revisit the question about "hello" above.
	# Look at the permissions of the program binaries of the external commands you have just found above. Who owns them? What group are they in?		# Look at the permissions of the program binaries of the external commands you have just found above. Who owns them? What group are they in?
	# For those same program binaries, figure out what the permission bits mean by reading the man page of <tt>chmod</tt> (this is the command you could use to change those permission bits).		# For those same program binaries, figure out what the permission bits mean by reading the man page of <tt>chmod</tt> (this is the command you could use to change those permission bits).

Lianyingzhao: /* Tasks/Questions */

2022-12-29T07:29:58Z

Tasks/Questions

← Older revision		Revision as of 07:29, 29 December 2022
Line 124:		Line 124:
	#* Figure out where at least three external commands reside on the system.		#* Figure out where at least three external commands reside on the system.
	# Making your own commands: the <tt>PATH</tt> environment variable lists the directories the shell uses to search for external commands. Where can you find documentation on it? How can you add the current directory (whichever directory you are currently in) to PATH? Then, how to make that change permanent? Try to identify multiple ways.		# Making your own commands: the <tt>PATH</tt> environment variable lists the directories the shell uses to search for external commands. Where can you find documentation on it? How can you add the current directory (whichever directory you are currently in) to PATH? Then, how to make that change permanent? Try to identify multiple ways.
	You can now revisit the question about "hello" above.		You can now revisit the question about "hello" above.
	# Look at the permissions of the program binaries of the external commands you have just found above. Who owns them? What group are they in?		# Look at the permissions of the program binaries of the external commands you have just found above. Who owns them? What group are they in?
	# For those same program binaries, figure out what the permission bits mean by reading the man page of <tt>chmod</tt> (this is the command you could use to change those permission bits).		# For those same program binaries, figure out what the permission bits mean by reading the man page of <tt>chmod</tt> (this is the command you could use to change those permission bits).

Lianyingzhao: /* Tasks/Questions */

2022-12-29T07:29:30Z

Tasks/Questions

← Older revision		Revision as of 07:29, 29 December 2022
Line 124:		Line 124:
	#* Figure out where at least three external commands reside on the system.		#* Figure out where at least three external commands reside on the system.
	# Making your own commands: the <tt>PATH</tt> environment variable lists the directories the shell uses to search for external commands. Where can you find documentation on it? How can you add the current directory (whichever directory you are currently in) to PATH? Then, how to make that change permanent? Try to identify multiple ways.		# Making your own commands: the <tt>PATH</tt> environment variable lists the directories the shell uses to search for external commands. Where can you find documentation on it? How can you add the current directory (whichever directory you are currently in) to PATH? Then, how to make that change permanent? Try to identify multiple ways.
			You can now revisit the question about "hello" above.
	# Look at the permissions of the program binaries of the external commands you have just found above. Who owns them? What group are they in?		# Look at the permissions of the program binaries of the external commands you have just found above. Who owns them? What group are they in?
	# For those same program binaries, figure out what the permission bits mean by reading the man page of <tt>chmod</tt> (this is the command you could use to change those permission bits).		# For those same program binaries, figure out what the permission bits mean by reading the man page of <tt>chmod</tt> (this is the command you could use to change those permission bits).

Lianyingzhao: /* Tasks/Questions */

2022-12-29T07:27:12Z

Tasks/Questions

← Older revision		Revision as of 07:27, 29 December 2022
Line 120:		Line 120:
	#* The name (binary path) of the current shell.		#* The name (binary path) of the current shell.
	# Using the <tt>man</tt> command, find out what the following commands do: <tt>which</tt>, <tt>pwd</tt>, <tt>who</tt>, <tt>whoami</tt>, <tt>whereis</tt>, and <tt>whatis</tt>.		# Using the <tt>man</tt> command, find out what the following commands do: <tt>which</tt>, <tt>pwd</tt>, <tt>who</tt>, <tt>whoami</tt>, <tt>whereis</tt>, and <tt>whatis</tt>.
	# Linux commands can be classified as internal (built into the shell) and external (separate program binaries). <u>How can you tell</u> if a specific command (e.g., <tt>cd</tt>) is internal or external? Figure out where at least three external commands reside on the system.		# Linux commands can be classified as internal (built into the shell) and external (separate program binaries). <u>How can you tell</u> if a specific command (e.g., <tt>cd</tt>) is internal or external?
			#* For the program you just compiled above, what if you used <tt>hello</tt> to run it instead of <tt>./hello</tt> (and why)?
			#* Figure out where at least three external commands reside on the system.
	# Making your own commands: the <tt>PATH</tt> environment variable lists the directories the shell uses to search for external commands. Where can you find documentation on it? How can you add the current directory (whichever directory you are currently in) to PATH? Then, how to make that change permanent? Try to identify multiple ways.		# Making your own commands: the <tt>PATH</tt> environment variable lists the directories the shell uses to search for external commands. Where can you find documentation on it? How can you add the current directory (whichever directory you are currently in) to PATH? Then, how to make that change permanent? Try to identify multiple ways.
	# Look at the permissions of the program binaries of the external commands you have just found above. Who owns them? What group are they in?		# Look at the permissions of the program binaries of the external commands you have just found above. Who owns them? What group are they in?

Lianyingzhao: /* Tasks/Questions */

2022-12-29T07:22:59Z

Tasks/Questions

← Older revision		Revision as of 07:22, 29 December 2022
Line 117:		Line 117:
	# When you have first logged in to a shell, <u>how</u> (i.e., using what commands?) can you find out information about the environment? Consider the following as examples. Try to find out mutiple ways for each (if you can).		# When you have first logged in to a shell, <u>how</u> (i.e., using what commands?) can you find out information about the environment? Consider the following as examples. Try to find out mutiple ways for each (if you can).
	#* The version of your Linux distribution (in our case, Ubuntu) and the version of your Linux kernel.		#* The version of your Linux distribution (in our case, Ubuntu) and the version of your Linux kernel.
	#* RAM, remaining/total disk space, and CPU.		#* RAM (remaining/total), disk space (remaining/total), and CPU.
	#* The name (binary path) of the current shell.		#* The name (binary path) of the current shell.
	# Using the <tt>man</tt> command, find out what the following commands do: <tt>which</tt>, <tt>pwd</tt>, <tt>who</tt>, <tt>whoami</tt>, <tt>whereis</tt>, and <tt>whatis</tt>.		# Using the <tt>man</tt> command, find out what the following commands do: <tt>which</tt>, <tt>pwd</tt>, <tt>who</tt>, <tt>whoami</tt>, <tt>whereis</tt>, and <tt>whatis</tt>.