DOCSLIB.ORG

Programming in the Linux Environment

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Programming in the Linux Environment Practical Computing-II Programming in the Linux Environment B.W.Gore March 20, 2015 0. An Introduction B.W.Gore Programming in the Linux Environment I 25 credits (33.33% weighting) I About Linux/Unix environment I Scripting Tools and Languages (like sed & awk) 1. boot-up sequence 2. kernel 3. Signals 4. programs vs. processes 5. permissions and access control 6. fork and exec 7. foreground and background processes About The Course I CMS M.2.2 Practical Computing-II B.W.Gore Programming in the Linux Environment I About Linux/Unix environment I Scripting Tools and Languages (like sed & awk) 1. boot-up sequence 2. kernel 3. Signals 4. programs vs. processes 5. permissions and access control 6. fork and exec 7. foreground and background processes About The Course I CMS M.2.2 Practical Computing-II I 25 credits (33.33% weighting) B.W.Gore Programming in the Linux Environment I Scripting Tools and Languages (like sed & awk) 1. boot-up sequence 2. kernel 3. Signals 4. programs vs. processes 5. permissions and access control 6. fork and exec 7. foreground and background processes About The Course I CMS M.2.2 Practical Computing-II I 25 credits (33.33% weighting) I About Linux/Unix environment B.W.Gore Programming in the Linux Environment 1. boot-up sequence 2. kernel 3. Signals 4. programs vs. processes 5. permissions and access control 6. fork and exec 7. foreground and background processes About The Course I CMS M.2.2 Practical Computing-II I 25 credits (33.33% weighting) I About Linux/Unix environment I Scripting Tools and Languages (like sed & awk) B.W.Gore Programming in the Linux Environment 2. kernel 3. Signals 4. programs vs. processes 5. permissions and access control 6. fork and exec 7. foreground and background processes About The Course I CMS M.2.2 Practical Computing-II I 25 credits (33.33% weighting) I About Linux/Unix environment I Scripting Tools and Languages (like sed & awk) 1. boot-up sequence B.W.Gore Programming in the Linux Environment 3. Signals 4. programs vs. processes 5. permissions and access control 6. fork and exec 7. foreground and background processes About The Course I CMS M.2.2 Practical Computing-II I 25 credits (33.33% weighting) I About Linux/Unix environment I Scripting Tools and Languages (like sed & awk) 1. boot-up sequence 2. kernel B.W.Gore Programming in the Linux Environment 4. programs vs. processes 5. permissions and access control 6. fork and exec 7. foreground and background processes About The Course I CMS M.2.2 Practical Computing-II I 25 credits (33.33% weighting) I About Linux/Unix environment I Scripting Tools and Languages (like sed & awk) 1. boot-up sequence 2. kernel 3. Signals B.W.Gore Programming in the Linux Environment 5. permissions and access control 6. fork and exec 7. foreground and background processes About The Course I CMS M.2.2 Practical Computing-II I 25 credits (33.33% weighting) I About Linux/Unix environment I Scripting Tools and Languages (like sed & awk) 1. boot-up sequence 2. kernel 3. Signals 4. programs vs. processes B.W.Gore Programming in the Linux Environment 6. fork and exec 7. foreground and background processes About The Course I CMS M.2.2 Practical Computing-II I 25 credits (33.33% weighting) I About Linux/Unix environment I Scripting Tools and Languages (like sed & awk) 1. boot-up sequence 2. kernel 3. Signals 4. programs vs. processes 5. permissions and access control B.W.Gore Programming in the Linux Environment 7. foreground and background processes About The Course I CMS M.2.2 Practical Computing-II I 25 credits (33.33% weighting) I About Linux/Unix environment I Scripting Tools and Languages (like sed & awk) 1. boot-up sequence 2. kernel 3. Signals 4. programs vs. processes 5. permissions and access control 6. fork and exec B.W.Gore Programming in the Linux Environment About The Course I CMS M.2.2 Practical Computing-II I 25 credits (33.33% weighting) I About Linux/Unix environment I Scripting Tools and Languages (like sed & awk) 1. boot-up sequence 2. kernel 3. Signals 4. programs vs. processes 5. permissions and access control 6. fork and exec 7. foreground and background processes B.W.Gore Programming in the Linux Environment I Familiarity with the basic Linux command line environment I Some experience in programming with the gcc and g++ compilers I Insights into how the system behaves in various circumstances Prerequisites I Linux account B.W.Gore Programming in the Linux Environment I Some experience in programming with the gcc and g++ compilers I Insights into how the system behaves in various circumstances Prerequisites I Linux account I Familiarity with the basic Linux command line environment B.W.Gore Programming in the Linux Environment I Insights into how the system behaves in various circumstances Prerequisites I Linux account I Familiarity with the basic Linux command line environment I Some experience in programming with the gcc and g++ compilers B.W.Gore Programming in the Linux Environment Prerequisites I Linux account I Familiarity with the basic Linux command line environment I Some experience in programming with the gcc and g++ compilers I Insights into how the system behaves in various circumstances B.W.Gore Programming in the Linux Environment I Ken Thompson in 1969 made it work on DEC PDP-7 I Also involved, through ideas & contributions, were Rudd Canaday, Doug McIlroy, Joe Ossanna & Dennis Ritchie I Ritchie ported UNIX to the more advanced PDP-11 in 1970 I He then developed C language & its compiler to work with UNIX I In 1973, Thompson & Ritchie rewrote entire UNIX system code in C I It broke the tradition of writing OS in assembly language I With rewrite in C, UNIX became portable to any hardware UNIX I The UNIX operating system was developed in the late 1960s at AT&T Bell Laboratories B.W.Gore Programming in the Linux Environment I Also involved, through ideas & contributions, were Rudd Canaday, Doug McIlroy, Joe Ossanna & Dennis Ritchie I Ritchie ported UNIX to the more advanced PDP-11 in 1970 I He then developed C language & its compiler to work with UNIX I In 1973, Thompson & Ritchie rewrote entire UNIX system code in C I It broke the tradition of writing OS in assembly language I With rewrite in C, UNIX became portable to any hardware UNIX I The UNIX operating system was developed in the late 1960s at AT&T Bell Laboratories I Ken Thompson in 1969 made it work on DEC PDP-7 B.W.Gore Programming in the Linux Environment I Ritchie ported UNIX to the more advanced PDP-11 in 1970 I He then developed C language & its compiler to work with UNIX I In 1973, Thompson & Ritchie rewrote entire UNIX system code in C I It broke the tradition of writing OS in assembly language I With rewrite in C, UNIX became portable to any hardware UNIX I The UNIX operating system was developed in the late 1960s at AT&T Bell Laboratories I Ken Thompson in 1969 made it work on DEC PDP-7 I Also involved, through ideas & contributions, were Rudd Canaday, Doug McIlroy, Joe Ossanna & Dennis Ritchie B.W.Gore Programming in the Linux Environment I He then developed C language & its compiler to work with UNIX I In 1973, Thompson & Ritchie rewrote entire UNIX system code in C I It broke the tradition of writing OS in assembly language I With rewrite in C, UNIX became portable to any hardware UNIX I The UNIX operating system was developed in the late 1960s at AT&T Bell Laboratories I Ken Thompson in 1969 made it work on DEC PDP-7 I Also involved, through ideas & contributions, were Rudd Canaday, Doug McIlroy, Joe Ossanna & Dennis Ritchie I Ritchie ported UNIX to the more advanced PDP-11 in 1970 B.W.Gore Programming in the Linux Environment I In 1973, Thompson & Ritchie rewrote entire UNIX system code in C I It broke the tradition of writing OS in assembly language I With rewrite in C, UNIX became portable to any hardware UNIX I The UNIX operating system was developed in the late 1960s at AT&T Bell Laboratories I Ken Thompson in 1969 made it work on DEC PDP-7 I Also involved, through ideas & contributions, were Rudd Canaday, Doug McIlroy, Joe Ossanna & Dennis Ritchie I Ritchie ported UNIX to the more advanced PDP-11 in 1970 I He then developed C language & its compiler to work with UNIX B.W.Gore Programming in the Linux Environment I It broke the tradition of writing OS in assembly language I With rewrite in C, UNIX became portable to any hardware UNIX I The UNIX operating system was developed in the late 1960s at AT&T Bell Laboratories I Ken Thompson in 1969 made it work on DEC PDP-7 I Also involved, through ideas & contributions, were Rudd Canaday, Doug McIlroy, Joe Ossanna & Dennis Ritchie I Ritchie ported UNIX to the more advanced PDP-11 in 1970 I He then developed C language & its compiler to work with UNIX I In 1973, Thompson & Ritchie rewrote entire UNIX system code in C B.W.Gore Programming in the Linux Environment I With rewrite in C, UNIX became portable to any hardware UNIX I The UNIX operating system was developed in the late 1960s at AT&T Bell Laboratories I Ken Thompson in 1969 made it work on DEC PDP-7 I Also involved, through ideas & contributions, were Rudd Canaday, Doug McIlroy, Joe Ossanna & Dennis Ritchie I Ritchie ported UNIX to the more advanced PDP-11 in 1970 I He then developed C language & its compiler to work with UNIX I In 1973, Thompson & Ritchie rewrote entire UNIX system code in C I It broke the tradition of writing OS in assembly language B.W.Gore Programming in the Linux Environment UNIX I The UNIX operating system was developed in the late 1960s at AT&T Bell Laboratories I Ken Thompson in 1969 made it work on DEC PDP-7 I Also involved, through ideas & contributions, were Rudd Canaday, Doug McIlroy, Joe Ossanna & Dennis Ritchie I Ritchie ported UNIX to the more advanced PDP-11 in 1970 I He then developed C language & its compiler to work with UNIX I In 1973, Thompson & Ritchie rewrote entire UNIX system code in C I It broke the tradition of writing OS in assembly language I With rewrite in C, UNIX became portable to any hardware B.W.Gore Programming in the Linux Environment 2.
Load more

