Operating Systems 2018F: Tutorial 5 - Revision history

Soma: /* Makefile */

2018-10-17T16:33:30Z

Makefile

← Older revision		Revision as of 16:33, 17 October 2018
Line 230:		Line 230:

	===Makefile===		===Makefile===
	<source lang="make">		<source lang="make" line>
	obj-m := ones.o		obj-m := ones.o
	KDIR := /lib/modules/$(shell uname -r)/build		KDIR := /lib/modules/$(shell uname -r)/build

Soma at 16:33, 17 October 2018

2018-10-17T16:33:11Z

← Older revision		Revision as of 16:33, 17 October 2018
Line 63:		Line 63:
	===simple.c===		===simple.c===

	<source lang="c">		<source lang="c" line>
	#include <linux/module.h>		#include <linux/module.h>
	#include <linux/init.h>		#include <linux/init.h>
Line 91:		Line 91:
	===Makefile===		===Makefile===

	<source lang="make">		<source lang="make" line>
	obj-m := simple.o		obj-m := simple.o
	KDIR := /lib/modules/$(shell uname -r)/build		KDIR := /lib/modules/$(shell uname -r)/build
Line 103:		Line 103:

	===ones.c===		===ones.c===
	<source lang="c">		<source lang="c" line>
	/* Code derived from:		/* Code derived from:
	https://appusajeev.wordpress.com/2011/06/18/writing-a-linux-character-device-driver/		https://appusajeev.wordpress.com/2011/06/18/writing-a-linux-character-device-driver/

Soma: /* Openstack */

2018-10-16T17:34:51Z

Openstack

