DOCSLIB.ORG

Unix 101: Introduction to UNIX (I.E. Unix for Windows Users)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Unix 101: Introduction to UNIX (I.E. Unix for Windows Users) Unix 101: Introduction to UNIX (i.e. Unix for Windows Users) Mark Kegel September 7, 2005 1 Introduction to UNIX (i.e. · solid and basic understanding of unix Unix for Windows Users) ¥ not enough time in the regular school year to teach you this and teach you everything • The cold hard truth else you need to know ¥ and also because the CS department · this course is NOT sponsored by the CS doesn’t have the resources, or want to of- dept. fer this course on its own - maybe they will · you will not receive any credit at all in the future ¥ we needed something to do with our sum- • introduce ourselves to the students mer vacation · Should introduce myself and Marshall ¥ the goodness of our hearts, etc. ¥ are seniors in CS and CS/Math • To make this perfectly clear... • And what do we think we’re doing... · will not teach you to program · will not teach you emacs tricks; will provide · here to teach you fundamentals of Unix a reference sheet · to teach you the student to teach yourself ¥ not about learning to use a single applica- about unix tion · to give you the necessary basics to go out ¥ will not solve world hunger, peace, or to be and teach yourself whatever you might need a better person to know to get work done on unix · catch a fish for a man vs teach a man to 2 Computers on Campus fish · trying to follow Mudd philosophy - teach • Available computing resources you to teach yourself · graphics lab • who this course is targeted at · terminal room - printer · AC and LAC labs - printer and scanner · those students who have never worked with unix before and would to get some experi- · Engineering lab - to be avoided ence doing • Servers · those students who have had some experi- · odin, thuban, banshee ence but would like to learn more · knuth, knuth, wilkes, muddcs, arc, cortana · someone who is lost, confused, and looking ¥ knuth is the one you care about for spiritual enlightenment ¥ main server everyone will be working on - ¥ mashall has a great religion for you to join give specs. - we sin so jesus didn’t die in vain • People to know ¥ ask around, see who has what experience · Tim Buchheim and Roger Wiechman • Some reasons to learn about Unix ¥ Bring them milk, cookies and be nice to · linux and OS X them, they make things work 1 3 Philosophy and History of ¥ about as different as mango, peach, kiwi, straw- UNIX berry ice-cream and peach, strawberry, kiwi, mango ice-cream with bits of vanilla • Origin of Unix ¥ especially that way in linux, its all just annoying ¥ computers were mainframes that people ¥ it doesn’t matter what you run, what we are worked at, much like knuth going to teach you here will apply across most ¥ teletypes - basically a typewriter plugged unixes though not all into a computer • What is Unix? · Ken Thomson implemented the first UNIX environment ¥ unix in some sense is not an operating sys- tem but rather a programming language ¥ had been working at Bell Labs on a project (C)/philosophy/interface (POSIX) called Multics (Multiplexed ...) ¥ the development of C (and the internet) are ¥ Unix was kind of a castrated Multics - much all connected smaller because invented on an underpow- ered system - PDP-7 ¥ unix is (kind of) C, the Standard C Li- brary, and POSIX (Portable Operating Sys- ¥ became popular mainly because it was dis- tem Standard) which is the API that pro- tributed to Universities grammers use to interact with the system ¥ will want to display Unix timeline kernel • Unix Today ¥ the design and implementation of unix also follows a certain philosophy about how ¥ programmers environment - because of this an OS should be designed, how programs is extremely powerful should be written, etc. · still very much a tinkerer’s environment ¥ everything else is just historical baggage · unix encourages and support ”hacking” the ¥ makes unix extremely flexible - can start system from scratch with a new implementation but still same ”design” · Fundamentally multi-user and multitasking ¥ designed in the days of mainframe environ- ¥ what would be some good philosophical ideas to ments when many people would all work on follow when building an OS? one computer system ¥ what are some good rules of thumb? what trade- ¥ we still use the same model in many ways offs do you want to make? with knuth • Unix philosophy ¥ clean, simple interface · programs should be designed to operate to- ¥ Chalkboard exercise gether ¥ unix is also multi-layered in design, mean- · output of one could be used as the in- ing that functionality separated into levels put to another going from the hardware to the user, stuff ¥ text streams -> universal input is also abstracted aways at each layer · Programs are viewed as simple tools that ¥ user | (shell, other programs) | OS(kernel) combined will do complex tasks | hardware · each program should do one thing ex- ¥ at top user at bottom hardware, what’s in- tremely well between? ¥ LEGO blocks - simple tools but can create ¥ scales very well - from supercomputers to very complex systems microwaves (embedded systems) ¥ another analogy - hammer, wrench, saw ¥ two different flavors of unix - BSD (FreeBSD, ¥ Avoid the ginormous programs that do ev- OSX) and System V (Solaris, Linux) erything 2 ¥ Windows has this problem (think of Of- make commands and programs interact fice) with each other, not just from treating ¥ Windows programs also don’t integrate each as a fixed black box. very nicely - no pipeline · Richness of utilities (over 400 standard · want to keep everything as simple as possi- ones) often overwhelms novices. Doc- ble umentation is short on examples and tutorials to help you figure out how to · KISS - keep it simple stupid use the many tools provided to accom- ¥ this applies everywhere - both in OS plish various kinds of tasks.” interaction (system calls and library ¥ ”Unix *is* user-friendly. It’s just picky calls) and in program creation about its friends.” · separate mechanism from policy ¥ very true - have to be able to understand ¥ Unix (and programs that run on Unix) the system at some intuitive level to be able provide a mechanism to do something to work with it but do not lock you down to one policy ¥ also if you don’t like something you can fix ¥ policy - how a program should look and it, maybe not easily, but you can fix it behave ¥ users have to decide on policy ¥ What makes a system secure? What needs to be ¥ games and GUIs are generally a good protected? examples - mods and skins ¥ What is a good way of protecting things, like ¥ walk up to some one and try to scare them property? Ownership · principle of least surprise • Unix security · applications will generally produce no output if successful · concept of ownership - everything on the · applications that fail will make it evi- system is owned by someone dent (sirens if necessary) ¥ ownership implies responsibility - so who- · programs should do the least surprising ever owns these files is in the end responsi- thing ble for them ¥ do not try to feed emacs a stray cat · protect users from one another and from · there is no ”one true way” - unix is not doing dangerous things perfect! · protect privacy -> data ¥ unix has things wrong with it, and · protect work -> programs things that unless you understand will · protect programs and files from users - or cause you a great deal of pain rather allow only certain users to do certain ¥ The Unix Hater’s Handbook - written things to expose the flaws in unix ¥ security: not perfect, can break, and will · from a stanford site: cause you to scream a few months down the http://pangea.stanford.edu/computerinfo/ line unix/overview/advantages.html · ”The traditional command line shell in- terface is user hostile 4 Types of users · designed for the programmer, not the casual user. ¥ what powers is each user going to have? · Commands often have cryptic names ¥ do you need to have a class of users that manage and give very little response to tell the the system? user what they are doing. Much use of special keyboard characters - little ty- ¥ what kinds of users are there going to be? pos have unexpected results. • administrative users · To use Unix well, you need to under- stand some of the main design features. · root - is the best known account of this type Its power comes from knowing how to - aka The SuperUser 3 · complete control over everything on the sys- ¥ for security reasons do not want to have a tem web server running as root · can do anything that they want (mostly) - ¥ what if someone owned your web daemon - has to respect file perms. would own your system...is bad · can become any user on the system ¥ unless you’re setting up your own system ¥ loaded gun with the safety off, easy to shoot don’t have to worry about this yourself in the foot ¥ and even then still don’t really have to · is a standard account on every worry about this since most of these users UNIX/Linux/BSD machine will have been created by default - rarely have to create a new system user · used for system administra- tion/maintenance ¥ now that we have users, how do we manage · what this is will cover later them? ¥ any other user however can be granted ad- ¥ should all users be lumped in to one category? min privileges, so root isn’t strictly neces- sary to run a system • groups ¥ why would you want? what if you tried to ¥ are the unix solution to separating respon- delete all the files on the system? shouldn’t sibilty amoung users be able to do · every user on the system belongs to one or more groups ¥ should there be different types of normal users? is there a better way to organize responsibility? · these are
Load more