Recommended publications
  • Extending Gnu Troff to Produce Html Through The
    G. MULLEY and W.LEMBERG: EXTENDING GNU TROFF TOPRODUCE HTML EXTENDING GNU TROFF TOPRODUCE HTML THROUGH THE TECHNIQUE OF NEXT EVENT SIMULATION GAIUS MULLEY,WERNER LEMBERG School of Computing,University of Glamorgan, CF37 1DL, UK E-Mail: [email protected] Kl. Beurhausstr.1,44137 Dortmund, Germany E-Mail: [email protected] Abstract: This paper reports on a technique used to generate accurate HTML output from GNU Troff. GNU Troff is a typesetting package which reads plain text mixed with formatting commands and produces formatted output. It supports a number of devices and nowsupports the production of HTML.The paper discusses the design of the HTML device driver grohtml and modifications made to GNU Troff. The front end program troff wasmodi- fied to maintain a reduced state machine which is examined each time a glyph is passed to the back end device driver(post-grohtml). Anychange in system state between the production of twoglyphs results in a sequence of events being passed to the device driver. There is a direct correspondence between this technique and creating ascript for a next event simulation queue. Furthermore the device driverreconstructs the system state and for- mats the HTML according to state changes caused when processing the event queue. This technique works well, as it minimises the state information passed from front end to back end device driverwhilst still preserving the high levellayout of the text. Using this technique GNU Troffeffectively translates input source into another mark-up language and thus this technique could be extended to translate GNU Troffdocuments into anyofthe OpenOffice supported formats.
    [Show full text]
  • Reflections on Software Research
    TURING AWARD LECTURE Reflections on Software Research Can the circumstances that existed in Bell Labs that nurtured the UNIX project be produced again? DENNIS M. RITCHIE The UNIX 1 operating system has suddenly become System V is a supported product on several different news, but it is not new. It began in 1969 when Ken hardware lines, most recently including the 3B systems Thompson discovered a little-used PDP-7 computer and designed and built by AT&T. set out to fashion a computing environment that he UNIX is in wide use, and is now even spoken of as a liked. His work soon attracted me; I joined in the enter- possible industry standard. How did it come to suc- prise, though most of the ideas, and most of the work ceed? for that matter, were his. Before long, others from our There are, of course, its technical merits. Because the group in the research area of AT&T Bell Laboratories system and its history have been discussed at some were using the system; Joe Ossanna, Doug McIlroy, and length in the literature [6, 7, 11], I will not talk about Bob Morris were especially enthusiastic critics and con- these qualities except for one; despite its frequent sur- tributors. In 1971, we acquired a PDP-11, and by the face inconsistency, so colorfully annotated by Don Nor- end of that year we were supporting our first real users: man in his Datamation article [4] and despite its rich- three typists entering patent applications. In 1973, the ness, UNIX is a simple, coherent system that pushes a system was rewritten in the C language, and in that few good ideas and models to the limit.
    [Show full text]
  • Introduction to Linux
    Introduction to Linux Yuwu Chen HPC User Services LSU HPC LONI [email protected] Louisiana State University Baton Rouge June 17, 2020 Why you should learn Linux? . Linux is everywhere, not just on HPC . Linux is used on most web servers. Google or Facebook . Android phone . Linux is free and you can personally use it . You will learn how hardware and operating systems work . A better chance of getting a job Introduction to Linux 2 Why Linux for HPC - 2014 OS family system share OS family performance share http://www.top500.org/statistics/list/ November 2014 Introduction to Linux 3 Why Linux for HPC - 2019 OS family system share OS family performance share Linux is the most popular OS used in supercomputers http://www.top500.org/statistics/list/ November 2019 Introduction to Linux 4 Roadmap • What is Linux • Linux file system • Basic commands • File permissions • Variables • Use HPC clusters • Processes and jobs • File editing Introduction to Linux 5 History of Linux (1) . Unix was initially designed and implemented at AT&T Bell Labs 1969 by Ken Thompson, Dennis Ritchie, Douglas McIlroy, and Joe Ossanna . First released in 1971 and was written in assembly language . Re-written in C by Dennis Ritchie in 1973 for better portability (with exceptions to the kernel and I/O) Introduction to Linux 6 History of Linux (2) . Linus Torvalds, a student at University of Helsinki began working on his own operating system, which became the "Linux Kernel", 1991 . Linus released his kernel for free download and helped further development Introduction to Linux 7 History of Linux (3) .
    [Show full text]
  • Concept Learning
    Unit 3 Milestones and Giants in IT Industry Concept Learning The Birth of Unix Kenneth "Ken" Thompson (born February 4, 1943), commonly referred to as Ken in hacker circles, is an American pioneer of computer science. Having worked at Bell Labs for most of his career, Thompson designed and implemented the original Unix operating system. He also invented the B programming language, the direct predecessor to the C programming language, and was one of the creators and early developers of the Plan 9 operating systems. Since 2006, Thompson has worked at Google, where he co-invented the Go programming language. In 1983, Thompson and Ritchie jointly received the Turing Award "for their development of generic operating systems theory and specifically for the implementation of the UNIX operating system." C Ken Ken Thompson and Dennis Ritchie (standing) at Bell Labs, 1972 In the end of 1960s, the young engineer at AT&T Bell Labs Kenneth (Ken) Thompson worked on the project of Multics operating system. Multics (Multiplexing Information and Computer Services) was an experimental operating system for GE-645 mainframe, developed in 1960s by Massachusetts Institute of Technology, Bell Labs, and General Electric. It introduced many innovations, but had many problems. 1969 was that magic year in which mankind first went to the moon, ARPANET (the precursor to the Internet) was launched, UNIX was born, and a number of other interesting events occurred. It was also the year that Thompson wrote the game Space Travel. In 1969, frustrated by the slow progress and difficulties, Bell Labs withdrew from the MULTICS project and Thompson decided to write his own operating system, in large part because he wanted a decent system on which to run his game, Space Travel, on the PDP-7.
    [Show full text]
  • Nroff/Troff User's Manual
    AT&T Bell Laboratories Murray Hill, New Jersey 07974 Computing Science Technical Report No. 54 Troff User's Manual² Joseph F. Ossanna Brian W. Kernighan Revised November, 1992 Troff User's Manual² Joseph F. Ossanna Brian W. Kernighan AT&T Bell Laboratories Murray Hill, New Jersey 07974 Revised November, 1992 Troff User's Manual² Joseph F. Ossanna Brian W. Kernighan AT&T Bell Laboratories Murray Hill, New Jersey 07974 Introduction Troff and nroff are text processors that format text for typesetter- and typewriter-like terminals, respectively. They accept lines of text interspersed with lines of format control information and format the text into a printable, paginated document having a user-designed style. Troff and nroff offer unusual free- dom in document styling: arbitrary style headers and footers; arbitrary style footnotes; multiple automatic sequence numbering for paragraphs, sections, etc; multiple column output; dynamic font and point-size control; arbitrary horizontal and vertical local motions at any point; and a family of automatic overstriking, bracket construction, and line-drawing functions. Troff produces its output in a device-independent form, although parameterized for a specific device; troff output must be processed by a driver for that device to produce printed output. Troff and nroff are highly compatible with each other and it is almost always possible to prepare input acceptable to both. Conditional input is provided that enables the user to embed input expressly des- tined for either program. Nroff can prepare output directly for a variety of terminal types and is capable of utilizing the full resolution of each terminal. A warning, however: nroff necessarily cannot support all fea- tures of troff.
    [Show full text]
  • SEGURIDAD EN UNIX Y REDES Versión 2.1'
    SEGURIDAD EN UNIX Y REDES Versión 2.1' Antonio Villalón Huerta Julio, 2000 – Julio, 2002 – Enero, 2020 © Antonio Villalón Huerta © Derechos de edición: Nau Llibres - Edicions Culturals Valencianes, S.A. Tel.: 96 360 33 36, Fax: 96 332 55 82. C/ Periodista Badía, 10. 46010 Valencia E-mail: [email protected] web: www.naullibres.com Diseño de portada e interiores: Carol López, Pablo Navarro y Artes Digitales Nau Llibres ISBN: 978-84-18047-04-6 Dep.Legal: V-3368-2019 Imprime: Safekat Cualquier forma de reproducción, distribución, comunicación pública o transformación de esta obra solo puede ser realizada con la autorización de sus titulares, salvo excepción prevista por la ley. Diríjase a CEDRO (Centro Español de Derechos Reprográficos) si necesita fotocopiar o escanear algún fragmento de esta obra (www.conlicencia.com; 91 702 19 70 / 93 27204 45). i Copyright c 2000,2002 Antonio Villal´onHuerta. Permission is granted to copy, distribute and/or modify this do- cument under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with the Invariant Sections being `Notas del Autor' and `Conclusiones', with no Front-Cover Texts, and with no Back- Cover Texts. A copy of the license is included in the section entitled `GNU Free Documentation License'. ii ´Indice general Notas del autor XVII 1. Introducci´ony conceptos previos 1 1.1. Introducci´on. 1 1.2. Justificaci´ony objetivos . 2 1.3. >Qu´ees seguridad?........................... 3 1.4. >Qu´equeremos proteger? . 5 1.5. >De qu´enos queremos proteger? . 7 1.5.1.
    [Show full text]
  • A Research UNIX Reader: Annotated Excerpts from the Programmer's
    AResearch UNIX Reader: Annotated Excerpts from the Programmer’sManual, 1971-1986 M. Douglas McIlroy ABSTRACT Selected pages from the nine research editions of the UNIX®Pro grammer’sManual illustrate the development of the system. Accompanying commentary recounts some of the needs, events, and individual contributions that shaped this evolution. 1. Introduction Since it beganatthe Computing Science Research Center of AT&T Bell Laboratories in 1969, the UNIX system has exploded in coverage, in geographic distribution and, alas, in bulk. It has brought great honor to the primary contributors, Ken Thompson and Dennis Ritchie, and has reflected respect upon many others who have built on their foundation. The story of howthe system came to be and howitgrewand prospered has been told manytimes, often embroidered almost into myth. Still, aficionados seem neverto tire of hearing about howthings were in that special circle where the system first flourished. This collection of excerpts from the nine editions of the research UNIX Programmer’sManual has been chosen to illustrate trends and some of the lively give-and-take—or at least the tangible results thereof—that shaped the system. It is a domestic study,aimed only at capturing the way things were in the system’soriginal home. To look further afield would require a tome, not a report, and possibly a more dis- passionate scholar,not an intimate participant. The rawreadings are supplemented by my own recollec- tions as corrected by the memories of colleagues. The collection emphasizes development up to the Seventh Edition (v7*) in 1979, providing only occasional peeks ahead to v8 and v9.
    [Show full text]
  • Validators Report
    National Information Assurance Partnership ® TM Common Criteria Evaluation and Validation Scheme Validation Report Wind River Wind River Linux Secure 1.0 Report Number: CCEVS-VR-VID10430-2011 Dated: 2011-04-05 Version: 1.0 National Institute of Standards and Technology National Security Agency Information Technology Laboratory Information Assurance Directorate 100 Bureau Drive 9800 Savage Road STE 6940 Gaithersburg, MD 20899 Fort George G. Meade, MD 20755-6940 ACKNOWLEDGEMENTS Validation Team Daniel Faigin The Aerospace Corporation El Segundo, California Jerome Myers The Aerospace Corporation Columbia, Maryland Evaluation Team Jeremy Powell atsec Information Security Corporation Austin, Texas Andreas Siegert atsec Information Security Corporation Munich, Germany Table of Contents 1. EXECUTIVE SUMMARY .......................................................................................................................................... 5 2. IDENTIFICATION ...................................................................................................................................................... 5 3. CLARIFICATION OF SCOPE ................................................................................................................................... 7 4. SECURITY POLICY ................................................................................................................................................... 9 5. ASSUMPTIONS .......................................................................................................................................................
    [Show full text]
  • Computer Science: Reflections On
    http://www.nap.edu/catalog/11106.html We ship printed books within 1 business day; personal PDFs are available immediately. Computer Science: Reflections on the Field, Reflections from the Field Committee on the Fundamentals of Computer Science: Challenges and Opportunities, National Research Council ISBN: 0-309-54529-3, 208 pages, 6 x 9, (2004) This PDF is available from the National Academies Press at: http://www.nap.edu/catalog/11106.html Visit the National Academies Press online, the authoritative source for all books from the National Academy of Sciences, the National Academy of Engineering, the Institute of Medicine, and the National Research Council: • Download hundreds of free books in PDF • Read thousands of books online for free • Explore our innovative research tools – try the “Research Dashboard” now! • Sign up to be notified when new books are published • Purchase printed books and selected PDF files Thank you for downloading this PDF. If you have comments, questions or just want more information about the books published by the National Academies Press, you may contact our customer service department toll- free at 888-624-8373, visit us online, or send an email to [email protected]. This book plus thousands more are available at http://www.nap.edu. Copyright © National Academy of Sciences. All rights reserved. Unless otherwise indicated, all materials in this PDF File are copyrighted by the National Academy of Sciences. Distribution, posting, or copying is strictly prohibited without written permission of the National Academies Press. Request reprint permission for this book. Computer Science: Reflections on the Field, Reflections from the Field http://www.nap.edu/catalog/11106.html Computer Science Reflections on the Field, Reflections from the Field Committee on the Fundamentals of Computer Science: Challenges and Opportunities Computer Science and Telecommunications Board THE NATIONAL ACADEMIES PRESS Washington, D.C.
    [Show full text]
  • Praktikum Iz Softverskih Alata U Elektronici 2017/2018
    PRAKTIKUM IZ SOFTVERSKIH ALATA U ELEKTRONICI 2017/2018 Predrag Pejović 31. decembar 2017. Linkovi na primere: OS: http://tnt.etf.bg.ac.rs/~oe4sae/primeri-3-2017.zip LATEX 1: http://tnt.etf.bg.ac.rs/~oe4sae/primeri-4-2017.zip LATEX 2: http://tnt.etf.bg.ac.rs/~oe4sae/primeri-5-2017.zip LATEX 3: http://tnt.etf.bg.ac.rs/~oe4sae/primeri-6-2017.zip GNU Octave: http://tnt.etf.bg.ac.rs/~oe4sae/primeri-8-2017.zip gnuplot: http://tnt.etf.bg.ac.rs/~oe4sae/primeri-10-2017.zip Maxima: http://tnt.etf.bg.ac.rs/~oe4sae/primeri-11-2017.zip Python 1: http://tnt.etf.bg.ac.rs/~oe4sae/primeri-12-2017.py Python 2: http://tnt.etf.bg.ac.rs/~oe4sae/primeri-13-2017.zip PyLab: http://tnt.etf.bg.ac.rs/~oe4sae/primeri-14-2017.zip SymPy: http://tnt.etf.bg.ac.rs/~oe4sae/prim-sympy.py Lica (i ostali podaci o predmetu): I Predrag Pejović, [email protected], 102 levo, http://tnt.etf.rs/~peja PRAKTIKUM IZ SOFTVERSKIH ALATA I Strahinja Janković U ELEKTRONICI I sajt: http://tnt.etf.rs/~oe4sae 2017 I cilj: savladavanje niza programa koji se koriste za svakodnevne poslove u elektronici (i ne samo elektronici . ) I svi programi koji će biti obrađivani su slobodan softver (free software), legalno možete da ih koristite (i ne samo to) gde hoćete, kako hoćete, za šta hoćete, koliko hoćete, na kom računaru hoćete . I literatura . sve sa www, legalno, besplatno! I zašto svake godine (pomalo) updated slajdovi? Prezentacije predmeta A šta se tačno radi u predmetu, koji programi? 1.
    [Show full text]
  • Berkeley Odyssey
    BERKELEY ODYSSEY Ten years of BSD history by Marshall Kirk McKusick Ken Thompson and Dennis Ritchie presented the first UNIX paper at the Symposium on Operating Systems Principles at Pur­ due University in November, 1973. Professor Bob Fabry was in attendance and immediately became interested in obtaining a f copy of the system to experiment with at Berkeley. - At the time, Berkeley had only large mainframe computer systems doing batch processing, so the first order of business was to get a PDP-11/45 suitable for running the then current Version 4 of UNIX. The Computer Science Department, together with the Mathematics Department and the Statistics Department were able to jointly purchase a PDP-11/45. In January, 1974, a Version 4 tape was delivered and UNIX was installed by graduate student ¥<~ Keith Standiford. Although Ken Thompson was not involved in the installation — as he had been for most systems up to that time — his exper­ tise was soon needed to determine the cause of several strange system crashes. Because Berkeley had only a 300 baud acoustic- coupled modem without auto answer capability, Thompson would call Standiford in the machine room and have him insert the phone into the modem; in this way Thompson was able to remote­ ly debug crash dumps from New Jersey. 9mm £££ SK wmmMm&?<%?+•*>' '-•fy&Z j?m gis£^t - WMm ^ssg®mmm m^f, ?*S£ SP mm? r^^^m^^S?^^ :%%&m. ':•! '-^SS&^i * Jfjfe BERKELEY ODYSSEY Many of the crashes were project became the first group in immediate interest in the new caused by the disk controller's the Computer Science department system.
    [Show full text]
  • Teste-Livro-2Vfinal.Pdf
    SÉRIE PENSAMENTO MATEMÁTICO @ CIÊNCIA COMPUTAÇÃO Volume II: Da Computabilidade Formal às Máquinas Programáveis João Bosco M. Sobral EDIÇÃO DO AUTOR Jo~aoBosco M. Sobral Da Computabilidade Formal `as M´aquinasProgram´aveis S´erie Pensamento Matem´atico@ Ci^enciada Computa¸c~ao Edi¸c~aodo Autor Laborat´orioe Grupo de Pesquisa UFSC-CNPq Revis~aoT´ecnica Renato Bobsin Machado Dr. em Ci^encias- UNICAMP Programa de P´os-Gradua¸c~aoem Engenharia El´etricae Computa¸c~ao- UNIOESTE Universidade Federal de Santa Catarina Centro Tecnol´ogico Departamento de Inform´aticae Estat´ıstica Laborat´orioDMC & NS Projeto de Pesquisa PRPE 2013.1533 Jo~aoBosco M. Sobral Da Computabilidade Formal `as M´aquinasProgram´aveis S´erie Pensamento Matem´atico@ Ci^enciada Computa¸c~ao a 1¯ Edi¸c~ao Florian´opolis Edi¸c~ao do Autor 2015 c 2015 Jo~aoBosco M. Sobral Universidade Federal de Santa Catarina Centro Tecnol´ogico Departamento de Inform´aticae Estat´ıstica Laborat´orioDMC & NS Projeto de Pesquisa PRPE 2013.1533 Qualquer parte desta publica¸c~aopode ser reproduzida, desde que citada a fonte, e as fontes originais referenciadas neste livro. Al´emda bibliografia citada, o autor fez uso extensivo de diversos e excelentes sites da Internet, e imagens dos personagens e fatos marcantes na hist´oriada Matem´atica,da L´ogicae da Ci^enciada Computa¸c~ao,aos quais, n~aosendo de sua propriedade, est~ao devidamente referenciados. Conforme declarado `aAg^enciaBrasileira do ISBN, este livro n~ao´epara ser comercializado. Nota - Muito trabalho foi empregado nesta edi¸c~ao.No entanto, podem ocorrer erros de digita¸c~ao,impress~aoou d´uvida sobre os conceitos.
    [Show full text]