Operating Systems 2021F: Tutorial 1 - Revision history

Soma: /* Setting up and connecting a VM */

2021-10-25T16:57:27Z

Setting up and connecting a VM

← Older revision		Revision as of 16:57, 25 October 2021
Line 30:		Line 30:

	Create a VM on the SCS openstack cluster as shown in lecture. Make sure do the following:		Create a VM on the SCS openstack cluster as shown in lecture. Make sure do the following:
	* Choose the COMP3000A-2021F snapshot image ONLY (others won't have the right software for later tutorials),		* Choose the COMP3000A-2021F-* snapshot image ONLY (others won't have the right software for later tutorials), use the latest one.
	* Add the ping-ssh-egress security group, and		* Add the ping-ssh-egress security group, and
	* Associating a floating IP address.		* Associating a floating IP address.

Soma: /* Setting up and connecting a VM */

2021-09-16T19:42:43Z

Setting up and connecting a VM

← Older revision		Revision as of 19:42, 16 September 2021
Line 37:		Line 37:

	Once you are prompted to log in, the default user is student, default password is student. Please change your password after you first connect to your machine (using the passwd command).		Once you are prompted to log in, the default user is student, default password is student. Please change your password after you first connect to your machine (using the passwd command).

			You can also connect directly to your instance with ssh -J (proxy), going through access:

			ssh -J <SCS username>@access.scs.carleton.ca student@<Openstack floating IP address>

			(In lecture I showed a way to do this with two commands and -L. It is a more general solution, but this is much easier for what we want to do.)

	(Don't use the web console unless it is an emergency, it will be glitchy. Also, while you may use x2go to connect to this VM, we recommend connecting via ssh for faster performance.)		(Don't use the web console unless it is an emergency, it will be glitchy. Also, while you may use x2go to connect to this VM, we recommend connecting via ssh for faster performance.)

Soma: /* Cotrolling Processes */

2021-09-16T19:31:45Z

Cotrolling Processes

← Older revision		Revision as of 19:31, 16 September 2021
Line 128:		Line 128:
	One of the key reasons people choose alternatives to bash is because of quirks like this!		One of the key reasons people choose alternatives to bash is because of quirks like this!

	===~~Cotrolling~~ Processes===		===Controlling Processes===

	On Linux, you can control processes by sending them signals.		On Linux, you can control processes by sending them signals.

Soma: /* Background */

2021-09-16T15:39:10Z

Background

← Older revision		Revision as of 15:39, 16 September 2021
Line 61:		Line 61:

	Note that the topics in man pages go beyond just software & command manuals; they also include conventions and abstract concepts (e.g., <tt>man syscalls</tt> and <tt>man man-pages</tt>). Thus if you have questions, consider browsing the man pages rather than just going to a search engine.		Note that the topics in man pages go beyond just software & command manuals; they also include conventions and abstract concepts (e.g., <tt>man syscalls</tt> and <tt>man man-pages</tt>). Thus if you have questions, consider browsing the man pages rather than just going to a search engine.

			Note that <tt>whatis</tt> gives you a man summary, and <tt>apropos</tt> is a quick way to search man pages.

	===The Shell===		===The Shell===

Soma: /* Getting Started */

2021-09-14T16:07:31Z

Getting Started