← Older revision		Revision as of 17:34, 16 October 2018
Line 7:		Line 7:
	=Openstack=		=Openstack=

	See [[Operating Systems 2018F Lecture 8\|Lecture 8]] for a walkthrough of setting up an openstack instance. ~~‘’’Note~~ that you can do all of the following in Windows or MacOS.~~’’’~~ On Windows, you can use PuTTY as your SSH client (MacOS includes the ssh command). Key steps:		See [[Operating Systems 2018F Lecture 8\|Lecture 8]] for a walkthrough of setting up an openstack instance. '''Note that you can do all of the following in Windows or MacOS.''' On Windows, you can use PuTTY as your SSH client (MacOS includes the ssh command). Key steps:
	* Login at [https://openstack.scs.carleton.ca openstack.scs.carleton.ca] (you need to be connected to the Carleton network, either directly or via VPN).		* Login at [https://openstack.scs.carleton.ca openstack.scs.carleton.ca] (you need to be connected to the Carleton network, either directly or via VPN).
	* If you can't log in, change your SCS password (this updates your openstack credentials).		* If you can't log in, change your SCS password (this updates your openstack credentials).

Soma: /* Openstack */

2018-10-16T17:33:50Z

Openstack

← Older revision		Revision as of 17:33, 16 October 2018
Line 7:		Line 7:
	=Openstack=		=Openstack=

	See [[Operating Systems 2018F Lecture 8\|Lecture 8]] for a walkthrough of setting up an openstack instance. Key steps:		See [[Operating Systems 2018F Lecture 8\|Lecture 8]] for a walkthrough of setting up an openstack instance. ‘’’Note that you can do all of the following in Windows or MacOS.’’’ On Windows, you can use PuTTY as your SSH client (MacOS includes the ssh command). Key steps:
	* Login at [https://openstack.scs.carleton.ca openstack.scs.carleton.ca] (you need to be connected to the Carleton network, either directly or via VPN).		* Login at [https://openstack.scs.carleton.ca openstack.scs.carleton.ca] (you need to be connected to the Carleton network, either directly or via VPN).
	* If you can't log in, change your SCS password (this updates your openstack credentials).		* If you can't log in, change your SCS password (this updates your openstack credentials).

Soma at 17:31, 16 October 2018

2018-10-16T17:31:51Z

← Older revision		Revision as of 17:31, 16 October 2018
Line 11:		Line 11:
	* If you can't log in, change your SCS password (this updates your openstack credentials).		* If you can't log in, change your SCS password (this updates your openstack credentials).
	* Create an instance by going to Images, selecting one of the public images, and then launching an instance based on it. Be sure to give it a name (your username dash a number, e.g. anilsomayaji-1) and enable ssh & ping access under "Access control". We suggest using the image "ubuntu_18.04_x64_openstack_lightapps_desktop_2018-09-28", but any other ubuntu 18.04 image should work (although you may need to install extra packages, see below).		* Create an instance by going to Images, selecting one of the public images, and then launching an instance based on it. Be sure to give it a name (your username dash a number, e.g. anilsomayaji-1) and enable ssh & ping access under "Access control". We suggest using the image "ubuntu_18.04_x64_openstack_lightapps_desktop_2018-09-28", but any other ubuntu 18.04 image should work (although you may need to install extra packages, see below).
	* ~~Assign~~ your instance a globally routable visible IP address (rather than a private 192.168.X.X address).		* After your instance has started, assign your instance a globally routable visible IP address (rather than a private 192.168.X.X address).
	* Connect to your instance via ssh or x2go. Remember the default username is "student" and the password is "student". '''Please change your password!''' Use the <tt>passwd</tt> command or GUI tools for managing users.		* Connect to your instance via ssh or x2go. Remember the default username is "student" and the password is "student". '''Please change your password!''' Use the <tt>passwd</tt> command or GUI tools for managing users.
	* (Please don't try to create any snapshots, you can't - it will just get queued up and won't succeed.)		* (Please don't try to create any snapshots, you can't - it will just get queued up and won't succeed.)

Soma: /* Openstack */

2018-10-16T17:24:13Z

Openstack

← Older revision		Revision as of 17:24, 16 October 2018
Line 20:		Line 20:
	sudo apt install build-essential		sudo apt install build-essential
	sudo apt clean		sudo apt clean
			When upgrading you may get a message when upgrading grub about which boot device to use. Select /dev/vda or /dev/sda - don’t select the devices that end with a number.

	If your build failed before doing this and again after, delete the downloaded code and unpack the zip file again. (The build process generates hidden files which can mess up later builds.)		If your build failed before doing this and again after, delete the downloaded code and unpack the zip file again. (The build process generates hidden files which can mess up later builds.)

Soma: /* Openstack */

2018-10-15T19:34:22Z

Openstack

← Older revision		Revision as of 19:34, 15 October 2018
Line 16:		Line 16:

	'''If you cannot build a module''' you may have installed a version of ubuntu that is too minimal. But you can fix it by installing the right packages. Do the following:		'''If you cannot build a module''' you may have installed a version of ubuntu that is too minimal. But you can fix it by installing the right packages. Do the following:
	apt update		sudo apt update
	apt dist-upgrade		sudo apt dist-upgrade
	apt install build-essential		sudo apt install build-essential
	apt clean		sudo apt clean
	If your build failed before doing this and again after, delete the downloaded code and unpack the zip file again. (The build process generates hidden files which can mess up later builds.)		If your build failed before doing this and again after, delete the downloaded code and unpack the zip file again. (The build process generates hidden files which can mess up later builds.)

Soma: /* Openstack */

2018-10-15T19:34:04Z

Openstack

← Older revision		Revision as of 19:34, 15 October 2018
Line 19:		Line 19:
	apt dist-upgrade		apt dist-upgrade
	apt install build-essential		apt install build-essential
			apt clean
	If your build failed before doing this and again after, delete the downloaded code and unpack the zip file again. (The build process generates hidden files which can mess up later builds.)		If your build failed before doing this and again after, delete the downloaded code and unpack the zip file again. (The build process generates hidden files which can mess up later builds.)

Soma: /* Openstack */

2018-10-15T19:33:27Z

Openstack

← Older revision		Revision as of 19:33, 15 October 2018
Line 12:		Line 12:
	* Create an instance by going to Images, selecting one of the public images, and then launching an instance based on it. Be sure to give it a name (your username dash a number, e.g. anilsomayaji-1) and enable ssh & ping access under "Access control". We suggest using the image "ubuntu_18.04_x64_openstack_lightapps_desktop_2018-09-28", but any other ubuntu 18.04 image should work (although you may need to install extra packages, see below).		* Create an instance by going to Images, selecting one of the public images, and then launching an instance based on it. Be sure to give it a name (your username dash a number, e.g. anilsomayaji-1) and enable ssh & ping access under "Access control". We suggest using the image "ubuntu_18.04_x64_openstack_lightapps_desktop_2018-09-28", but any other ubuntu 18.04 image should work (although you may need to install extra packages, see below).
	* Assign your instance a globally routable visible IP address (rather than a private 192.168.X.X address).		* Assign your instance a globally routable visible IP address (rather than a private 192.168.X.X address).
	* Connect to your instance via ssh or x2go. Remember the default username is "student" and the password is "student". Please change your password!		* Connect to your instance via ssh or x2go. Remember the default username is "student" and the password is "student". '''Please change your password!''' Use the <tt>passwd</tt> command or GUI tools for managing users.
	* (Please don't try to create any snapshots, you can't - it will just get queued up and won't succeed.)		* (Please don't try to create any snapshots, you can't - it will just get queued up and won't succeed.)

Soma: /* Openstack */

2018-10-15T19:27:55Z

Openstack

← Older revision		Revision as of 19:27, 15 October 2018
Line 19:		Line 19:
	apt dist-upgrade		apt dist-upgrade
	apt install build-essential		apt install build-essential
			If your build failed before doing this and again after, delete the downloaded code and unpack the zip file again. (The build process generates hidden files which can mess up later builds.)

	(Note: You may encounter errors when trying to update the virtualbox VM. That is because that VM's disk is too small. You shouldn't encounter such issues on openstack.)		Note: You may encounter errors when trying to update the virtualbox VM. That is because that VM's disk is too small. You shouldn't encounter such issues on openstack.

	=Tasks=		=Tasks=