Operating Systems 2015F: Tutorial 5 - Revision history

Soma at 19:05, 24 November 2015

2015-11-24T19:05:21Z

← Older revision		Revision as of 19:05, 24 November 2015
Line 1:		Line 1:
	In today's tutorial you will be getting your own virtual machine set up in OpenStack. Your tasks are as follows:		In today's tutorial you will be getting your own virtual machine set up in OpenStack. Your tasks are as follows:

			'''Note: the directions below have been updated.'''

	# Connect to the SCS Openstack web portal at https://openstack.scs.carleton.ca		# Connect to the SCS Openstack web portal at https://openstack.scs.carleton.ca
Line 19:		Line 21:
	# Build the kernel by running "make bzImage"		# Build the kernel by running "make bzImage"
	# Build the modules by running "make modules"		# Build the modules by running "make modules"
			# Install the modules by running "sudo make modules_install" ('''Do this before make install.''')
	# Install the kernel by running "sudo make install"		# Install the kernel by running "sudo make install"
	~~# Install the modules by running "sudo make modules_install"~~
	# While waiting for your kernel to build, try tracing various kernel events in /sys/kernel/debug/tracing as detailed in Lecture 11. Try to trace:		# While waiting for your kernel to build, try tracing various kernel events in /sys/kernel/debug/tracing as detailed in Lecture 11. Try to trace:
	#* entry to the chdir system call		#* entry to the chdir system call
Line 30:		Line 32:
	* It is very easy to make your instance not bootable by installing a bad kernel. Before installing a new kernel verify that you can choose which kernel you boot from the console by hitting escape and getting the boot menu. You may also want to increase the timeout from 5 seconds to something longer, e.g. 30 or 60 seconds, in order to give you time to get to the console.		* It is very easy to make your instance not bootable by installing a bad kernel. Before installing a new kernel verify that you can choose which kernel you boot from the console by hitting escape and getting the boot menu. You may also want to increase the timeout from 5 seconds to something longer, e.g. 30 or 60 seconds, in order to give you time to get to the console.
	* You can configure a kernel an existing config file by copying it to .config and running "make oldconfig". A minimal config that works in the class VM is [http://homeostasis.scs.carleton.ca/~soma/os-2015f/code/minimal-config here]. Save it as ".config" in the top level of the kernel source directory.		* You can configure a kernel an existing config file by copying it to .config and running "make oldconfig". A minimal config that works in the class VM is [http://homeostasis.scs.carleton.ca/~soma/os-2015f/code/minimal-config here]. Save it as ".config" in the top level of the kernel source directory.
			* '''New:''' If you want to just build the modules your distribution kernel uses, then you should:
			*# Copy the config file for the currently running kernel from /boot to .config
			*# Run "make localmodconfig" to update the config file. Just hit return for any questions that it asks (accept the default answer).
			*# Run "make bzImage; make modules; sudo make modules_install; sudo make install". It should run much faster than building a kernel with all of the distribution's modules enabled.
	* Builds can take a long time! You can always redirect the output to a file and then walk away, however. For example, to build the kernel and redirect standard out and error to the file make.log, and put it in the background, just run <pre>make bzImage >& make.log &</pre>		* Builds can take a long time! You can always redirect the output to a file and then walk away, however. For example, to build the kernel and redirect standard out and error to the file make.log, and put it in the background, just run <pre>make bzImage >& make.log &</pre>
	* Remember you can ssh in to your instances! If you can't ssh, you probably forgot to add the instance to the ssh and ping security groups. Find the "Edit Security Groups" option and change it there. (Click around, you'll find it on one of the button menus for the instance.)		* Remember you can ssh in to your instances! If you can't ssh, you probably forgot to add the instance to the ssh and ping security groups. Find the "Edit Security Groups" option and change it there. (Click around, you'll find it on one of the button menus for the instance.)

Soma: /* Hints */

2015-11-14T18:21:31Z

Hints