Recommended publications
  • Running Windows Programs on Ubuntu with Wine Wine Importer Shanna Korby, Fotolia
    KNoW-HoW Wine Running Windows programs on Ubuntu with Wine Wine importer Shanna Korby, Fotolia Korby, Shanna Users who move from Windows to Ubuntu often miss some of their favorite programs and games. Wouldn’t it be practical to run Windows applications on the free Ubuntu operating system? Time for a little taste of Wine. BY TIM SCHÜRMANN any Ubuntu migrants miss to develop something similar for Linux. Box or VMware, Wine does not emulate games and graphics programs A short while later, the first version of a whole PC and thus cannot be consid- Msuch as CorelDRAW or prod- Wine was released. Today, more than ered a real emulator. This also explains ucts such as Adobe Photoshop. The only 300 volunteer programmers from all over the name Wine, which means Wine Is solution is to install Windows parallel to the world continue to contribute to the Not an Emulator. Ubuntu – or try Wine, which tricks ap- Wine project. Because of the way Wine works, it of- plications into believing they are run- fers a number of advantages. Chiefly, ning on a Windows system. What’s in a Name? you do not need an expensive Windows The history of Wine goes back to the To run Windows programs on Ubuntu, license. Programs will run almost as fast year 1993. At the time, Sun developed a Wine uses a fairly complex trick: It sits as on the Redmond operating system, small tool to run Windows applications between the Windows application and and windows behave as if they belong on its own Solaris operating system, Ubuntu like a simultaneous interpreter.
    [Show full text]
  • Virtualgl / Turbovnc Survey Results Version 1, 3/17/2008 -- the Virtualgl Project
    VirtualGL / TurboVNC Survey Results Version 1, 3/17/2008 -- The VirtualGL Project This report and all associated illustrations are licensed under the Creative Commons Attribution 3.0 License. Any works which contain material derived from this document must cite The VirtualGL Project as the source of the material and list the current URL for the VirtualGL web site. Between December, 2007 and March, 2008, a survey of the VirtualGL community was conducted to ascertain which features and platforms were of interest to current and future users of VirtualGL and TurboVNC. The larger purpose of this survey was to steer the future development of VirtualGL and TurboVNC based on user input. 1 Statistics 49 users responded to the survey, with 32 complete responses. When listing percentage breakdowns for each response to a question, this report computes the percentages relative to the total number of complete responses for that question. 2 Responses 2.1 Server Platform “Please select the server platform(s) that you currently use or plan to use with VirtualGL/TurboVNC” Platform Number of Respondees (%) Linux/x86 25 / 46 (54%) ● Enterprise Linux 3 (x86) 2 / 46 (4.3%) ● Enterprise Linux 4 (x86) 5 / 46 (11%) ● Enterprise Linux 5 (x86) 6 / 46 (13%) ● Fedora Core 4 (x86) 1 / 46 (2.2%) ● Fedora Core 7 (x86) 1 / 46 (2.2%) ● Fedora Core 8 (x86) 4 / 46 (8.7%) ● SuSE Linux Enterprise 9 (x86) 1 / 46 (2.2%) 1 Platform Number of Respondees (%) ● SuSE Linux Enterprise 10 (x86) 2 / 46 (4.3%) ● Ubuntu (x86) 7 / 46 (15%) ● Debian (x86) 5 / 46 (11%) ● Gentoo (x86) 1 /
    [Show full text]
  • MX-18.3 Users Manual
    MX-18.3 Users Manual v. 20190614 manual AT mxlinux DOT org Ctrl-F = Search this Manual Ctrl+Home = Return to top Table of Contents 1 Introduction................................................................................2 2 Installation..................................................................................8 3 Configuration...........................................................................37 4 Basic use..................................................................................93 5 Software Management...........................................................126 6 Advanced use.........................................................................141 7 Under the hood.......................................................................164 8 Glossary.................................................................................178 1 Introduction 1.1 About MX Linux MX Linux is a cooperative venture between the antiX and former MEPIS communities, using the best tools and talents from each distro and including work and ideas originally created by Warren Woodford. It is a midweight OS designed to combine an elegant and efficient desktop with simple configuration, high stability, solid performance and medium-sized footprint. Relying on the excellent upstream work by Linux and the open-source community, we deploy Xfce 4.12 as Desktop Environment on top of a Debian Stable base, drawing from the core antiX system. Ongoing backports and outside additions to our Repos serve to keep components current with developments.
    [Show full text]
  • MX-19.2 Users Manual
    MX-19.2 Users Manual v. 20200801 manual AT mxlinux DOT org Ctrl-F = Search this Manual Ctrl+Home = Return to top Table of Contents 1 Introduction...................................................................................................................................4 1.1 About MX Linux................................................................................................................4 1.2 About this Manual..............................................................................................................4 1.3 System requirements..........................................................................................................5 1.4 Support and EOL................................................................................................................6 1.5 Bugs, issues and requests...................................................................................................6 1.6 Migration............................................................................................................................7 1.7 Our positions......................................................................................................................8 1.8 Notes for Translators.............................................................................................................8 2 Installation...................................................................................................................................10 2.1 Introduction......................................................................................................................10
    [Show full text]
  • Download the Index
    41_067232945x_index.qxd 10/5/07 1:09 PM Page 667 Index NUMBERS 3D video, 100-101 10BaseT Ethernet NIC (Network Interface Cards), 512 64-bit processors, 14 100BaseT Ethernet NIC (Network Interface Cards), 512 A A (Address) resource record, 555 AbiWord, 171-172 ac command, 414 ac patches, 498 access control, Apache web server file systems, 536 access times, disabling, 648 Accessibility module (GNOME), 116 ACPI (Advanced Configuration and Power Interface), 61-62 active content modules, dynamic website creation, 544 Add a New Local User screen, 44 add command (CVS), 583 address books, KAddressBook, 278 Administrator Mode button (KDE Control Center), 113 Adobe Reader, 133 AFPL Ghostscript, 123 41_067232945x_index.qxd 10/5/07 1:09 PM Page 668 668 aggregators aggregators, 309 antispam tools, 325 aKregator (Kontact), 336-337 KMail, 330-331 Blam!, 337 Procmail, 326, 329-330 Bloglines, 338 action line special characters, 328 Firefox web browser, 335 recipe flags, 326 Liferea, 337 special conditions, 327 Opera web browser, 335 antivirus tools, 331-332 RSSOwl, 338 AP (Access Points), wireless networks, 260, 514 aKregator webfeeder (Kontact), 278, 336-337 Apache web server, 529 album art, downloading to multimedia dynamic websites, creating players, 192 active content modules, 544 aliases, 79 CGI programming, 542-543 bash shell, 80 SSI, 543 CNAME (Canonical Name) resource file systems record, 555 access control, 536 local aliases, email server configuration, 325 authentication, 536-538 allow directive (Apache2/httpd.conf), 536 installing Almquist shells
    [Show full text]
  • Microsoft Windows –História
    Microsoft Windows –História Bárbara Alves nº9 12ºB ÍNDICE Breve introdução Windows 95 Windows 98 Windows XP Windows Vista Windows 7 Windows 8 Windows 10 Características técnicas Implementações alternativas ao Windows e suas APIs de programação o Wine o CrossOver o ReactOS o Cedega o Darwine I Breve introdução Microsoft Windows (ou simplesmente Windows) é uma família de sistemas operacionais desenvolvidos, comercializados e vendidos pela Microsoft. É constituída por várias famílias de sistemas operacionais, cada qual atendendo a um determinado setor da indústria da computação, sendo que o sistema geralmente é associado com a arquitetura IBM PC compatível. As famílias ativas do Windows incluem Windows NT, Windows Embedded e Windows Phone; estes podem abranger subfamílias, como Windows CE ou Windows Server. Entre as famílias Windows extintas estão o Windows 9x; o Windows 10 Mobile é um produto ativo, não relacionado à família defunta Windows Mobile. A Microsoft introduziu um ambiente operacional chamado Windows em 20 de novembro de 1985, como um shell para MS-DOS, em resposta ao crescente interesse em interfaces gráficas de usuário (GUIs). O Microsoft Windows passou a dominar o mercado de computadores pessoais (PC) do mundo, com mais de 90% de participação de mercado, superando o Mac OS, que havia sido introduzido em 1984. A Apple chegou a ver o Windows como uma invasão injusta em sua inovação no desenvolvimento de produtos GUI, como o Lisa e o Macintosh (eventualmente resolvido na Justiça em favor da Microsoft em 1993). Nos PCs, o Windows ainda é o sistema operacional mais popular. No entanto, em 2014, a Microsoft admitiu a perda da maioria do mercado global de sistemas operacionais do sistema operacional móvel Android, devido ao enorme crescimento nas vendas de smartphones.
    [Show full text]
  • Ubuntu Unleashed 2015 Edition: Covering 14.10
    Matthew Helmke with Andrew Hudson and Paul Hudson Ubuntu UNLEASHED 2015 Edition 800 East 96th Street, Indianapolis, Indiana 46240 USA Ubuntu Unleashed 2015 Edition Editor-in-Chief Copyright © 2015 by Pearson Education, Inc. Mark Taub All rights reserved. No part of this book shall be reproduced, stored in a retrieval system, or transmitted by any means, electronic, mechanical, photocopying, record- Acquisitions Editor ing, or otherwise, without written permission from the publisher. No patent liability is Debra Williams assumed with respect to the use of the information contained herein. Although every Cauley precaution has been taken in the preparation of this book, the publisher and author assume no responsibility for errors or omissions. Nor is any liability assumed for Managing Editor damages resulting from the use of the information contained herein. Kristy Hart ISBN-13: 978-0-672-33837-3 Project Editor ISBN-10: 0-672-33837-8 Andy Beaster Library of Congress Control Number: 2014946899 Printed in the United States of America Indexer First Printing November 2014 Cheryl Lenser Trademarks Proofreader All terms mentioned in this book that are known to be trademarks or service marks have Sarah Kearns been appropriately capitalized. Sams Publishing cannot attest to the accuracy of this information. Use of a term in this book should not be regarded as affecting the validity Technical Editors of any trademark or service mark. Micah Brown Elizabeth Krumbach Warning and Disclaimer Every effort has been made to make this book as complete and as accurate as Editorial Assistant possible, but no warranty or fitness is implied. The information provided is on an Kim Boedigheimer “as is” basis.
    [Show full text]
  • “Análisis Y Configuración De API's Para Ejecución De Aplicaciones
    ESCUELA SUPERIOR POLITECNICA DE CHIMBORAZO FACULTAD DE INFORMATICA Y ELECTRONICA ESCUELA DE INGENIERIA EN SISTEMAS “Análisis y Configuración de API’s para ejecución de Aplicaciones Microsoft Office en un entorno de Windows bajo Linux”. TESIS DE GRADO Previa la obtención del título de INGENIERO EN SISTEMAS INFORMATICOS Presentado por: SAMUEL CARRASCO LLERENA RIOBAMBA – ECUADOR 2008 - 2 - AGRADECIMIENTO Mi profundo y sincero agradecimiento a quienes han sido parte importante de mi vida académica: A Dios, Por su presencia en mi vida y por su guía en la realización de esta tesis. A mis padres, José y Teresita, Por su constante e incondicional apoyo, por sus fervientes oraciones en mi favor. A mis Asesores de Tesis, Ing. Danilo Pastor e Ing. Jorge Menéndez, Por su valioso e invaluable aporte al desarrollo de esta tesis. - 3 - Con amor incondicional, dedico esta tesis a las tres mujeres que con su existencia alegran mi corazón: AMBITAR TERESITA PRISCILA - 4 - FIRMAS DE RESPONSABILIDAD NOMBRE NOTA FIRMA Dr. Romeo Rodríguez DECANO FACULTAD INFORMATICA Y ELECTRONICA Ing. Iván Menes DIRECTOR ESCUELA DE INGENIERIA EN SISTEMAS Ing. Danilo Pástor DIRECT OR DE TESIS Ing. Jorge Menéndez V. MIEMBRO DE TESIS Tlgo. Carlos Rodríguez DIRECTOR CENTRO DE DOCUMENTACION Nota: - 5 - RESPONSABILIDAD DEL AUTOR Yo, Samuel Carrasco Llerena, soy responsable de las ideas, doctrinas y resultados expuestos en esta tesis; el Patrimonio intelectual de esta tesis de grado pertenece a la Escuela Superior Politécnica de Chimborazo. ____________________ Samuel Carrasco Ll.
    [Show full text]
  • The Ability to Fork a Program Is One of the Free Software
    WHEN PROJECTS SPLIT Fork it! Forks have created some of the best projects in Free Software, but their origins are usually controversial and messy. Mike Saunders investigates. magine you’ve been using a certain program for gather together some fellow hackers to begin work on years. You absolutely love it, and you can’t live an open source version of your beloved app – but it Iwithout it. You know every feature, menu item and could take years to reach the same level of functionality. keybinding like the back of your hand. Then suddenly the In other words, you’re stuck. development team announces a major change: they’re Fortunately, we users of free and open source redesigning the interface, or removing features to make software don’t have this problem. At any point we can the program more take a program’s source accessible to newcomers. code and split it off – or You’re incensed. You join “The ability to fork a program “fork” it – into another the hordes of angry users is one of the Free Software project. It happens all the on forums and IRC, and time, sometimes for good complain bitterly about the community’s great strengths.” reasons, and sometimes for program’s sudden change bad ones, but without of direction. You’re deeply disappointed, and while you question the ability to fork a program is one of the Free may be able to understand the argument from the Software community’s great strengths. developers’ perspective, it doesn’t stop the fact that the Many of the most popular and famous programs we program you use every day and may even depend on for use began as forks, often in controversial or unpleasant your livelihood is about to change drastically.
    [Show full text]
  • Contents [Edit] Total Cost of Ownership
    Comparisons between the Microsoft Windows and Linux computer operating systems are a long-running discussion topic within the personal computer industry.[citation needed] Throughout the entire period of the Windows 9x systems through the introduction of Windows 7, Windows has retained an extremely large retail sales majority among operating systems for personal desktop use, while Linux has sustained its status as the most prominent Free Software and Open Source operating system. Both operating systems are present on servers, embedded systems, mobile internet devices as well as supercomputers. Linux and Microsoft Windows differ in philosophy, cost, versatility and stability, with each seeking to improve in their perceived weaker areas. Comparisons of the two operating systems tend to reflect their origins, historic user bases and distribution models. Typical perceived weaknesses regularly cited have often included poor consumer familiarity with Linux, and Microsoft Windows' susceptibility to viruses and malware.[1][2] Contents [hide] 1 Total cost of ownership o 1.1 Real world experience 2 Market share 3 User interface 4 Installation and Live environments 5 Accessibility and usability 6 Stability 7 Performance 8 Support 9 Platform for third party applications o 9.1 Gaming 10 Software development 11 Security o 11.1 Threats and vulnerabilities o 11.2 Security features and architecture 12 Localization 13 See also 14 References 15 External links [edit] Total cost of ownership See also: Studies related to Microsoft In 2004, Microsoft
    [Show full text]
  • CYBERSECURITY When Will You Be Hacked?
    SUFFOLK ACADEMY OF LAW The Educational Arm of the Suffolk County Bar Association 560 Wheeler Road, Hauppauge, NY 11788 (631) 234-5588 CYBERSECURITY When Will You Be Hacked? FACULTY Victor John Yannacone, Jr., Esq. April 26, 2017 Suffolk County Bar Center, NY Cybersecurity Part I 12 May 2017 COURSE MATERIALS 1. A cybersecurity primer 3 – 1.1. Cybersecurity practices for law firms 5 – 1.2. Cybersecurity and the future of law firms 11 – 2. Information Security 14 – 2.1. An information security policy 33 – 2.2. Data Privacy & Cloud Computing 39 – 2.3. Encryption 47 – 3. Computer security 51 – 3.1. NIST Cybersecurity Framework 77 – 4. Cybersecurity chain of trust; third party vendors 113 – 5. Ransomware 117 – 5.1. Exploit kits 132 – 6. Botnets 137 – 7. BIOS 139 – 7.1. Universal Extensible Firmware Interface (UEFI) 154– 8. Operating Systems 172 – 8.1. Microsoft Windows 197 – 8.2. macOS 236– 8.3. Open source operating system comparison 263 – 9. Firmware 273 – 10. Endpoint Security Buyers Guide 278 – 11. Glossaries & Acronym Dictionaries 11.1. Common Computer Abbreviations 282 – 11.2. BABEL 285 – 11.3. Information Technology Acronymns 291 – 11.4. Glossary of Operating System Terms 372 – 2 Cyber Security Primer Network outages, hacking, computer viruses, and similar incidents affect our lives in ways that range from inconvenient to life-threatening. As the number of mobile users, digital applications, and data networks increase, so do the opportunities for exploitation. Cyber security, also referred to as information technology security, focuses on protecting computers, networks, programs, and data from unintended or unauthorized access, change, or destruction.
    [Show full text]
  • Open Source Vendors' Business Model
    Linköping Studies in Science and Technology Dissertations, No. 1438 Open Source Vendors’ Business Models Thomas Rosenfall April 2012 Department of Management and Engineering Linköpings universitet, SE-581 83 Linköping, Sweden © Thomas Rosenfall, 2012 ”Open Source Vendor’s Business Models” Linköping Studies in Science and Technology, Dissertations, No. 1438 ISBN: 978-91-7519-926-9 ISSN: 0345-7524 Printed by: LiU-Tryck, Linköping Distributed by: Linköping University Department of Management and Engineering SE-581 83 Linköping, Sweden Tel: +46 13 281000 2 Acknowledgements This thesis was a long time in coming. The author is graciously indebted to several individu- als and organizations for their support and contributions during the process. First, the work of my supervisor, Anna Öhrwall Rönnbäck, together with professor Staffan Brege, whom probably are the sole reason for the completion of this thesis. Without their support and advice, the author would have given up years ago. The author would also like to thank the case companies and their representatives that have shown patience over the years, with a special note to the new and former management of Cendio AB. Several other colleagues have been involved in the process and provided much support and insight, for which the author is grateful. A special “thank you” goes to Christina Grundström for the support and advice concerning as assistance supervisor. Additionally, the author gra- ciously would like to thank Mica Comstock for the outstanding proofreading. The research was funded by Lundbergstiftelserna in 2005 - 2008, while the final thesis was conducted as a part of the research project BOSSANOVA, financed by VINNOVA between 2008 and 2011.
    [Show full text]