DOCSLIB.ORG

Free Software and Proprietary Software a History of Free Software the FOSS Development Model FOSS Business Model Conclusion

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Free Software and Proprietary Software a History of Free Software the FOSS Development Model FOSS Business Model Conclusion Free Software and Proprietary Software A History of Free Software The FOSS development model FOSS business model Conclusion Free Software Free as in freedom Josep M. Rib´o Universitat de Lleida January 22, 2009 Josep M. Rib´o Free Software Free Software and Proprietary Software A History of Free Software The FOSS development model FOSS business model Conclusion Outline 1 Free Software and Proprietary Software 2 A History of Free Software The first years 1980s: The begining of the Free Software Movement 1990s: Linux 2000s: The present of FOSS 3 The FOSS development model The Bazaar Infrastructure for FOSS projects 4 FOSS business model A collection of FOSS business models Community projects vs. corporate projects 5 Conclusion Josep M. Rib´o Free Software Free Software and Proprietary Software A History of Free Software The FOSS development model FOSS business model Conclusion You buy a brand new car..... Congratulations!!!! But unfortunatelly, its hood is locked and the seller has not given you the key :-( If you want to fix some add-ons or if the car breaks down you have to pay a visit to the Official Service (the only ones who have the key of the hood) ... and what will happen? Josep M. Rib´o Free Software Free Software and Proprietary Software A History of Free Software The FOSS development model FOSS business model Conclusion The official service The price is guaranteed to be excessive There is no competition (monopoly) It hinders the development of a network of local garage workshops It prevents you from fixing it yourself (provided you have mechanics knowledge) In a few years there will not be any maintenance for that car forcing you to buy a new one Would you buy a product like this? Well.... you probably have.... Take a look at the software that runs on your computer Josep M. Rib´o Free Software Free Software and Proprietary Software A History of Free Software The FOSS development model FOSS business model Conclusion What Free Software is Free Software definition It is software that comes packaged with several freedoms: Freedom to run it without any restriction Freedom to see its source code and to study it Freedom (and also encouragement) to redistribute it Freedom to modify it and to redistribute the modifications Josep M. Rib´o Free Software Free Software and Proprietary Software A History of Free Software The FOSS development model FOSS business model Conclusion What Free Software is not Free software is not: Inexpensive software In english Free = (1) Freedom (2) Free of charge Free software refers to free as in freedom not as in free of charge Freeware: Software which is distributed free of charge It is distributed only in binary format It may have restrictions to redistribute it Example: Microsoft Internet Explorer Josep M. Rib´o Free Software Free Software and Proprietary Software A History of Free Software The FOSS development model FOSS business model Conclusion What free software is not Shareware: Commercial software that is (usually) distributed free of charge for trial purposes before purchasing the software license It is distributed only in binary format And with limitations (it is not the full version or it only works for a limited period) Careware: Software that is obtained usually for a fee, which is donated to some charity This type of software can be free software (e.g. vim) Josep M. Rib´o Free Software Free Software and Proprietary Software A History of Free Software The FOSS development model FOSS business model Conclusion What free software is not And, obviously, free software is not... Proprietary software: Software that is legally owned by a specific party, which regulates the particular terms of access, use and distribution by means of a usually restrictive license Proprietary software usually has the opposite features to free software: Restrictions to use it Impossibility to study it (binary format) Prohibition to redistribute it Prohibition/Impossibility to modify it Josep M. Rib´o Free Software Free Software and Proprietary Software A History of Free Software The FOSS development model FOSS business model Conclusion Creative commons and copyleft It is not software all that glitters... Copyleft refers to a family of licenses for human works (software, documents, music, films ...) which grants the user the freedom to reproduce, adapt and redistribute the work... ... as long as the adapted work keeps the same license Creative commons licenses are licenses applied to human works (music, documents, software ...) that grant users certain rights The specific rights depend on the particular license Some rights: Attribution Non commercial use Non derivative work allowed Derivative work allowed (provided that the same license is kept in the derivative work). The same idea as in copyleft Josep M. Rib´o Free Software Free Software and Proprietary Software The first years A History of Free Software 1980s: The begining of the Free Software Movement The FOSS development model 1990s: Linux FOSS business model 2000s: The present of FOSS Conclusion Outline 1 Free Software and Proprietary Software 2 A History of Free Software The first years 1980s: The begining of the Free Software Movement 1990s: Linux 2000s: The present of FOSS 3 The FOSS development model The Bazaar Infrastructure for FOSS projects 4 FOSS business model A collection of FOSS business models Community projects vs. corporate projects 5 Conclusion Josep M. Rib´o Free Software Free Software and Proprietary Software The first years A History of Free Software 1980s: The begining of the Free Software Movement The FOSS development model 1990s: Linux FOSS business model 2000s: The present of FOSS Conclusion 1960s: The innocence of the youth In the 1960s IBM led the computer (i.e., mainframes) market with the IBM-360 The software (including the source code) to use those mainframes was sold together with the computers Communities of IBM/360 users (SHARE) and of DEC (DECUS) shared and distributed programs without any limitation At those early years software was still free Josep M. Rib´o Free Software Free Software and Proprietary Software The first years A History of Free Software 1980s: The begining of the Free Software Movement The FOSS development model 1990s: Linux FOSS business model 2000s: The present of FOSS Conclusion 1970s: The beginning of proprietary software In 1970 IBM started to sell some of their computer software separately from the computers themselves In mid 70s, proprietary software was the dominant business model among companies: software was sold without the source code and without the right of modifying and redistributing it In 70s proprietary software started its successful trip to become the dominant business model Josep M. Rib´o Free Software Free Software and Proprietary Software The first years A History of Free Software 1980s: The begining of the Free Software Movement The FOSS development model 1990s: Linux FOSS business model 2000s: The present of FOSS Conclusion Mid 70s and first 80s: A dim light in the dark Two brilliant individual initiatives offer an alternative to the proprietary software dominant position: SPICE (Larry Nagel, 1973): A simulator program for integrated circuits (Electronic Research Laboratory in the California University, Berkeley). TEX (Donald Knuth, 1978-1985): A text processor Donald Knuth Josep M. Rib´o Free Software Free Software and Proprietary Software The first years A History of Free Software 1980s: The begining of the Free Software Movement The FOSS development model 1990s: Linux FOSS business model 2000s: The present of FOSS Conclusion The role of Unix UNIX was first developed in 1969 by a group of AT&T developers at Bell Laboratories UNIX has always been a proprietary Operating System (Bell Laboratories and Novell), However, in 1973-74, Universities had free access to Unix source code and contributed to it 1980s: Access to Unix source code was difficult and expensive Unix followed the dominant trend and chose to be entirely proprietary Josep M. Rib´o Free Software Free Software and Proprietary Software The first years A History of Free Software 1980s: The begining of the Free Software Movement The FOSS development model 1990s: Linux FOSS business model 2000s: The present of FOSS Conclusion Outline 1 Free Software and Proprietary Software 2 A History of Free Software The first years 1980s: The begining of the Free Software Movement 1990s: Linux 2000s: The present of FOSS 3 The FOSS development model The Bazaar Infrastructure for FOSS projects 4 FOSS business model A collection of FOSS business models Community projects vs. corporate projects 5 Conclusion Josep M. Rib´o Free Software Free Software and Proprietary Software The first years A History of Free Software 1980s: The begining of the Free Software Movement The FOSS development model 1990s: Linux FOSS business model 2000s: The present of FOSS Conclusion 80s: The GNU Project At early 80s Richard Stallman was a hacker working at the AI laboratory at the MIT He shared with many other developers the so-called hacker culture which promoted the sharing, modification and redistribution of software source Richard Stallman However, in 1980 a big problem occurred: The AI laboratory. at the MIT bought a new HP printer... Josep M. Rib´o Free Software Free Software and Proprietary Software The first years A History of Free Software 1980s: The begining of the Free Software Movement The FOSS development model 1990s: Linux FOSS business model 2000s: The present of FOSS Conclusion 80's: The GNU project Stallman wanted to modify the controller software of the HP (as he had done with the previous printer) so that the controller sent a message to the user whose job was being printed However, he was not able to do so, since the source code of the accompanying software was not distributed anymore... And that was only the beginning...
Load more

Recommended publications
  • Practice Tips for Open Source Licensing Adam Kubelka
    Santa Clara High Technology Law Journal Volume 22 | Issue 4 Article 4 2006 No Free Beer - Practice Tips for Open Source Licensing Adam Kubelka Matthew aF wcett Follow this and additional works at: http://digitalcommons.law.scu.edu/chtlj Part of the Law Commons Recommended Citation Adam Kubelka and Matthew Fawcett, No Free Beer - Practice Tips for Open Source Licensing, 22 Santa Clara High Tech. L.J. 797 (2005). Available at: http://digitalcommons.law.scu.edu/chtlj/vol22/iss4/4 This Article is brought to you for free and open access by the Journals at Santa Clara Law Digital Commons. It has been accepted for inclusion in Santa Clara High Technology Law Journal by an authorized administrator of Santa Clara Law Digital Commons. For more information, please contact [email protected]. ARTICLE NO FREE BEER - PRACTICE TIPS FOR OPEN SOURCE LICENSING Adam Kubelkat Matthew Fawcetttt I. INTRODUCTION Open source software is big business. According to research conducted by Optaros, Inc., and InformationWeek magazine, 87 percent of the 512 companies surveyed use open source software, with companies earning over $1 billion in annual revenue saving an average of $3.3 million by using open source software in 2004.1 Open source is not just staying in computer rooms either-it is increasingly grabbing intellectual property headlines and entering mainstream news on issues like the following: i. A $5 billion dollar legal dispute between SCO Group Inc. (SCO) and International Business Machines Corp. t Adam Kubelka is Corporate Counsel at JDS Uniphase Corporation, where he advises the company on matters related to the commercialization of its products.
    [Show full text]
  • An Introduction to Software Licensing
    An Introduction to Software Licensing James Willenbring Software Engineering and Research Department Center for Computing Research Sandia National Laboratories David Bernholdt Oak Ridge National Laboratory Please open the Q&A Google Doc so that I can ask you Michael Heroux some questions! Sandia National Laboratories http://bit.ly/IDEAS-licensing ATPESC 2019 Q Center, St. Charles, IL (USA) (And you’re welcome to ask See slide 2 for 8 August 2019 license details me questions too) exascaleproject.org Disclaimers, license, citation, and acknowledgements Disclaimers • This is not legal advice (TINLA). Consult with true experts before making any consequential decisions • Copyright laws differ by country. Some info may be US-centric License and Citation • This work is licensed under a Creative Commons Attribution 4.0 International License (CC BY 4.0). • Requested citation: James Willenbring, David Bernholdt and Michael Heroux, An Introduction to Software Licensing, tutorial, in Argonne Training Program on Extreme-Scale Computing (ATPESC) 2019. • An earlier presentation is archived at https://ideas-productivity.org/events/hpc-best-practices-webinars/#webinar024 Acknowledgements • This work was supported by the U.S. Department of Energy Office of Science, Office of Advanced Scientific Computing Research (ASCR), and by the Exascale Computing Project (17-SC-20-SC), a collaborative effort of the U.S. Department of Energy Office of Science and the National Nuclear Security Administration. • This work was performed in part at the Oak Ridge National Laboratory, which is managed by UT-Battelle, LLC for the U.S. Department of Energy under Contract No. DE-AC05-00OR22725. • This work was performed in part at Sandia National Laboratories.
    [Show full text]
  • ** OPEN SOURCE LIBRARIES USED in Tv.Verizon.Com/Watch
    ** OPEN SOURCE LIBRARIES USED IN tv.verizon.com/watch ------------------------------------------------------------ 02/27/2019 tv.verizon.com/watch uses Node.js 6.4 on the server side and React.js on the client- side. Both are Javascript frameworks. Below are the licenses and a list of the JS libraries being used. ** NODE.JS 6.4 ------------------------------------------------------------ https://github.com/nodejs/node/blob/master/LICENSE Node.js is licensed for use as follows: """ Copyright Node.js contributors. All rights reserved. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. """ This license applies to parts of Node.js originating from the https://github.com/joyent/node repository: """ Copyright Joyent, Inc. and other Node contributors.
    [Show full text]
  • Open Source Software Notice
    Open Source Software Notice This document describes open source software contained in LG Smart TV SDK. Introduction This chapter describes open source software contained in LG Smart TV SDK. Terms and Conditions of the Applicable Open Source Licenses Please be informed that the open source software is subject to the terms and conditions of the applicable open source licenses, which are described in this chapter. | 1 Contents Introduction............................................................................................................................................................................................. 4 Open Source Software Contained in LG Smart TV SDK ........................................................... 4 Revision History ........................................................................................................................ 5 Terms and Conditions of the Applicable Open Source Licenses..................................................................................... 6 GNU Lesser General Public License ......................................................................................... 6 GNU Lesser General Public License ....................................................................................... 11 Mozilla Public License 1.1 (MPL 1.1) ....................................................................................... 13 Common Public License Version v 1.0 .................................................................................... 18 Eclipse Public License Version
    [Show full text]
  • Communicating Between the Kernel and User-Space in Linux Using Netlink Sockets
    SOFTWARE—PRACTICE AND EXPERIENCE Softw. Pract. Exper. 2010; 00:1–7 Prepared using speauth.cls [Version: 2002/09/23 v2.2] Communicating between the kernel and user-space in Linux using Netlink sockets Pablo Neira Ayuso∗,∗1, Rafael M. Gasca1 and Laurent Lefevre2 1 QUIVIR Research Group, Departament of Computer Languages and Systems, University of Seville, Spain. 2 RESO/LIP team, INRIA, University of Lyon, France. SUMMARY When developing Linux kernel features, it is a good practise to expose the necessary details to user-space to enable extensibility. This allows the development of new features and sophisticated configurations from user-space. Commonly, software developers have to face the task of looking for a good way to communicate between kernel and user-space in Linux. This tutorial introduces you to Netlink sockets, a flexible and extensible messaging system that provides communication between kernel and user-space. In this tutorial, we provide fundamental guidelines for practitioners who wish to develop Netlink-based interfaces. key words: kernel interfaces, netlink, linux 1. INTRODUCTION Portable open-source operating systems like Linux [1] provide a good environment to develop applications for the real-world since they can be used in very different platforms: from very small embedded devices, like smartphones and PDAs, to standalone computers and large scale clusters. Moreover, the availability of the source code also allows its study and modification, this renders Linux useful for both the industry and the academia. The core of Linux, like many modern operating systems, follows a monolithic † design for performance reasons. The main bricks that compose the operating system are implemented ∗Correspondence to: Pablo Neira Ayuso, ETS Ingenieria Informatica, Department of Computer Languages and Systems.
    [Show full text]
  • Linux Kernel and Driver Development Training Slides
    Linux Kernel and Driver Development Training Linux Kernel and Driver Development Training © Copyright 2004-2021, Bootlin. Creative Commons BY-SA 3.0 license. Latest update: October 9, 2021. Document updates and sources: https://bootlin.com/doc/training/linux-kernel Corrections, suggestions, contributions and translations are welcome! embedded Linux and kernel engineering Send them to [email protected] - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 1/470 Rights to copy © Copyright 2004-2021, Bootlin License: Creative Commons Attribution - Share Alike 3.0 https://creativecommons.org/licenses/by-sa/3.0/legalcode You are free: I to copy, distribute, display, and perform the work I to make derivative works I to make commercial use of the work Under the following conditions: I Attribution. You must give the original author credit. I Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under a license identical to this one. I For any reuse or distribution, you must make clear to others the license terms of this work. I Any of these conditions can be waived if you get permission from the copyright holder. Your fair use and other rights are in no way affected by the above. Document sources: https://github.com/bootlin/training-materials/ - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 2/470 Hyperlinks in the document There are many hyperlinks in the document I Regular hyperlinks: https://kernel.org/ I Kernel documentation links: dev-tools/kasan I Links to kernel source files and directories: drivers/input/ include/linux/fb.h I Links to the declarations, definitions and instances of kernel symbols (functions, types, data, structures): platform_get_irq() GFP_KERNEL struct file_operations - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 3/470 Company at a glance I Engineering company created in 2004, named ”Free Electrons” until Feb.
    [Show full text]
  • Are Projects Hosted on Sourceforge.Net Representative of the Population of Free/Open Source Software Projects?
    Are Projects Hosted on Sourceforge.net Representative of the Population of Free/Open Source Software Projects? Bob English February 5, 2008 Introduction We are researchers studying Free/Open Source Software (FOSS) projects . Because some of our work uses data gathered from Sourceforge.net (SF), a web site that hosts FOSS projects, we consider it important to understand how representative SF is of the entire population of FOSS projects. While SF is probably hosts the greatest number of FOSS projects, there are many other similar hosting sites. In addition, many FOSS projects maintain their own web sites and other project infrastructure on their own servers. Based on performing an Internet search and literature review (see Appendix for search procedures), it appears that no one knows how many Free/Open Source Software Projects exist in the world or how many people are working on them. Because the population of FOSS projects and developers is unknown, it is not surprising that we were not able to find any empirical analysis to assess how representative SF is of this unknown population. Although an extensive empirical analysis has not been performed, many researchers have considered the question or related questions. The next section of this paper reviews some of the FOSS literature that discusses the representativeness of SF. The third section of the paper describes some ideas for empirically exploring the representativeness of SF. The paper closes with some arguments for believing SF is the best choice for those interested in studying the population of FOSS projects. Literature Review In one of the earliest references to the representativeness of SF, Madley, Freeh and Tynan (2002) mention that they assumed that SF was representative because of its popularity and because of the number of projects hosted there, although they note that this assumption “needs to be confirmed” (p.
    [Show full text]
  • Annex I Definitions
    Annex I Definitions Free and Open Source Software (FOSS): Software whose source code is published and made available to the public, enabling anyone to copy, modify and redistribute the source code without paying royalties or fees. Open source code evolves through community cooperation. These communities are composed of individual programmers and users as well as very large companies. Some examples of open source initiatives are GNU/Linux, Eclipse, Apache, Mozilla, and various projects hosted on SourceForge1 and Savannah2 Web sites. Proprietary software -- Software that is distributed under commercial licence agreements, usually for a fee. The main difference between the proprietary software licence and the open source licence is that the recipient does not normally receive the right to copy, modify, redistribute the software without fees or royalty obligations. Something proprietary is something exclusively owned by someone, often with connotations that it is exclusive and cannot be used by other parties without negotiations. It may specifically mean that the item is covered by one or more patents, as in proprietary technology. Proprietary software means that some individual or company holds the exclusive copyrights on a piece of software, at the same time denying others access to the software’s source code and the right to copy, modify and study the software. Open standards -- Software interfaces, protocols, or electronic formats that are openly documented and have been accepted in the industry through either formal or de facto processes, which are freely available for adoption by the industry. The open source community has been a leader in promoting and adopting open standards. Some of the success of open source software is due to the availability of worldwide standards for exchanging information, standards that have been implemented in browsers, email systems, file sharing applications and many other tools.
    [Show full text]
  • FOSS Philosophy 6 the FOSS Development Method 7
    1 Published by the United Nations Development Programme’s Asia-Pacific Development Information Programme (UNDP-APDIP) Kuala Lumpur, Malaysia www.apdip.net Email: [email protected] © UNDP-APDIP 2004 The material in this book may be reproduced, republished and incorporated into further works provided acknowledgement is given to UNDP-APDIP. For full details on the license governing this publication, please see the relevant Annex. ISBN: 983-3094-00-7 Design, layout and cover illustrations by: Rezonanze www.rezonanze.com PREFACE 6 INTRODUCTION 6 What is Free/Open Source Software? 6 The FOSS philosophy 6 The FOSS development method 7 What is the history of FOSS? 8 A Brief History of Free/Open Source Software Movement 8 WHY FOSS? 10 Is FOSS free? 10 How large are the savings from FOSS? 10 Direct Cost Savings - An Example 11 What are the benefits of using FOSS? 12 Security 13 Reliability/Stability 14 Open standards and vendor independence 14 Reduced reliance on imports 15 Developing local software capacity 15 Piracy, IPR, and the WTO 16 Localization 16 What are the shortcomings of FOSS? 17 Lack of business applications 17 Interoperability with proprietary systems 17 Documentation and “polish” 18 FOSS SUCCESS STORIES 19 What are governments doing with FOSS? 19 Europe 19 Americas 20 Brazil 21 Asia Pacific 22 Other Regions 24 What are some successful FOSS projects? 25 BIND (DNS Server) 25 Apache (Web Server) 25 Sendmail (Email Server) 25 OpenSSH (Secure Network Administration Tool) 26 Open Office (Office Productivity Suite) 26 LINUX 27 What is Linux?
    [Show full text]
  • Free Software As Commons
    FREE SOFTWARE AS COMMONS BETWEEN INFORMATIONAL CAPITALISM AND A NEW MODE OF PRODUCTION By Emrah Irzık Submitted to Central European University Department of Sociology and Social Anthropology In partial fulfillment of the requirements for the degree of Doctor of Philosophy Supervisor: Professor Jakob Rigi CEU eTD Collection Budapest, Hungary 2015 Statement I hereby state that the thesis contains no material accepted for any other degrees in any other institutions. The thesis contains no materials previously written and/or published by another person, except where appropriate acknowledgment is made in the form of bibliographical reference. Emrah Irzık Budapest, November 2015 CEU eTD Collection Abstract Free Software is a particular way of organizing the production and distribution of software that offers a solid alternative to the intellectual property regime by constituting an open commons: non-proprietary, created and held in common by all. Considering that in contemporary capitalism a significant amount of wealth is created through the application of intellectual effort to existing knowledge to produce new, higher compositions of knowledge that can be privately monetized as intellectual property, the challenge that Free Software might present to capitalism is bound to have important transformational potential. This potential needs to be studied both on an empirical level, in its partial and concrete manifestations in actual projects, and investigated more theoretically, to see if Free Software can be characterized as a nascent, new mode of production. This dissertation aims to contribute to the theorization of the relation between Free Software as a commons and the tenets of informational capitalism by means of an analytical study that is supported by an ethnography of a particular instance of Free Software as a project and a community.
    [Show full text]
  • Linux 2.5 Kernel Developers Summit
    conference reports This issue’s reports are on the Linux 2.5 Linux 2.5 Kernel Developers Linux development, but I certainly Kernel Developers Summit Summit thought that, in all of this time, someone would have brought this group together OUR THANKS TO THE SUMMARIZER: SAN JOSE, CALIFORNIA before. Rik Farrow, with thanks to La Monte MARCH 30-31, 2001 Yarroll and Chris Mason for sharing their Summarized by Rik Farrow Another difference appeared when the notes. first session started on Friday morning. The purpose of this workshop was to The conference room was set up with cir- provide a forum for discussion of cular tables, each with power strips for changes to be made in the 2.5 release of For additional information on the Linux laptops, and only a few attendees were Linux (a trademark of Linus Torvalds). I not using a laptop. USENIX had pro- 2.5 Kernel Developers Summit, see the assume that many people reading this vided Aeronet wireless setup via the following sites: will be familiar with Linux, and I will hotel’s T1 link, and people were busy <http://lwn.net/2001/features/KernelSummit/> attempt to explain things that might be typing and compiling. Chris Mason of unfamiliar to others. That said, the odd- <http://cgi.zdnet.com/slink?91362:12284618> OSDN noticed that Dave Miller had numbered releases, like 2.3 and now 2.5, <http://www.osdn.com/conferences/kernel/> written a utility to modulate the speed of are development releases where the the CPU fans based upon the tempera- intent is to try out new features or make ture reading from his motherboard.
    [Show full text]
  • Linux Kernel 8.1 Introduction
    Page 1 of 6 Linux Kernel 8.1 Introduction: The Linux kernel is a Unix-like operating system kernel used by a variety of operating systems based on it, which are usually in the form of Linux distributions. The Linux kernel is a prominent example of free and open source software. The Linux kernel is released under the GNU General Public License version 2 (GPLv2) (plus some firmware images with various non-free licenses), and is developed by contributors worldwide. Day-to-day development discussions take place on the Linux kernel mailing list. The Linux kernel was initially conceived and created in 1991 by Finnish computer science student Linus Torvalds. Linux rapidly accumulated developers and users who adapted code from other free software projects for use with the new operating system. The Linux kernel has received contributions from thousands of programmers. 8.2 History: History In April 1991, Linus Torvalds, a 21-year-old student at the University of Helsinki, Finland started working on some simple ideas for an operating system. He started with a task switcher in Intel 80386 assembly language and a terminal driver. On 25 August 1991, Torvalds posted the following to comp.os.minix, a newsgroup on Usenet: I'm doing a (free) operating system (just a hobby, won't be big and professional like gnu) for 386(486) AT clones. This has been brewing since April, and is starting to get ready. I'd like any feedback on things people like/dislike in minix, as my OS resembles it somewhat (same physical layout of the file-system (due to practical reasons) among other things).
    [Show full text]