everything is a file main.c a.out /dev/sda1 /dev/tty2 /proc/cpuinfo file descriptor int
|
|
- Theodore Cross
- 1 years ago
- Views:
Transcription
1 everything is a file main.c a.out /dev/sda1 /dev/tty2 /proc/cpuinfo file descriptor int
2 #include <sys/types.h> #include <sys/stat.h> #include <fcntl.h> int open(const char *path, int flags); flagso_rdonly O_WRONLY O_RDWR O_CREAT #include <unistd.h> int close(int fd);
3 #include <unistd.h> ssize_t read(int fd, void *buf, size_t n); fdnbuf #include <unistd.h> ssize_t write(int fd, const void *buf, size_t n); fdnbuf -1
4 #include "csapp.h" int main(int argc, char **argv) { int fd = Open(argv[0], O_RDONLY, 0); char buf[5]; ELF Read(fd, buf, 4); buf[4] = 0; } printf("%s\n", buf+1); return 0;
5 #include <unistd.h> int pipe(int fds[2]); fds[0] fds[1]
6 #include "csapp.h" int main(int argc, char **argv) { int fds[2]; char buf[6]; Hello Pipe(fds); Write(fds[1], "Hello", 5); Read(fds[0], buf, 5); buf[5] = 0; } printf("%s\n", buf); return 0;
7 #include "csapp.h" int main(int argc, char **argv) { int fds[2]; Pipe(fds); Hello if (Fork() == 0) { Sleep(1); Write(fds[1], "Hello", 5); } else { char buf[6]; Read(fds[0], buf, 5); buf[5] = 0; printf("%s\n", buf); } } return 0;
8 #include "csapp.h" int main(int argc, char **argv) { int fds[2]; char buf[6]; Pipe(fds); Hel low orl d Write(fds[1], "Hello", 5); Write(fds[1], "World", 5); Close(fds[1]); while (1) { ssize_t n = Read(fds[0], buf, 3); if (n == 0) break; buf[n] = 0; printf("%s\n", buf); } } return 0;
9 #include "csapp.h" int main(int argc, char **argv) { int fds[2]; Pipe(fds); Close } if (Fork() == 0) { Write(fds[1], "Hello", 5); Close(fds[1]); } else { // Close(fds[1]); while (1) { char buf[6]; ssize_t n = Read(fds[0], buf, 3); if (n == 0) break; buf[n] = 0; printf("%s\n", buf); } } return 0;
10 per-process shared by all processes shared by all processes fd 0 fd 1 fd 2 fd 3 fd Hello pipe(fds) Computer Systems: A Programmer s Perspective
11 per-process shared by all processes shared by all processes fd 0 fd 1 fd 2 fd 3 fd Hello pipe(fds) close(fds[1]) Computer Systems: A Programmer s Perspective
12 per-process shared by all processes shared by all processes fd 0 fd 1 fd 2 fd 3 fd Hello pipe(fds) Computer Systems: A Programmer s Perspective
13 per-process shared by all processes shared by all processes fd 0 fd 1 fd 2 fd 3 fd 4 fd 0 fd 1 fd 2 fd 3 fd pipe(fds) Hello fork Computer Systems: A Programmer s Perspective
14 per-process shared by all processes shared by all processes fd 0 fd 1 fd 2 fd 3 fd 4 fd 0 fd 1 fd 2 fd 3 fd pipe(fds) Hello close(fds[1]) fork Computer Systems: A Programmer s Perspective
15 per-process shared by all processes shared by all processes fd 0 fd 1 fd 2 fd 3 fd Hello close(fds[1]) exit pipe(fds) fork Computer Systems: A Programmer s Perspective
16 per-process shared by all processes shared by all processes fd 0 fd 1 fd 2 fd 3 fd Hello close(fds[1]) exit pipe(fds) fork close(fds[1]) Computer Systems: A Programmer s Perspective
17 #include "csapp.h" int main(int argc, char **argv) { int fds[2]; Pipe(fds); if (Fork() == 0) { char buf[6]; Sleep(2); while (Read(fds[0], buf, 6) > 0) { } } else { int i; for (i = 0; i < 20000; i++) Write(fds[1], "Hello", 5); printf("done\n"); } done Sleep(1) } return 0;
18 per-process shared by all processes shared by all processes fd 0 fd 1 fd 2 fd 3 fd Hello Computer Systems: A Programmer s Perspective
19 0 1 2
20 #include "csapp.h" int main() { char buffer[32]; int n; Write(1, "Your name? ", 11); n = Read(0, buffer, 32); Write(2, "Unknown: ", 9); Write(2, buffer, n); } return 0;
21 fork #include <unistd.h> int dup2(int oldfd, int newfd); newfd oldfd newfd
22 #include "csapp.h" int main() { pid_t pid; int fds[2], n; Pipe(fds); Got: Hello! printf 1 } pid = Fork(); if (pid == 0) { Dup2(fds[1], 1); printf("hello!"); } else { char buffer[32]; Close(fds[1]); Waitpid(pid, NULL, 0); n = Read(fds[0], buffer, 31); buffer[n] = 0; printf("got: %s\n",buffer); } return 0;
23 per-process shared by all processes shared by all processes fd 0 fd 1 fd 2 fd 3 fd pipe(fds) Computer Systems: A Programmer s Perspective
24 per-process shared by all processes shared by all processes fd 0 fd 1 fd 2 fd 3 fd 4 fd 0 fd 1 fd 2 fd 3 fd pipe(fds) fork Computer Systems: A Programmer s Perspective
25 per-process shared by all processes shared by all processes fd 0 fd 1 fd 2 fd 3 fd 4 fd 0 fd 1 fd 2 fd 3 fd pipe(fds) dup2(fds[1], 1) fork Computer Systems: A Programmer s Perspective
26 per-process shared by all processes shared by all processes fd 0 fd 1 fd 2 fd 3 fd 4 fd 0 fd 1 fd 2 fd 3 fd dup2 close(fds[0]) close(fds[1]) fork close(fds[1]) Computer Systems: A Programmer s Perspective
27 per-process shared by all processes shared by all processes fd 0 fd 1 fd 2 fd 3 fd Hello! dup2 printf exit fork close(fds[1]) Computer Systems: A Programmer s Perspective
28 $ cat *.c grep fork wc -l pipe(fdsa) catgrep pipe(fdsb) grepwc fork dup2(fdsa[1], 1) exec("/bin/cat", ) dup2(fdsa[0], 0) dup2(fdsb[1], 1) exec("/bin/grep", ) dup2(fdsb[0], 0) exec("/bin/wc", )
29 $ cat *.c grep fork wc -l pipe(fdsa) catgrep pipe(fdsb) grepwc fork dup2(fdsa[1], 1) exec("/bin/cat", ) dup2(fdsa[0], 0) dup2(fdsb[1], 1) exec("/bin/grep", ) dup2(fdsb[0], 0) exec("/bin/wc", ) exec close(fdsa[0]) close(fdsa[1]) close(fdsb[0]) close(fdsb[1])
30 $ cat *.c grep fork wc -l cat grep
31 int openreadwrite FILE* fopenfreadfwrite FILE* fdopen stdin fdopen(0, "r") stdout fdopen(1, "w") stderr fdopen(2, "w")
32 #include "csapp.h" #define ITERS int main() { int fds[2]; int i; #include "csapp.h" #define ITERS int main() { int fds[2]; int i; } Pipe(fds); if (Fork() == 0) { for (i = 0; i < ITERS; i++) Write(fds[1], "Hello", 5); } else { char buffer[5]; int n = 0; for (i = 0; i < ITERS; i++) n += Read(fds[0], buffer, 5); printf("%d\n", n); } return 0; } Pipe(fds); if (Fork() == 0) { FILE *out = fdopen(fds[1], "w"); for (i = 0; i < ITERS; i++) fwrite("hello", 1, 5, out); } else { FILE *in = fdopen(fds[0], "r"); char buffer[5]; int n = 0; for (i = 0; i < ITERS; i++) n += fread(buffer, 1, 5, in); printf("%d\n", n); } return 0;
33 #include "csapp.h" #define ITERS int main() { int fds[2]; int i; #include "csapp.h" #define ITERS int main() { int fds[2]; int i; } Pipe(fds); if (Fork() == 0) { for (i = 0; i < ITERS; i++) Write(fds[1], "Hello", 5); } else { char buffer[5]; int n = 0; for (i = 0; i < ITERS; i++) n += Read(fds[0], buffer, 5); printf("%d\n", n); } return 0; } Pipe(fds); if (Fork() == 0) { FILE *out = fdopen(fds[1], "w"); for (i = 0; i < ITERS; i++) fwrite("hello", 1, 5, out); } else { FILE *in = fdopen(fds[0], "r"); char buffer[5]; int n = 0; for (i = 0; i < ITERS; i++) n += fread(buffer, 1, 5, in); printf("%d\n", n); } return 0;
34 Read(, 5)
35 Read(, 5) read(, 5)
36 Read(, 5) read(, 5)
37 Read(, 5) read(, 5)
38 fread(, 5, )
39 fread(, 5, ) read(, 4096)
40 fread(, 5, ) read(, 4096) FILE
41 fread(, 5, ) FILE
42 fread(, 5, ) memcpy() FILE
43 Write(, 5)
44 Write(, 5) write(, 5)
45 Write(, 5) write(, 5)
46 Write(, 5) write(, 5)
47 fwrite(, 5, )
48 fwrite(, 5, ) memcpy() FILE
49 fwrite(, 5, ) write(, 4096) FILE
50 fflush() write(, 130) FILE
51 Unbuffered Block buffered Line buffered printf("hello\n");
52 Unbuffered Block buffered Line buffered It depends stderr isatty()
53 csapp.c sio_ rio_
Recitation 8: Tshlab + VM
Recitation 8: Tshlab + VM Instructor: TAs 1 Outline Labs Signals IO Virtual Memory 2 TshLab and MallocLab TshLab due Tuesday MallocLab is released immediately after Start early Do the checkpoint first,
CSC209H Lecture 6. Dan Zingaro. February 11, 2015
CSC209H Lecture 6 Dan Zingaro February 11, 2015 Zombie Children (Kerrisk 26.2) As with every other process, a child process terminates with an exit status This exit status is often of interest to the parent
Processes often need to communicate. CSCB09: Software Tools and Systems Programming. Solution: Pipes. Recall: I/O mechanisms in C
2017-03-06 Processes often need to communicate CSCB09: Software Tools and Systems Programming E.g. consider a shell pipeline: ps wc l ps needs to send its output to wc E.g. the different worker processes
CS 25200: Systems Programming. Lecture 14: Files, Fork, and Pipes
CS 25200: Systems Programming Lecture 14: Files, Fork, and Pipes Dr. Jef Turkstra 2018 Dr. Jeffrey A. Turkstra 1 Lecture 14 File table and descriptors Fork and exec Fd manipulation Pipes 2018 Dr. Jeffrey
System- Level I/O. Andrew Case. Slides adapted from Jinyang Li, Randy Bryant and Dave O Hallaron
System- Level I/O Andrew Case Slides adapted from Jinyang Li, Randy Bryant and Dave O Hallaron 1 Unix I/O and Files UNIX abstracts many things into files (just a series of bytes) All I/O devices are represented
System Programming. Pipes I
Content : by Dr. B. Boufama School of Computer Science University of Windsor Instructor: Dr. A. Habed adlane@cs.uwindsor.ca http://cs.uwindsor.ca/ adlane/60-256 Content Content 1 Review Signals and files
Contents. IPC (Inter-Process Communication) Representation of open files in kernel I/O redirection Anonymous Pipe Named Pipe (FIFO)
Pipes and FIFOs Prof. Jin-Soo Kim( jinsookim@skku.edu) TA JinHong Kim( jinhong.kim@csl.skku.edu) Computer Systems Laboratory Sungkyunkwan University http://csl.skku.edu Contents IPC (Inter-Process Communication)
Outline. OS Interface to Devices. System Input/Output. CSCI 4061 Introduction to Operating Systems. System I/O and Files. Instructor: Abhishek Chandra
Outline CSCI 6 Introduction to Operating Systems System I/O and Files File I/O operations File Descriptors and redirection Pipes and FIFOs Instructor: Abhishek Chandra 2 System Input/Output Hardware devices:
Preview. Interprocess Communication with Pipe. Pipe from the Parent to the child Pipe from the child to the parent FIFO popen() with r Popen() with w
Preview Interprocess Communication with Pipe Pipe from the Parent to the child Pipe from the child to the parent FIFO popen() with r Popen() with w COCS 350 System Software, Fall 2015 1 Interprocess Communication
UNIX System Programming. Overview. 1. A UNIX System. 2. Processes (review) 2.1. Context. Pipes/FIFOs
UNIX System Programming Pipes/FIFOs Overview 1. A UNIX System (review) 2. Processes (review) Objectives Look at UNIX support for interprocess communication (IPC) on a single machine Review processes pipes,
Princeton University Computer Science 217: Introduction to Programming Systems I/O Management
Princeton University Computer Science 7: Introduction to Programming Systems I/O Management From a student's readme: ====================== Stress Testing ====================== To stress out this program,
Operating System Labs. Yuanbin Wu
Operating System Labs Yuanbin Wu cs@ecnu Annoucement Next Monday (28 Sept): We will have a lecture @ 4-302, 15:00-16:30 DON'T GO TO THE LABORATORY BUILDING! TA email update: ecnucchuang@163.com ecnucchuang@126.com
628 Lecture Notes Week 4
628 Lecture Notes Week 4 (February 3, 2016) 1/8 628 Lecture Notes Week 4 1 Topics I/O Redirection Notes on Lab 4 Introduction to Threads Review Memory spaces #include #include int
System-Level I/O. Topics Unix I/O Robust reading and writing Reading file metadata Sharing files I/O redirection Standard I/O
System-Level I/O Topics Unix I/O Robust reading and writing Reading file metadata Sharing files I/O redirection Standard I/O A Typical Hardware System CPU chip register file ALU system bus memory bus bus
Chapter 3 Processes we will completely ignore threads today
Chapter 3 Processes we will completely ignore threads today Images from Silberschatz Pacific University 1 Process Define: Memory Regions: Loaded from executable file: ELF: Executable and Linkable Format
Pipes and FIFOs. Woo-Yeong Jeong Computer Systems Laboratory Sungkyunkwan University
Pipes and FIFOs Woo-Yeong Jeong (wooyeong@csl.skku.edu) Computer Systems Laboratory Sungkyunkwan University http://csl.skku.edu Open Files in Kernel How the Unix kernel represents open files? Two descriptors
Systems Programming. COSC Software Tools. Systems Programming. High-Level vs. Low-Level. High-Level vs. Low-Level.
Systems Programming COSC 2031 - Software Tools Systems Programming (K+R Ch. 7, G+A Ch. 12) The interfaces we use to work with the operating system In this case: Unix Programming at a lower-level Systems
Inter-process Communication using Pipes
Inter-process Communication using Pipes Dept. of Computer Science & Engineering 1 Pipes A pipe is a one-way communication channel that couples one process to another. Used only between processes that have
Princeton University Computer Science 217: Introduction to Programming Systems. I/O Management
Princeton University Computer Science 7: Introduction to Programming Systems I/O Management Goals of this Lecture Help you to learn about: The C/Unix file abstraction Standard C I/O Data structures & functions
COMP 2355 Introduction to Systems Programming
COMP 2355 Introduction to Systems Programming Christian Grothoff christian@grothoff.org http://grothoff.org/christian/ 1 Today sprintf scanf file IO fork 2 System Programming 101 Check return values of
Operating Systems. Lecture 06. System Calls (Exec, Open, Read, Write) Inter-process Communication in Unix/Linux (PIPE), Use of PIPE on command line
Operating Systems Lecture 06 System Calls (Exec, Open, Read, Write) Inter-process Communication in Unix/Linux (PIPE), Use of PIPE on command line March 04, 2013 exec() Typically the exec system call is
CMSC 216 Introduction to Computer Systems Lecture 17 Process Control and System-Level I/O
CMSC 216 Introduction to Computer Systems Lecture 17 Process Control and System-Level I/O Sections 8.2-8.5, Bryant and O'Hallaron PROCESS CONTROL (CONT.) CMSC 216 - Wood, Sussman, Herman, Plane 2 Signals
System-Level I/O : Introduction to Computer Systems 16 th Lecture, March 23, Instructors: Franz Franchetti & Seth Copen Goldstein
System-Level I/O 15-213: Introduction to Computer Systems 16 th Lecture, March 23, 2017 Instructors: Franz Franchetti & Seth Copen Goldstein 1 Today: Unix I/O and C Standard I/O Two sets: system-level
All the scoring jobs will be done by script
File I/O Prof. Jin-Soo Kim( jinsookim@skku.edu) TA Sanghoon Han(sanghoon.han@csl.skku.edu) Computer Systems Laboratory Sungkyunkwan University http://csl.skku.edu Announcement (1) All the scoring jobs
IC221: Systems Programming 12-Week Written Exam [SOLUTIONS]
IC221: Systems Programming 12-Week Written Exam [SOLUTIONS] April 2, 2014 Answer the questions in the spaces provided on the question sheets. If you run out of room for an answer, continue on the back
ECE 650 Systems Programming & Engineering. Spring 2018
ECE 650 Systems Programming & Engineering Spring 2018 Inter-process Communication (IPC) Tyler Bletsch Duke University Slides are adapted from Brian Rogers (Duke) Recall Process vs. Thread A process is
File I/O. Jin-Soo Kim Computer Systems Laboratory Sungkyunkwan University
File I/O Jin-Soo Kim (jinsookim@skku.edu) Computer Systems Laboratory Sungkyunkwan University http://csl.skku.edu Unix Files A Unix file is a sequence of m bytes: B 0, B 1,..., B k,..., B m-1 All I/O devices
File I/O. Dong-kun Shin Embedded Software Laboratory Sungkyunkwan University Embedded Software Lab.
1 File I/O Dong-kun Shin Embedded Software Laboratory Sungkyunkwan University http://nyx.skku.ac.kr Unix files 2 A Unix file is a sequence of m bytes: B 0, B 1,..., B k,..., B m-1 All I/O devices are represented
Final Exam. Fall Semester 2016 KAIST EE209 Programming Structures for Electrical Engineering. Name: Student ID:
Fall Semester 2016 KAIST EE209 Programming Structures for Electrical Engineering Final Exam Name: This exam is open book and notes. Read the questions carefully and focus your answers on what has been
Final Exam. Fall Semester 2016 KAIST EE209 Programming Structures for Electrical Engineering. Name: Student ID:
Fall Semester 2016 KAIST EE209 Programming Structures for Electrical Engineering Final Exam Name: This exam is open book and notes. Read the questions carefully and focus your answers on what has been
Contents. Programming Assignment 0 review & NOTICE. File IO & File IO exercise. What will be next project?
File I/O Prof. Jin-Soo Kim(jinsookim@skku.edu) TA - Dong-Yun Lee(dylee@csl.skku.edu) Computer Systems Laboratory Sungkyunkwan University http://csl.skku.edu Contents Programming Assignment 0 review & NOTICE
Unix programming interface for file I/O operations and pipes
Unix programming interface for file I/O operations and pipes M1 MOSIG Operating System Design Renaud Lachaize Acknowledgments Many ideas and slides in these lectures were inspired by or even borrowed from
File I/O. Woo-Yeong Jeong Computer Systems Laboratory Sungkyunkwan University
File I/O Woo-Yeong Jeong (wooyeong@csl.skku.edu) Computer Systems Laboratory Sungkyunkwan University http://csl.skku.edu Unix Files A Unix file is a sequence of m bytes: B 0, B 1,..., B k,..., B m-1 All
Naked C Lecture 6. File Operations and System Calls
Naked C Lecture 6 File Operations and System Calls 20 August 2012 Libc and Linking Libc is the standard C library Provides most of the basic functionality that we've been using String functions, fork,
Topics. Unix Pipes (CSE 422S) In A Nutshell. Ken Wong Washington University. Pipe (Unnamed FIFO) in the Shell.
Unix s (CSE 422S) Ken Wong Washington University kenw@wustl.edu www.arl.wustl.edu/~kenw Topics Interprocess Communication (IPC) with named and unnamed pipes»unbuffered I/O system calls (open, read, write,
CMPS 105 Systems Programming. Prof. Darrell Long E2.371
+ CMPS 105 Systems Programming Prof. Darrell Long E2.371 darrell@ucsc.edu + Chapter 3: File I/O 2 + File I/O 3 n What attributes do files need? n Data storage n Byte stream n Named n Non-volatile n Shared
OS COMPONENTS OVERVIEW OF UNIX FILE I/O. CS124 Operating Systems Fall , Lecture 2
OS COMPONENTS OVERVIEW OF UNIX FILE I/O CS124 Operating Systems Fall 2017-2018, Lecture 2 2 Operating System Components (1) Common components of operating systems: Users: Want to solve problems by using
What is a Process. Preview. What is a Process. What is a Process. Process Instruction Cycle. Process Instruction Cycle 3/14/2018.
Preview Process Control What is process? Process identifier A key concept in OS is the process Process a program in execution Once a process is created, OS not only reserve space (in Memory) for the process
Week 2 Intro to the Shell with Fork, Exec, Wait. Sarah Diesburg Operating Systems CS 3430
Week 2 Intro to the Shell with Fork, Exec, Wait Sarah Diesburg Operating Systems CS 3430 1 Why is the Shell Important? Shells provide us with a way to interact with the core system Executes programs on
CS 33. Shells and Files. CS33 Intro to Computer Systems XX 1 Copyright 2017 Thomas W. Doeppner. All rights reserved.
CS 33 Shells and Files CS33 Intro to Computer Systems XX 1 Copyright 2017 Thomas W. Doeppner. All rights reserved. Shells Command and scripting languages for Unix First shell: Thompson shell sh, developed
Contents. NOTICE & Programming Assignment 0 review. What will be next project? File IO & File IO exercise
File I/O Prof. Jin-Soo Kim( jinsookim@skku.edu) TA Dong-Yun Lee(dylee@csl.skku.edu) Computer Systems Laboratory Sungkyunkwan University http://csl.skku.edu Contents NOTICE & Programming Assignment 0 review
Process Management! Goals of this Lecture!
Process Management! 1 Goals of this Lecture! Help you learn about:" Creating new processes" Programmatically redirecting stdin, stdout, and stderr" (Appendix) communication between processes via pipes"
COSC Operating Systems Design, Fall Lecture Note: Unnamed Pipe and Shared Memory. Unnamed Pipes
COSC4740-01 Operating Systems Design, Fall 2001 Lecture Note: Unnamed Pipe and Shared Memory Unnamed Pipes Pipes are a form of Inter-Process Communication (IPC) implemented on Unix and Linux variants.
System-Level I/O March 31, 2005
15-213 The course that gives CMU its Zip! System-Level I/O March 31, 2005 Topics Unix I/O Robust reading and writing Reading file metadata Sharing files I/O redirection Standard I/O 21-io.ppt Unix I/O
I/O Management! Goals of this Lecture!
I/O Management! 1 Goals of this Lecture! Help you to learn about:" The Unix stream concept" Standard C I/O functions" Unix system-level functions for I/O" How the standard C I/O functions use the Unix
UNIX System Overview E. Im
UNIX System Overview 2009 E. Im 1 History of UNIX Adopted from Operating System Concepts by Abraham Silberschatz et al. For a full history, refer to http://www.levenez.com/unix General Characteristics
Input and Output System Calls
Chapter 2 Input and Output System Calls Internal UNIX System Calls & Libraries Using C --- 1011 OBJECTIVES Upon completion of this unit, you will be able to: Describe the characteristics of a file Open
System Calls and I/O. CS 241 January 27, Copyright : University of Illinois CS 241 Staff 1
System Calls and I/O CS 241 January 27, 2012 Copyright : University of Illinois CS 241 Staff 1 This lecture Goals Get you familiar with necessary basic system & I/O calls to do programming Things covered
Inter-Process Communication. Disclaimer: some slides are adopted from the book authors slides with permission 1
Inter-Process Communication Disclaimer: some slides are adopted from the book authors slides with permission 1 Today Inter-Process Communication (IPC) What is it? What IPC mechanisms are available? 2 Inter-Process
Basic OS Progamming Abstrac2ons
Basic OS Progamming Abstrac2ons Don Porter Recap We ve introduced the idea of a process as a container for a running program And we ve discussed the hardware- level mechanisms to transi2on between the
CSC209H Lecture 7. Dan Zingaro. February 25, 2015
CSC209H Lecture 7 Dan Zingaro February 25, 2015 Inter-process Communication (IPC) Remember that after a fork, the two processes are independent We re going to use pipes to let the processes communicate
I/O OPERATIONS. UNIX Programming 2014 Fall by Euiseong Seo
I/O OPERATIONS UNIX Programming 2014 Fall by Euiseong Seo Files Files that contain a stream of bytes are called regular files Regular files can be any of followings ASCII text Data Executable code Shell
Matt Ramsay CS 375 EXAM 2 Part 1
Matt Ramsay CS 375 EXAM 2 Part 1 Output: csserver:/home/mr56/cs375/exam2 > parent 1 75000 Multiples of 3 between 3 and 15000 add to 37507500 This total written to /home/mr56/tmp/file8771.out Multiples
Fall 2017 :: CSE 306. File Systems Basics. Nima Honarmand
File Systems Basics Nima Honarmand File and inode File: user-level abstraction of storage (and other) devices Sequence of bytes inode: internal OS data structure representing a file inode stands for index
CMPSC 311- Introduction to Systems Programming Module: Input/Output
CMPSC 311- Introduction to Systems Programming Module: Input/Output Professor Patrick McDaniel Fall 2014 Input/Out Input/output is the process of moving bytes into and out of the process space. terminal/keyboard
Processes COMPSCI 386
Processes COMPSCI 386 Elements of a Process A process is a program in execution. Distinct processes may be created from the same program, but they are separate execution sequences. call stack heap STACK
System-Level I/O. William J. Taffe Plymouth State University. Using the Slides of Randall E. Bryant Carnegie Mellon University
System-Level I/O William J. Taffe Plymouth State University Using the Slides of Randall E. Bryant Carnegie Mellon University Topics Unix I/O Robust reading and writing Reading file metadata Sharing files
CS 350 : COMPUTER SYSTEM CONCEPTS SAMPLE TEST 2 (OPERATING SYSTEMS PART) Student s Name: MAXIMUM MARK: 100 Time allowed: 70 minutes
CS 350 : COMPUTER SYSTEM CONCEPTS SAMPLE TEST 2 (OPERATING SYSTEMS PART) Student s Name: MAXIMUM MARK: 100 Time allowed: 70 minutes Q1 (30 marks) NOTE: Unless otherwise stated, the questions are with reference
Operating Systems 2230
Operating Systems 2230 Computer Science & Software Engineering Lecture 4: Operating System Services All operating systems provide service points through which a general application program may request
CPSC 410/611: File Management. What is a File?
CPSC 410/611: What is a file? Elements of file management File organization Directories File allocation Reading: Silberschatz, Chapter 10, 11 What is a File? A file is a collection of data elements, grouped
Application Programming Interfaces
Application Programming Interfaces Stefan D. Bruda Winter 2018 SYSTEM CALLS Machine 1 Machine 2 Application 1 Application 3 Application 4 Application 5 Application 2 API (system functions) API (system
CS 471 Operating Systems. Yue Cheng. George Mason University Fall 2017
CS 471 Operating Systems Yue Cheng George Mason University Fall 2017 Review: RAID 2 RAID o Idea: Build an awesome disk from small, cheap disks o Metrics: Capacity, performance, reliability 3 RAID o Idea:
Operating System Labs. Yuanbin Wu
Operating System Labs Yuanbin Wu cs@ecnu Announcement Project 1 due 21:00, Oct. 8 Operating System Labs Introduction of I/O operations Project 1 Sorting Operating System Labs Manipulate I/O System call
Chapter 3. File I/O. System Programming 熊博安國立中正大學資訊工程學系
Chapter 3. File I/O System Programming http://www.cs.ccu.edu.tw/~pahsiung/courses/sp 熊博安國立中正大學資訊工程學系 pahsiung@cs.ccu.edu.tw Class: EA-104 (05)2720411 ext. 33119 Office: EA-512 Textbook: Advanced Programming
File and Directories. Advanced Programming in the UNIX Environment
File and Directories Advanced Programming in the UNIX Environment stat Function #include int stat(const char *restrict pathname, struct stat *restrict buf ); int fstat(int fd, struct stat
Operating Systems, 142
Operating Systems, 142 Tas: Vadim Levit, Dan Brownstein, Ehud Barnea, Matan Drory and Yerry Sofer Practical Session 1, System Calls A few administrative notes Course homepage: http://www.cs.bgu.ac.il/~os142/
Computer Science 162, Fall 2014 David Culler University of California, Berkeley Midterm 2 November 14, 2014
Computer Science 162, Fall 2014 David Culler University of California, Berkeley Midterm 2 November 14, 2014 Name SID Login TA Name Section Time This is a closed book exam with one 2-sided page of notes
CS 33. Architecture and the OS. CS33 Intro to Computer Systems XIX 1 Copyright 2017 Thomas W. Doeppner. All rights reserved.
CS 33 Architecture and the OS CS33 Intro to Computer Systems XIX 1 Copyright 2017 Thomas W. Doeppner. All rights reserved. The Operating System My Program Mary s Program Bob s Program OS CS33 Intro to
UNIX input and output
UNIX input and output Disk files In UNIX a disk file is a finite sequence of bytes, usually stored on some nonvolatile medium. Disk files have names, which are called paths. We won t discuss file naming
Layers in a UNIX System. Create a new process. Processes in UNIX. fildescriptors streams pipe(2) labinstructions
Process Management Operating Systems Spring 2005 Layers in a UNIX System interface Library interface System call interface Lab Assistant Magnus Johansson magnusj@it.uu.se room 1442 postbox 54 (4th floor,
CSci 4061 Introduction to Operating Systems. IPC: Basics, Pipes
CSci 4061 Introduction to Operating Systems IPC: Basics, Pipes Communication IPC in Unix Pipes: most basic form of IPC in Unix process-process ps u jon grep tcsh // what happens? Pipe has a read-end (receive)
Pipelines, Forks, and Shell
Scribe Notes for CS61: 11/14/13 By David Becerra and Arvind Narayanan Pipelines, Forks, and Shell Anecdote on Pipelines: Anecdote 1: In 1964, Bell Labs manager Doug Mcllroy sent a memo stating that programs
Unix Basics Compiling and Using. CMPT 300 Operating Systems I Summer Segment 2: Unix Basics. Melissa O Neill
CMPT 300 Operating Systems I Summer 1999 Segment 2: Unix Basics Melissa O Neill Unix Basics Compiling and Using You had to learn how to do the basics on a Unix system, including: Look up a manual page
Outline. Relationship between file descriptors and open files
Outline 3 File I/O 3-1 3.1 File I/O overview 3-3 3.2 open(), read(), write(), and close() 3-7 3.3 The file offset and lseek() 3-21 3.4 Atomicity 3-30 3.5 Relationship between file descriptors and open
CS240: Programming in C
CS240: Programming in C Lecture 17: Processes, Pipes, and Signals Cristina Nita-Rotaru Lecture 17/ Fall 2013 1 Processes in UNIX UNIX identifies processes via a unique Process ID Each process also knows
Prepared by Prof. Hui Jiang Process. Prof. Hui Jiang Dept of Electrical Engineering and Computer Science, York University
EECS3221.3 Operating System Fundamentals No.2 Process Prof. Hui Jiang Dept of Electrical Engineering and Computer Science, York University How OS manages CPU usage? How CPU is used? Users use CPU to run
The Shell, System Calls, Processes, and Basic Inter-Process Communication
The Shell, System Calls, Processes, and Basic Inter-Process Communication Michael Jantz Dr. Prasad Kulkarni 1 Shell Programs A shell program provides an interface to the services of the operating system.
UNIVERSITY OF TORONTO Faculty of Arts and Science. St. George Campus DECEMBER 2017 EXAMINATIONS. CSC 209H1F Liu, Reid 3 hours. No Examination Aids
PLEASE HAND IN UNIVERSITY OF TORONTO Faculty of Arts and Science St. George Campus DECEMBER 2017 EXAMINATIONS CSC 209H1F Liu, Reid 3 hours PLEASE HAND IN No Examination Aids Student Number: Last (Family)
Implementation of Pipe under C in Linux. Tushar B. Kute,
Implementation of Pipe under C in Linux Tushar B. Kute, http://tusharkute.com Pipe We use the term pipe to mean connecting a data flow from one process to another. Generally you attach, or pipe, the output
10. I/O System Library
10. I/O System Library Header File #include // Found in C:\Nburn\include General File Descriptor Functions close --- Close open file descriptors read --- Read data from a file descriptor ReadWithTimeout
UNIX. Session 2. UNIX processes and forking fork system call exec system call death of process kill fork and I/O using it UNIX.
ProgrammingII Session 2 process handling processes and forking fork system call exec system call death of process kill fork and I/O using it ProgrammingII Short Course Notes Alan Dix 1996 II/20 process:
Lecture 14. Shell. File descriptors. File table and descriptors. Fork and exec Fd manipulation Pipes
218 Dr. Jeffrey A. Turkstra 1 Lecture 14 File table ad descriptors CS 252: Systems Programmig Lecture 14: Files, Fork, ad Pipes Fork ad exec Fd maipulatio Pipes Dr. Jef Turkstra 218 Dr. Jeffrey A. Turkstra
Lecture 21 Systems Programming in C
Lecture 21 Systems Programming in C A C program can invoke UNIX system calls directly. A system call can be defined as a request to the operating system to do something on behalf of the program. During
Prepared by Prof. Hui Jiang (COSC3221) 2/9/2007
1 * * ' &% $ # " "! 4 ' Prepared by Prof Hui Jiang COSC1 /9/007 / 0 How CPU is used? Users run programs in CPU In a multiprogramming system a CPU always has several jobs to run How to define a CPU job?
Computer Science & Engineering Department I. I. T. Kharagpur
Computer Science & Engineering Department I. I. T. Kharagpur Operating System: CS33007 3rd Year CSE: 5th Semester (Autumn 2006-2007) Lecture III (Linux System Calls II) Goutam Biswas Date: 1st-7th August,
COMP 2355 Introduction to Systems Programming
COMP 2355 Introduction to Systems Programming Christian Grothoff christian@grothoff.org http://grothoff.org/christian/ 1 Processes A process is an instance of a running program. Programs do not have to
Maria Hybinette, UGA. ! One easy way to communicate is to use files. ! File descriptors. 3 Maria Hybinette, UGA. ! Simple example: who sort
Two Communicating Processes Hello Gunnar CSCI 6730/ 4730 Operating Systems Process Chat Maria A Hi Nice to Hear from you Process Chat Gunnar B Dup & Concept that we want to implement 2 On the path to communication
Inter-process communication (IPC)
Inter-process communication (IPC) Operating Systems Kartik Gopalan References Chapter 5 of OSTEP book. Unix man pages Advanced Programming in Unix Environment by Richard Stevens http://www.kohala.com/start/apue.html
Communication. Serial port programming
Applied mechatronics Communication. Serial port programming Sven Gestegård Robertz sven.robertz@cs.lth.se Department of Computer Science, Lund University 2017 Outline 1 Introduction 2 Terminal I/O programming
T4-Input/Output Management
T4-Input/Output Management SO-Grade 2013-2014 Q2 License Aquest document es troba sota una llicència Reconeixement - No comercial - Compartir Igual sota la mateixa llicència 3.0 de Creative Commons. Per
Operating Systems. Lecture 07. System Calls, Input/Output and Error Redirection, Inter-process Communication in Unix/Linux
Operating Systems Lecture 07 System Calls, Input/Output and Error Redirection, Inter-process Communication in Unix/Linux March 11, 2013 Goals for Today Interprocess communication (IPC) Use of pipe in a
Shared Memory Memory mapped files
Shared Memory Memory mapped files 1 Shared Memory Introduction Creating a Shared Memory Segment Shared Memory Control Shared Memory Operations Using a File as Shared Memory 2 Introduction Shared memory
CSCI 4210 Operating Systems CSCI 6140 Computer Operating Systems Sample Final Exam Questions (document version 1.1) WITH SELECTED SOLUTIONS
CSCI 4210 Operating Systems CSCI 6140 Computer Operating Systems Sample Final Exam Questions (document version 1.1) WITH SELECTED SOLUTIONS Overview The final exam will be on Tuesday, May 17, 2016 from
File: /home/young/mywork/7.cordic_accuracy/ghdl/print.file Page 1 of 13
File: /home/young/mywork/7.cordic_accuracy/ghdl/print.file Page 1 of 13 makefile sendrecv.o: sendrecv.c gcc -c -Wall sendrecv.c cordic_vtb: sendrecv.o cordic_vtb.vhdl cp /home/young/mywork/5.cordic_vhdl/a.beh/cordic_pkg.vhdl.
#include <sys/types.h> #include <sys/wait.h> pid_t wait(int *stat_loc); pid_t waitpid(pid_t pid, int *stat_loc, int options);
pid_t fork(void); #include pid_t wait(int *stat_loc); pid_t waitpid(pid_t pid, int *stat_loc, int options); char **environ; int execl(const char *path, const char *arg0,..., (char *)0); int
Multi-Process Programming in C
Multi-Process Programming in C (2016/2017) Giuseppe Massari giuseppe.massari@polimi.it Outline 2/43 Multi-process programming Fork processes Inter-process synchronization Executing other programs Inter-Process
The link() System Call. Preview. The link() System Call. The link() System Call. The unlink() System Call 9/25/2017
Preview The link() System Call link(), unlink() System Call remove(), rename() System Call Symbolic link to directory Symbolic link to a executable file symlink() System Call File Times utime() System
CSCI0330 Intro Computer Systems Doeppner. Project C-Shell. Due: November 1, 2017 at 11:59pm
CSCI0330 Intro Computer Systems Doeppner Project C-Shell Due: November 1, 2017 at 11:59pm IMPORTANT: The TAs will start grading Shell 1 the day after it is due. Therefore, if you ve handed in and might
You are familiar with how to use pipes at the command level. A command such as
9 Interprocess Communication (IPC) Concepts Covered Pipes I/O Redirection FIFOs Concurrent Servers Daemons Multiplexed I/O with select() Sockets mknod, tee, API: accept, bind, connect, dup, dup2, fpathconf,
Lecture 3. Review of C Programming Tools Unix File I/O System Calls
Lecture 3 Review of C Programming Tools Unix File I/O System Calls Review of C Programming Tools Compilation Linkage The Four Stages of Compilation preprocessing compilation assembly linking gcc driver