← Older revision		Revision as of 16:07, 14 September 2021
Line 21:		Line 21:
	SCS 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]. Start here!		SCS 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]. Start here!

	Create a VM on the new SCS openstack cluster at [https://openstack-stein.scs.carleton.ca openstack-stein.scs.carleton.ca] and do your work there~~. Documentation on the cluster is [https://carleton.ca/scs/tech-support/scs-open-stack/ here]~~. While you don't need a persistent VM for this lab, it will be important for future tuturials - and it is nice to have your work stick around when you leave the lab.		Create a VM on the new SCS openstack cluster at [https://openstack-stein.scs.carleton.ca openstack-stein.scs.carleton.ca] and do your work there. While you don't need a persistent VM for this lab, it will be important for future tuturials - and it is nice to have your work stick around when you leave the lab.

	'''To access Openstack''' you must be on the Carleton network, so make sure to VPN in!		'''To access Openstack''' you must be on the Carleton network, so make sure to VPN in!

Soma: /* Connecting to Openstack */

2021-09-14T16:06:40Z

Connecting to Openstack

← Older revision		Revision as of 16:06, 14 September 2021
Line 18:		Line 18:

	===Connecting to Openstack===		===Connecting to Openstack===

			SCS 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]. Start here!

	Create a VM on the new SCS openstack cluster at [https://openstack-stein.scs.carleton.ca openstack-stein.scs.carleton.ca] and do your work there. Documentation on the cluster is [https://carleton.ca/scs/tech-support/scs-open-stack/ here]. While you don't need a persistent VM for this lab, it will be important for future tuturials - and it is nice to have your work stick around when you leave the lab.		Create a VM on the new SCS openstack cluster at [https://openstack-stein.scs.carleton.ca openstack-stein.scs.carleton.ca] and do your work there. Documentation on the cluster is [https://carleton.ca/scs/tech-support/scs-open-stack/ here]. While you don't need a persistent VM for this lab, it will be important for future tuturials - and it is nice to have your work stick around when you leave the lab.

Soma: /* Code */

2021-09-13T15:52:18Z

Code

← Older revision		Revision as of 15:52, 13 September 2021
Line 187:		Line 187:
	==Code==		==Code==

	===[http://~~homeostasis~~.scs.carleton.ca/~soma/os-2019w/code/csimpleshell.c csimpleshell.c]===		===[http://people.scs.carleton.ca/~soma/os-2019w/code/csimpleshell.c csimpleshell.c]===
	<syntaxhighlight line lang="C">		<syntaxhighlight line lang="C">
	/* csimpleshell.c, Enrico Franchi © 2005		/* csimpleshell.c, Enrico Franchi © 2005

Soma: /* Tasks/Questions */

2021-09-13T15:52:07Z

Tasks/Questions

← Older revision		Revision as of 15:52, 13 September 2021
Line 182:		Line 182:
	<li>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		<li>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?</tt>		to make a file hidden?</tt>
	<li>Compile and run [http://~~homeostasis~~.scs.carleton.ca/~soma/os-2019w/code/csimpleshell.c <tt>csimpleshell.c</tt>]. How does its functionality compare to that of bash? List at least 3 differences.</li>		<li>Compile and run [http://people.scs.carleton.ca/~soma/os-2019w/code/csimpleshell.c <tt>csimpleshell.c</tt>]. How does its functionality compare to that of bash? List at least 3 differences.</li>
	</ol>		</ol>

Soma: /* Downloading Code & Compiling Programs */

2021-09-13T15:51:51Z

Downloading Code & Compiling Programs

← Older revision		Revision as of 15:51, 13 September 2021
Line 144:		Line 144:
	To download C programs to your VM, use <tt>wget</tt> or <tt>curl</tt> commands:		To download C programs to your VM, use <tt>wget</tt> or <tt>curl</tt> commands:

	wget https://~~homeostasis~~.scs.carleton.ca/~soma/os-2017f/code/tut1/hello.c		wget https://people.scs.carleton.ca/~soma/os-2017f/code/tut1/hello.c
	curl https://~~homeostasis~~.scs.carleton.ca/~soma/os-2017f/code/tut1/hello.c -o hello.c		curl https://people.scs.carleton.ca/~soma/os-2017f/code/tut1/hello.c -o hello.c

	To compile, use gcc:		To compile, use gcc:

Soma: /* Tasks/Questions */

2021-09-13T03:11:39Z

Tasks/Questions

← Older revision		Revision as of 03:11, 13 September 2021
Line 172:		Line 172:
	<li> RAM, disk space, and CPU.</li>		<li> RAM, disk space, and CPU.</li>
	</ol>		</ol>
	<li>Using the man command, find out what the following commands do: <tt>which</tt>, <tt>pwd</tt>, <tt>who</tt>, <tt>whoami</tt>, and		<li>Using the man command, find out what the following commands do: <tt>which</tt>, <tt>pwd</tt>, <tt>who</tt>, <tt>whoami</tt>, <tt>env</tt> and
	<tt>whereis</tt>.</li>		<tt>whereis</tt>. Try using each of them.</li>
	<li>Linux commands can be classified as internal (built into the shell) and external (separate program binaries). How can you tell if a specific command (e.g., cd) is internal or external? Figure out where at least three external commands reside on the system.</li>		<li>Linux commands can be classified as internal (built into the shell) and external (separate program binaries). How can you tell if a specific command (e.g., cd) is internal or external? Figure out where at least three external commands reside on the system.</li>
	<li>Making your own commands: the PATH 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.</li>		<li>Making your own commands: the PATH 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.</li>