← Older revision		Revision as of 18:21, 14 November 2015
Line 28:		Line 28:

	==Hints==		==Hints==
	* It is very easy to make your instance not bootable by installing a bad kernel. Before installing a new kernel verify that you can choose which kernel you boot from the console by hitting escape and getting the boot menu.		* It is very easy to make your instance not bootable by installing a bad kernel. Before installing a new kernel verify that you can choose which kernel you boot from the console by hitting escape and getting the boot menu. You may also want to increase the timeout from 5 seconds to something longer, e.g. 30 or 60 seconds, in order to give you time to get to the console.
	* You can configure a kernel an existing config file by copying it to .config and running "make oldconfig". A minimal config that works in the class VM is [http://homeostasis.scs.carleton.ca/~soma/os-2015f/code/minimal-config here]. Save it as ".config" in the top level of the kernel source directory.		* You can configure a kernel an existing config file by copying it to .config and running "make oldconfig". A minimal config that works in the class VM is [http://homeostasis.scs.carleton.ca/~soma/os-2015f/code/minimal-config here]. Save it as ".config" in the top level of the kernel source directory.
	* Builds can take a long time! You can always redirect the output to a file and then walk away, however. For example, to build the kernel and redirect standard out and error to the file make.log, and put it in the background, just run <pre>make bzImage >& make.log &</pre>		* Builds can take a long time! You can always redirect the output to a file and then walk away, however. For example, to build the kernel and redirect standard out and error to the file make.log, and put it in the background, just run <pre>make bzImage >& make.log &</pre>

Soma: /* Hints */

2015-11-14T18:09:07Z

Hints

← Older revision		Revision as of 18:09, 14 November 2015
Line 28:		Line 28:

	==Hints==		==Hints==
			* It is very easy to make your instance not bootable by installing a bad kernel. Before installing a new kernel verify that you can choose which kernel you boot from the console by hitting escape and getting the boot menu.
	* You can configure a kernel an existing config file by copying it to .config and running "make oldconfig". A minimal config that works in the class VM is [http://homeostasis.scs.carleton.ca/~soma/os-2015f/code/minimal-config here]. Save it as ".config" in the top level of the kernel source directory.		* You can configure a kernel an existing config file by copying it to .config and running "make oldconfig". A minimal config that works in the class VM is [http://homeostasis.scs.carleton.ca/~soma/os-2015f/code/minimal-config here]. Save it as ".config" in the top level of the kernel source directory.
	* Builds can take a long time! You can always redirect the output to a file and then walk away, however. For example, to build the kernel and redirect standard out and error to the file make.log, and put it in the background, just run <pre>make bzImage >& make.log &</pre>		* Builds can take a long time! You can always redirect the output to a file and then walk away, however. For example, to build the kernel and redirect standard out and error to the file make.log, and put it in the background, just run <pre>make bzImage >& make.log &</pre>

Soma: /* Hints */

2015-10-20T18:57:01Z

Hints

← Older revision		Revision as of 18:57, 20 October 2015
Line 30:		Line 30:
	* You can configure a kernel an existing config file by copying it to .config and running "make oldconfig". A minimal config that works in the class VM is [http://homeostasis.scs.carleton.ca/~soma/os-2015f/code/minimal-config here]. Save it as ".config" in the top level of the kernel source directory.		* You can configure a kernel an existing config file by copying it to .config and running "make oldconfig". A minimal config that works in the class VM is [http://homeostasis.scs.carleton.ca/~soma/os-2015f/code/minimal-config here]. Save it as ".config" in the top level of the kernel source directory.
	* Builds can take a long time! You can always redirect the output to a file and then walk away, however. For example, to build the kernel and redirect standard out and error to the file make.log, and put it in the background, just run <pre>make bzImage >& make.log &</pre>		* Builds can take a long time! You can always redirect the output to a file and then walk away, however. For example, to build the kernel and redirect standard out and error to the file make.log, and put it in the background, just run <pre>make bzImage >& make.log &</pre>
			* Remember you can ssh in to your instances! If you can't ssh, you probably forgot to add the instance to the ssh and ping security groups. Find the "Edit Security Groups" option and change it there. (Click around, you'll find it on one of the button menus for the instance.)
	* Note this configuration has no modules; however, previously the following modules were loaded (see below). However, the kernel works fine without them. Which of these modules need to be built and loaded? Why or why not?		* Note this configuration has no modules; however, previously the following modules were loaded (see below). However, the kernel works fine without them. Which of these modules need to be built and loaded? Why or why not?
	<pre>		<pre>

Soma: /* Hints */

2015-10-20T18:30:11Z

Hints

← Older revision		Revision as of 18:30, 20 October 2015
Line 30:		Line 30:
	* You can configure a kernel an existing config file by copying it to .config and running "make oldconfig". A minimal config that works in the class VM is [http://homeostasis.scs.carleton.ca/~soma/os-2015f/code/minimal-config here]. Save it as ".config" in the top level of the kernel source directory.		* You can configure a kernel an existing config file by copying it to .config and running "make oldconfig". A minimal config that works in the class VM is [http://homeostasis.scs.carleton.ca/~soma/os-2015f/code/minimal-config here]. Save it as ".config" in the top level of the kernel source directory.
	* Builds can take a long time! You can always redirect the output to a file and then walk away, however. For example, to build the kernel and redirect standard out and error to the file make.log, and put it in the background, just run <pre>make bzImage >& make.log &</pre>		* Builds can take a long time! You can always redirect the output to a file and then walk away, however. For example, to build the kernel and redirect standard out and error to the file make.log, and put it in the background, just run <pre>make bzImage >& make.log &</pre>
	* Note this configuration has no modules; however, previously the following modules were loaded (see below). However, the kernel works fine without them. Which of these modules need to be built and loaded? Why or why not? <pre>Module Size Used by		* Note this configuration has no modules; however, previously the following modules were loaded (see below). However, the kernel works fine without them. Which of these modules need to be built and loaded? Why or why not?
			<pre>
			Module Size Used by
	ppdev 20480 0		ppdev 20480 0
	kvm_intel 151552 0		kvm_intel 151552 0

Soma: /* Hints */

2015-10-20T18:29:54Z

Hints

← Older revision		Revision as of 18:29, 20 October 2015
Line 30:		Line 30:
	* You can configure a kernel an existing config file by copying it to .config and running "make oldconfig". A minimal config that works in the class VM is [http://homeostasis.scs.carleton.ca/~soma/os-2015f/code/minimal-config here]. Save it as ".config" in the top level of the kernel source directory.		* You can configure a kernel an existing config file by copying it to .config and running "make oldconfig". A minimal config that works in the class VM is [http://homeostasis.scs.carleton.ca/~soma/os-2015f/code/minimal-config here]. Save it as ".config" in the top level of the kernel source directory.
	* Builds can take a long time! You can always redirect the output to a file and then walk away, however. For example, to build the kernel and redirect standard out and error to the file make.log, and put it in the background, just run <pre>make bzImage >& make.log &</pre>		* Builds can take a long time! You can always redirect the output to a file and then walk away, however. For example, to build the kernel and redirect standard out and error to the file make.log, and put it in the background, just run <pre>make bzImage >& make.log &</pre>
	* Note this configuration has no modules; however, previously the following modules were loaded (see below). However, the kernel works fine without them. Which of these modules need to be built and loaded? Why or why not?<pre>Module Size Used by		* Note this configuration has no modules; however, previously the following modules were loaded (see below). However, the kernel works fine without them. Which of these modules need to be built and loaded? Why or why not? <pre>Module Size Used by
	ppdev 20480 0		ppdev 20480 0
	kvm_intel 151552 0		kvm_intel 151552 0

Soma: /* Hints */

2015-10-20T18:29:40Z

Hints

← Older revision		Revision as of 18:29, 20 October 2015
Line 30:		Line 30:
	* You can configure a kernel an existing config file by copying it to .config and running "make oldconfig". A minimal config that works in the class VM is [http://homeostasis.scs.carleton.ca/~soma/os-2015f/code/minimal-config here]. Save it as ".config" in the top level of the kernel source directory.		* You can configure a kernel an existing config file by copying it to .config and running "make oldconfig". A minimal config that works in the class VM is [http://homeostasis.scs.carleton.ca/~soma/os-2015f/code/minimal-config here]. Save it as ".config" in the top level of the kernel source directory.
	* Builds can take a long time! You can always redirect the output to a file and then walk away, however. For example, to build the kernel and redirect standard out and error to the file make.log, and put it in the background, just run <pre>make bzImage >& make.log &</pre>		* Builds can take a long time! You can always redirect the output to a file and then walk away, however. For example, to build the kernel and redirect standard out and error to the file make.log, and put it in the background, just run <pre>make bzImage >& make.log &</pre>
	* Note this configuration has no modules; however, previously the following modules were loaded (see below). However, the kernel works fine without them. Which of these modules need to be built and loaded? Why or why not?<pre>		* Note this configuration has no modules; however, previously the following modules were loaded (see below). However, the kernel works fine without them. Which of these modules need to be built and loaded? Why or why not?<pre>Module Size Used by
	Module Size Used by
	ppdev 20480 0		ppdev 20480 0
	kvm_intel 151552 0		kvm_intel 151552 0

Soma: /* Hints */

2015-10-20T18:29:25Z

Hints

← Older revision		Revision as of 18:29, 20 October 2015
Line 30:		Line 30:
	* You can configure a kernel an existing config file by copying it to .config and running "make oldconfig". A minimal config that works in the class VM is [http://homeostasis.scs.carleton.ca/~soma/os-2015f/code/minimal-config here]. Save it as ".config" in the top level of the kernel source directory.		* You can configure a kernel an existing config file by copying it to .config and running "make oldconfig". A minimal config that works in the class VM is [http://homeostasis.scs.carleton.ca/~soma/os-2015f/code/minimal-config here]. Save it as ".config" in the top level of the kernel source directory.
	* Builds can take a long time! You can always redirect the output to a file and then walk away, however. For example, to build the kernel and redirect standard out and error to the file make.log, and put it in the background, just run <pre>make bzImage >& make.log &</pre>		* Builds can take a long time! You can always redirect the output to a file and then walk away, however. For example, to build the kernel and redirect standard out and error to the file make.log, and put it in the background, just run <pre>make bzImage >& make.log &</pre>
	* Note this configuration has no modules; however, previously the following modules were loaded (see below). However, the kernel works fine without them. Which of these modules need to be built and loaded? Why or why not?		* Note this configuration has no modules; however, previously the following modules were loaded (see below). However, the kernel works fine without them. Which of these modules need to be built and loaded? Why or why not?<pre>
	<pre>
	Module Size Used by		Module Size Used by
	ppdev 20480 0		ppdev 20480 0

Soma: /* Hints */

2015-10-20T18:29:14Z

Hints

← Older revision		Revision as of 18:29, 20 October 2015
Line 29:		Line 29:
	==Hints==		==Hints==
	* You can configure a kernel an existing config file by copying it to .config and running "make oldconfig". A minimal config that works in the class VM is [http://homeostasis.scs.carleton.ca/~soma/os-2015f/code/minimal-config here]. Save it as ".config" in the top level of the kernel source directory.		* You can configure a kernel an existing config file by copying it to .config and running "make oldconfig". A minimal config that works in the class VM is [http://homeostasis.scs.carleton.ca/~soma/os-2015f/code/minimal-config here]. Save it as ".config" in the top level of the kernel source directory.
	* Builds can take a long time! You can always redirect the output to a file and then walk away, however. For example, to build the kernel and redirect standard out and error to the file make.log, and put it in the background, just run "make bzImage >& make.log &"		* Builds can take a long time! You can always redirect the output to a file and then walk away, however. For example, to build the kernel and redirect standard out and error to the file make.log, and put it in the background, just run <pre>make bzImage >& make.log &</pre>
	* Note this configuration has no modules; however, previously the following modules were loaded (see below). However, the kernel works fine without them. Which of these modules need to be built and loaded? Why or why not?		* Note this configuration has no modules; however, previously the following modules were loaded (see below). However, the kernel works fine without them. Which of these modules need to be built and loaded? Why or why not?
	<pre>		<pre>

Soma: /* Hints */

2015-10-20T18:28:51Z

Hints

← Older revision		Revision as of 18:28, 20 October 2015
Line 29:		Line 29:
	==Hints==		==Hints==
	* You can configure a kernel an existing config file by copying it to .config and running "make oldconfig". A minimal config that works in the class VM is [http://homeostasis.scs.carleton.ca/~soma/os-2015f/code/minimal-config here]. Save it as ".config" in the top level of the kernel source directory.		* You can configure a kernel an existing config file by copying it to .config and running "make oldconfig". A minimal config that works in the class VM is [http://homeostasis.scs.carleton.ca/~soma/os-2015f/code/minimal-config here]. Save it as ".config" in the top level of the kernel source directory.
			* Builds can take a long time! You can always redirect the output to a file and then walk away, however. For example, to build the kernel and redirect standard out and error to the file make.log, and put it in the background, just run "make bzImage >& make.log &"
	* Note this configuration has no modules; however, previously the following modules were loaded (see below). However, the kernel works fine without them. Which of these modules need to be built and loaded? Why or why not?		* Note this configuration has no modules; however, previously the following modules were loaded (see below). However, the kernel works fine without them. Which of these modules need to be built and loaded? Why or why not?
	<pre>		<pre>