class_22 - Software Engineering 3156 26-Nov-01 #22: OS,...

Info iconThis preview shows pages 1–11. Sign up to view the full content.

View Full Document Right Arrow Icon
Software Engineering 3156 26-Nov-01 #22: OS, Language, Design Patterns Phil Gross
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
2 Administrivia Research Fair Nov 30 th , 10am-4pm http://www.cs.columbia.edu/acm/research Advanced Perl Networking and OO Tuesday, Nov 27 th , 6-8pm JSP and Servlets Wednesday, Nov 28 th , 6-8pm
Background image of page 2
3 Systems Programming Unix, Windows (and JVM) all written in C/C++ Couldn’t write a JVM for a bare system in Java Need access to underlying system resources Located at particular memory locations Operating system provides (very) basic services System calls
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
4 System Calls Man page section 2, not 3 Or weirder sections, particularly for Solaris That is the sum total of what an OS does It usually also comes with a bunch of software Systems programming involves dealing directly with the system calls, or just above
Background image of page 4
5 Typical System Calls File access Time and date Process management Signals Networking Security
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
6 File I/O open, creat, close read, write Pure byte-oriented
Background image of page 6
7 Unix and Devices Everything’s a file Devices are “special files” Character or block oriented Character devs include some weird things Mice Audio Block devices are storage Mknod
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
8 Filesystems Sorta part of the OS Usually abstracted and modularized Primitive version has one filesystem per “volume” Unix model has “mount points” Hard links vs. soft links
Background image of page 8
9 Special Filesystems /proc Virtual filesystem Access to all kinds of information Originally processes NFS Network filesystem RPC based Journalling Filesystems
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
10 Processes The fork model Copy on write Vfork Most processes are sleeping/waiting at any given time Scheduler in kernel picks from among the ready processes for the next time slice
Background image of page 10
Image of page 11
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 06/09/2010 for the course COMS 3156 taught by Professor Philgross during the Fall '01 term at Columbia.

Page1 / 33

class_22 - Software Engineering 3156 26-Nov-01 #22: OS,...

This preview shows document pages 1 - 11. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online