Operating Systems 2017F Lecture 2 - Revision history

Jagger: fix hello world syntax highlighting

2017-10-04T03:55:15Z

fix hello world syntax highlighting

← Older revision		Revision as of 03:55, 4 October 2017
Line 59:		Line 59:
	Using fork() in a c program		Using fork() in a c program

			<syntaxhighlight lang="c">
	/* hello-world.c */		/* hello-world.c */

Line 65:		Line 66:

	int main() {		int main() {
	fork();		fork();
	fork();		fork();

	printf("Hello world! I'm %d. My parent is %d\n", getpid(), getppid());		printf("Hello world! I'm %d. My parent is %d\n", getpid(), getppid());
	return 42;		return 42;
	}		}
			</syntaxhighlight>

	'''What does the program do?'''		'''What does the program do?'''

Ssarazin at 01:54, 4 October 2017

2017-10-04T01:54:08Z

← Older revision		Revision as of 01:54, 4 October 2017
Line 6:		Line 6:

	Code and files from the lecture (captured as they were at the end) are available [http://homeostasis.scs.carleton.ca/~soma/os-2017f/code/lec02/ here].		Code and files from the lecture (captured as they were at the end) are available [http://homeostasis.scs.carleton.ca/~soma/os-2017f/code/lec02/ here].

			==Notes==
			'''What is a file?'''
			- A hierarchical name with a value mapping, accessed using the API "open, read, close, seek" (roughly). Open and close are used for efficiency; read and write do all of the work.

			'''Why is Unix and Linux interchangeable?'''
			- Linux is a variant of the Unix, it contains the Unix kernel with custom built layers on top.

			'''What is the architecture of the Unix kernel?'''
			- A system of hierarchical files that represent all of the different hardware devices
			for example: writing to stdout or reading from stdin. These are the computer monitor and keyborad file descriptors.

			'''How do we add new devices to the system?'''
			- We tell the operating system to mount the new device. The operating system responds with a file descriptor for the new device. Accessing the device means writing to its file.
			- There are many files that represent a device. We can trace these files by calling the command "lspci" which gets the PCI bus hardware device info from the kernel. Using the
			command "strace lspci" we can trace all of the system calls performed by lspci. Now we know exactly which files make up each device on the PCI bus.
			- file descriptors like /dev or /sys are conduits to the kernel. The kernel then performs operations on the hardware.

			The key point(s): The kernel abstracts the hardware by assigning file descriptors for every device. A program can gain information about the device using system calls to the kernel.

			'''Virtualizing Memory'''
			- Hard disks file descriptors appear as:
			- /dev/sda -> unencrypted drive
			- /dev/mapper… -> encrypted drive
			- We can see the filesystem using the "df" command or view the size of files using "df."
			- Why are some of the files showing a size of 0 bytes?
			- When memory is virtualized, the kernel builds the file system as it goes.

			'''Processes'''
			- '''What is a Process?'''
			- A running program
			- Just like the devices, every process gets a directory in the files system "/proc"
			- To view running process use the command "ps"
			- To stop a running process use the command "Kill <process id>"
			- '''What happens when multiple processes are created?'''
			- The operating system shares the resources between the processes using time sharing -- also called virtualizing the resources.
			- '''What is a shell in Linux?'''
			- Just another program that can access the operating system and run other programs
			- A shell can run multiple programs (processes), only control returns to the shell after the process has finished. To give the shell priority use the "&" to send the current process to
			the background. This idea demonstrates how the CPU is virtualized because it is being shared by the shell and the running process. The concept was demonstrated using xclock.
			- Use the "jobs" command to see which processes are running
			- Use the "ps aux" command to view the full command line of all running processes.
			- Use the "getpid()" function call in a c program to find the process id for the current process.
			- Use the "getppid()" function call in a c program to find the parents process id for the current process.
			- '''How do I make a process?'''
			- by copying the current process
			- fork(): a system call the clones the currently running process. The new process (child) begins executing from the statement that contained the call to fork().
			- fork() returns zero it means the child process is running.
			- fork() returns > 0 it means the parent process is running.
			- fork() returns < 0 it means the fork() failed.

			Using fork() in a c program

			/* hello-world.c */

			#include <stdio.h>
			#include <unistd.h>

			int main() {
			fork();
			fork();

			printf("Hello world! I'm %d. My parent is %d\n", getpid(), getppid());
			return 42;
			}

			'''What does the program do?'''
			- The first call to fork() clones a child process running the hello-world program. The child begins operating as if it just called fork(). Only the value returned from fork()
			is different for the child than the parent. The child process returns a zero.
			- Now there are two processes running concurrently, executing the same code. A parent process and a child process.
			- The parent process calls fork() again creating another child process, and the first child process also creates a child process. Now there are 4 processes running concurrently.
			- All 4 processes will print their process id and their parent's process id.
			- finally a return value of 42 is delivered to the parent of each process as it exits.
			- Important: The order of execution for each process is not deterministic. We do not know which process will run next because the operating system decides.

Soma at 20:48, 19 September 2017

2017-09-19T20:48:27Z

← Older revision		Revision as of 20:48, 19 September 2017
Line 1:		Line 1:
	==Video==		==Video==

	Video from the lecture given on September 12, 2017 [http://homeostasis.scs.carleton.ca/~soma/os-2017f/lectures/comp3000-2017f-lec02-12Sep2017.~~m4a~~ is now available].		Video from the lecture given on September 12, 2017 [http://homeostasis.scs.carleton.ca/~soma/os-2017f/lectures/comp3000-2017f-lec02-12Sep2017.mp4 is now available].

	==Code==		==Code==

	Code and files from the lecture (captured as they were at the end) are available [http://homeostasis.scs.carleton.ca/~soma/os-2017f/code/lec02/ here].		Code and files from the lecture (captured as they were at the end) are available [http://homeostasis.scs.carleton.ca/~soma/os-2017f/code/lec02/ here].

Soma at 00:24, 15 September 2017

2017-09-15T00:24:40Z

← Older revision		Revision as of 00:24, 15 September 2017
Line 2:		Line 2:

	Video from the lecture given on September 12, 2017 [http://homeostasis.scs.carleton.ca/~soma/os-2017f/lectures/comp3000-2017f-lec02-12Sep2017.m4a is now available].		Video from the lecture given on September 12, 2017 [http://homeostasis.scs.carleton.ca/~soma/os-2017f/lectures/comp3000-2017f-lec02-12Sep2017.m4a is now available].

			==Code==

			Code and files from the lecture (captured as they were at the end) are available [http://homeostasis.scs.carleton.ca/~soma/os-2017f/code/lec02/ here].

Soma at 00:22, 15 September 2017

2017-09-15T00:22:26Z

← Older revision		Revision as of 00:22, 15 September 2017
Line 1:		Line 1:
	==Video==		==Video==

	Video from the lecture given on September 12, 2017 [http://homeostasis.scs.carleton.ca/~soma/os-2017f/lectures/comp3000-2017f-lec02-~~12Sept2017~~.m4a is now available].		Video from the lecture given on September 12, 2017 [http://homeostasis.scs.carleton.ca/~soma/os-2017f/lectures/comp3000-2017f-lec02-12Sep2017.m4a is now available].

Soma at 01:32, 13 September 2017

2017-09-13T01:32:52Z

← Older revision		Revision as of 01:32, 13 September 2017
Line 1:		Line 1:
	==Video==		==Video==

	Video from the lecture given on September 12, 2017 [http://homeostasis.scs.carleton.ca/~soma/os-2017f/lectures/comp3000-2017f-lec02-~~12Sep2017~~.m4a is now available].		Video from the lecture given on September 12, 2017 [http://homeostasis.scs.carleton.ca/~soma/os-2017f/lectures/comp3000-2017f-lec02-12Sept2017.m4a is now available].

Soma: Created page with "==Video== Video from the lecture given on September 12, 2017 [http://homeostasis.scs.carleton.ca/~soma/os-2017f/lectures/comp3000-2017f-lec02-12Sep2017.m4a is now available]."

2017-09-13T01:31:57Z

Created page with "==Video== Video from the lecture given on September 12, 2017 [http://homeostasis.scs.carleton.ca/~soma/os-2017f/lectures/comp3000-2017f-lec02-12Sep2017.m4a is now available]."

New page

==Video==

Video from the lecture given on September 12, 2017 [http://homeostasis.scs.carleton.ca/~soma/os-2017f/lectures/comp3000-2017f-lec02-12Sep2017.m4a is now available].