DOCSLIB.ORG

Projet IRIS Le Financement Du Logiciel Libre

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Projet IRIS Le Financement Du Logiciel Libre Projet IRIS Le financement du logiciel libre Y-Lan Boureau Renaud Duplay St´ephane Lescuyer Julien Mairal Quentin Munier Annelise Rapha¨el Septembre 2005 Ecole´ Nationale Sup´erieure des T´el´ecommunications Cycle d'ouverture aux T´el´ecommunications 1 Table des mati`eres 1 Le monde du libre 3 1.1 Qu'est-ce que le logiciel libre ? . 4 1.1.1 La naissance du concept . 4 1.1.2 Les principes fondateurs . 5 1.2 Les besoins en financement . 8 1.2.1 Le cout^ humain . 8 1.2.2 Distribution des logiciels . 9 1.2.3 Communication efficace . 9 2 Les diff´erents modes de financement 12 2.1 Le financement par la communaut´e . 12 2.2 Services suppl´ementaires . 14 2.3 Entreprise : commande d'un logiciel . 15 2.4 SAV, maintenance, formation . 17 2.5 Produits d´eriv´es . 18 2.6 M´ec´enat priv´e . 18 2.7 Les Etats et le logiciel libre . 21 2.7.1 L'int´er^et des Etats pour le "libre" . 21 2.7.2 Une intervention mesur´ee des Etats . 22 2.7.3 Le soutien feutr´e des pays du Nord . 23 2.7.4 Le volontarisme des pays en voie de d´eveloppement . 26 2.7.5 Bilan . 29 3 Equilibre entre ces modes de financements : ´evolutions et perspectives 29 3.1 Les disparit´es du libre, deux exemples . 29 3.1.1 Ubuntu . 29 3.1.2 Debian . 32 3.2 Perspectives . 32 3.2.1 Ubuntu . 33 3.2.2 Debian . 33 3.3 Fiscalit´e . 34 2 Introduction Free as in "free speech", not "free beer" Richard M. Stallman L'un des paradoxes des communaut´es de d´eveloppement de logiciels libres est qu'elles r´eussissent le tour de force apparent de faire de l'argent avec du gratuit ; la gratuit´e ne fait pas fondamentalement partie de l'essence de la philosophie du libre, mais dans les faits elle est tr`es largement r´epandue. C'est l'une des sources de la fascination pour le monde du libre des non- sp´ecialistes comme les journalistes, qui assurent au logiciel libre une bonne image m´ediatique : dans un monde de plus en plus largement domin´e par l'´economie de march´e et sa logique de rentabilit´e impitoyable, les commu- naut´es de d´eveloppeurs qui distribuent le r´esultat de leur travail en toute gratuit´e alors que l'homme le plus riche du monde est justement un informa- ticien, font un peu figure de \petit village d'irr´eductibles qui r´esiste encore et toujours a` l'envahisseur". Mais cette image d'Epinal ne doit pas faire oublier que les communaut´es de logiciel libre ont leur propre logique ´economique, m^eme si elle est radica- lement diff´erente de celle d'une entreprise fond´ee sur le logiciel propri´etaire comme Microsoft (ou Adobe ou Macromedia si on en a assez de parler seule- ment du g´eant de Redmond). Les structures de la communaut´e du libre brassent de l'argent, et en ont besoin pour fonctionner, qu'il s'agisse des en- treprises fortement impliqu´ees dans le libre comme Novell, Sun, Mandriva, Canonical Limited, ou des cellules plus petites de la communaut´e. Nous allons tenter de mieux cerner cette logique ´economique, en analysant comment s'organise le financement du libre. Pour ce faire, il importe en pre- mier lieu de donner quelques ´eclaircissements sur ce qu'est le monde du libre, de sa philosophie a` ses besoins financiers. Ensuite, nous passerons en revue les diff´erentes sources de financement, des dons de particuliers aux financements ´etatiques, en passant par les partenariats avec les entreprises. Enfin, nous montrerons comment ces modes de financement vari´es s'articulent a` travers deux exemples de distributions Linux, Ubuntu et Debian. 1 Le monde du libre En tr`es peu d'ann´ees, les logiciels libres sont devenus incontournables. Cependant, si tout le monde sait ce qu'est un logiciel, le concept de libre, lui, reste souvent flou et parfois mal compris. Nous entreprenons ici de rappeler 3 les notions pr´ecises qui se cachent dans cette expression, ce que sont les logiciels libres et quels sont les besoins de financement dans ce domaine. 1.1 Qu'est-ce que le logiciel libre ? 1.1.1 La naissance du concept Le projet du logiciel libre na^ıt en 1984 avec le manifeste GNU1 de Ri- chard Stallman. Pour autant, jusqu’`a cette date, les logiciels n'´etaient pas que propri´etaires. L'usage g´en´eral en vogue au d´ebut des ann´ees 70, lorsque Stallman a commenc´e sa carri`ere, ´etait plut^ot a` la libert´e des logiciels et a` une coop´eration totale entre les d´eveloppeurs, h´erit´ee en grande partie de la pratique universitaire. Le manifeste de Stallman ne d´ecrivait donc pas un ph´enom`ene nouveau, mais se posait en fondateur d'un concept qui lui tenait a` cœur. Sa r´edaction fut motiv´ee justement par l'´emergence de la pratique du logiciel propri´etaire a` la fin des ann´ees 70. Un logiciel est propri´etaire quand son concepteur (entreprise ou individu) en restreint l'acc`es ou l'utilisation, ou quand le code source n'est pas disponible. C'est notamment la fermeture du code source qui emp^eche la coop´eration au sein de la communaut´e des d´eveloppeurs, et qui peut poser des probl`emes de s´ecurit´e : il n'y a pas de moyen a priori pour l'utilisateur de v´erifier quel type d'op´erations le logiciel effectue, la seule solution est de faire confiance a` l'´editeur du logiciel. Dans ce contexte, le manifeste de Stallman s'´etablissait comme le projet de d´efense d'une certaine vision, d'une certaine ´ethique, du d´eveloppement et de la diffusion de la ressource logicielle informatique. Le but du projet consistait a` s’affranchir de tous les logiciels propri´etaires, a` commencer par le syst`eme d'exploitation. En effet, avoir un syst`eme d'exploitation r´epondant a` ces crit`eres ´ethiques ´etait une condition sine qua none pour pouvoir se passer de logiciels propri´etaires comme MS-DOS2. Pour arriver au bout de ce projet ambitieux, Richard Stallman cr´ea la Free Software Foundation, destin´ee a` r´ecup´erer des dons pour soutenir l’effort du projet. Apr`es plusieurs ann´ees de travail acharn´e, en 1991, la pierre finale de l'´edifice sera apport´ee par Linus Torvalds et son noyau, Linux, la base de toutes les distributions Linux actuelles. 1Acronyme r´ecursif pour GNU's not Unix 2Microsoft Disk Operating System, publi´e en 1981, a ´et´e le syst`eme d'exploitation le plus utilis´e sur les ordinateurs personnels IBM dans les ann´ees 80, jusqu’`a son remplacement progressif par Windows 3.1 puis Windows 95 dans la premi`ere moiti´e des ann´ees 90 4 1.1.2 Les principes fondateurs Le logiciel libre est ouvert et gratuit : il est gratuit car on ne peut emp^echer sa distribution gratuite, mais il faut noter que l'on peut tout a` fait vendre du logiciel libre. Il est ouvert parce que son code source est disponible dans une forme qui permet d'en comprendre le fonctionnement, c’est-`a-dire non compil´e. Ces deux conditions, prise une a` une, ne sont pas suffisantes : il existe des logiciels gratuits mais propri´etaires et il existe des logiciels ouverts mais que l'on n'a pas le droit de modifier sous peine de sanctions p´enales. Pour ^etre r´eellement libre, un logiciel doit ^etre fourni avec une licence de logiciel libre. Pour d´efinir les conditions sous lesquelles une licence peut ^etre consid´er´ee comme une licence du logiciel libre et encourager leur utilisa- tion, Bruce Perens et Eric Raymond ont cr´e´e a` la fin des ann´ees 90 l'Open Source Initiative3. Dans un document repr´esentant un consensus entre les d´eveloppeurs de logiciels libres, ils d´efinissent les crit`eres n´ecessaires a` l'ap- pellation libre, au nombre de dix. 1. Redistribution libre The license shall not restrict any party from selling or giving away the soft- ware as a component of an aggregate software distribution containing pro- grams from several different sources. The license shall not require a royalty or other fee for such sale. Une licence de logiciel libre ne peut donc emp^echer la diffusion de ce logiciel, sa vente, ou son utilisation au sein d'autres applications. Il est important de remarquer qu'il est explicitement interdit de restreindre l'utilisation du logiciel a` des applications non commerciales.4 2. Code source The program must include source code, and must allow distribution in source code as well as compiled form. Where some form of a product is not distri- buted with source code, there must be a well-publicized means of obtaining the source code for no more than a reasonable reproduction cost - preferably, downloading via the Internet without charge. The source code must be the preferred form in which a programmer would modify the program. Delibera- tely obfuscated source code is not allowed. Intermediate forms such as the output of a preprocessor or translator are not allowed. 3OSI, http://www.opensource.org 4La port´ee de cette clause est sujette a` controverse : la General Public License (GPL) emp^eche l'int´egration du code dans un logiciel propri´etaire.
Load more

Recommended publications
  • Latent GOLD, Polca, and MCLUST
    JOBNAME: tast 63#1 2009 PAGE: 1 OUTPUT: Thursday January 15 07:45:17 2009 asa/tast/164303/SR3 Review of Three Latent Class Cluster Analysis Packages: Latent GOLD, poLCA, and MCLUST Dominique HAUGHTON, Pascal LEGRAND, and Sam WOOLFORD McCutcheon (2002). Because LCA is based upon a statistical model, maximum likelihood estimates can be used to classify This article reviews three software packages that can be used cases based upon what is referred to as their posterior proba- to perform latent class cluster analysis, namely, Latent GOLDÒ, bility of class membership. In addition, various diagnostics are MCLUST, and poLCA. Latent GOLDÒ is a product of Statistical available to assist in the determination of the optimal number Innovations whereas MCLUST and poLCA are packages of clusters. written in R and are available through the web site http:// LCA has been used in a broad range of contexts including www.r-project.org. We use a single dataset and apply each sociology, psychology, economics, and marketing. LCA is software package to develop a latent class cluster analysis for presented as a segmentation tool for marketing research and the data. This allows us to compare the features and the tactical brand decision in Finkbeiner and Waters (2008). Other resulting clusters from each software package. Each software applications in market segmentation are given in Cooil, package has its strengths and weaknesses and we compare the Keiningham, Askoy, and Hsu (2007), Malhotra, Person, and software from the perspectives of usability, cost, data charac- Bardi Kleiser (1999), Bodapati (2008), and Pancras and Sudhir teristics, and performance.
    [Show full text]
  • R Pass by Reference
    R Pass By Reference Unlidded Sherlock verjuices or imbibe some pancake ingenuously, however littery Winifield denitrifies detestably or jellified. Prasun rhubarbs simperingly while overnice Stanleigh witch thru or rent immemorially. Acescent and unprejudiced Tanney stints her distillations damming or jitterbugging luxuriously. Doing so any task in the argument and reference by value of the use it and data have no problems become hard to have been deactivated Thanks for sharing it. Modernization can operate much faster, simpler, and safer when supported with analysis tools and even code transformation tools. But by appending an element, they created a new hardware which, of course, did you update the reference. Joe, this is indeed excellent tutorial in your Java kitty. However, this section focuses on wade is afraid to template implementation. What are someone different types of Classes in Java? To insure goods are released, we need to begin able to decrement their reference counts once we no longer made them. You should contact the package authors for that. Limit the loop variable visibility to the except of cord loop. Protected member function can be simply fine. If she is a default constructor, compare those assignments to the initializations in the default constructor. Left clear Right sides of an assignment statement. What began the basic Structure of a Java Program? This can experience nasty bugs that are extremely hard to debug. Warn the two consecutive parameters share is same type. How can Convert Char To stuff In Java? Please lift the information below before signing in. NOTHING but pass by reference in Java.
    [Show full text]
  • Compiling C++ Files & Declarations and Definitions
    Compiling C++ files Compiling C++ files 143 Compiling C++ files Hello World 2.0 Hello World 2.0 In C++ the code is usually separated into header files (.h/.hpp) and implementation files (.cpp/.cc): sayhello.hpp #include <string> void sayhello(const std::string& name); sayhello.cpp #include "sayhello.hpp" #include <iostream> void sayhello(const std::string& name){ std::cout << "Hello " << name << '!' << std::endl; } Other code that wants to use this function only has to include sayhello.hpp. 144 Compiling C++ files Compiler Compiler Reminder: Internally, the compiler is divided into Preprocessor, Compiler, and Linker. Preprocessor: • Takes an input file of (almost) any programming language • Handles all preprocessor directives (i.e., all lines starting with #) and macros • Outputs the file without any preprocessor directives or macros Compiler: • Takes a preprocessed C++ (or C) file, called translation unit • Generates and optimizes the machine code • Outputs an object file Linker: • Takes multiple object files • Can also take references to other libraries • Finds the address of all symbols (e.g., functions, global variables) • Outputs an executable file or a shared library 145 Compiling C++ files Compiler Preprocessor Most common preprocessor directives: • #include: Copies (!) the contents of a file into the current file // include system file iostream: #include <iostream> // include regular file myfile.hpp: #include "myfile.hpp" • #define: Defines a macro #define FOO // defines the macro FOO with no content #define BAR 1 // defines the macro BAR as 1 • #ifdef/#ifndef/#else/#endif: Removes all code up to the next #else/#endif if a macro is set (#ifdef) or not set (#ifndef) #ifdef FOO ..
    [Show full text]
  • Khem Raj [email protected] Embedded Linux Conference 2014, San Jose, CA
    Khem Raj [email protected] Embedded Linux Conference 2014, San Jose, CA } Introduction } What is GCC } General Optimizations } GCC specific Optimizations } Embedded Processor specific Optimizations } What is GCC – Gnu Compiler Collection } Cross compiling } Toolchain } Cross compiling } Executes on build machine but generated code runs on different target machine } E.g. compiler runs on x86 but generates code for ARM } Building Cross compilers } Crosstool-NG } OpenEmbedded/Yocto Project } Buildroot } OpenWRT } More …. } On } controls compilation time } Compiler memory usage } Execution speed and size/space } O0 } No optimizations } O1 or O } General optimizations no speed/size trade-offs } O2 } More aggressive than O1 } Os } Optimization to reduce code size } O3 } May increase code size in favor of speed Property General Size Debug Speed/ Opt level info Fast O 1 No No No O1..O255 1..255 No No No Os 2 Yes No No Ofast 3 No No Yes Og 1 No Yes No } GCC inline assembly syntax asm ( assembly template : output operands : input operands : A list of clobbered registers ); } Used when special instruction that gcc backends do not generate can do a better job } E.g. bsrl instruction on x86 to compute MSB } C equivalent long i; for (i = (number >> 1), msb_pos = 0; i != 0; ++msb_pos) i >>= 1; } Attributes aiding optimizations } Constant Detection } int __builtin_constant_p( exp ) } Hints for Branch Prediction } __builtin_expect #define likely(x) __builtin_expect(!!(x), 1) #define unlikely(x) __builtin_expect(!!(x), 0) } Prefetching } __builtin_prefetch
    [Show full text]
  • Proceedings.Pdf
    Goals and scopes •The goals of the workshop is to create a forum around advances or experience in Smalltalk and to trigger discussions and exchanges of ideas. Participants are invited to submit research articles. We will not enforce any length restriction. However we expect papers of two kinds: –Short position papers describing emerging ideas. –Long research papers with deeper description of experiments and of research results. •We welcome contributions on all aspects, theoretical as well as practical, of Smalltalk related topics such as: –Aspect-oriented programming, –Design patterns, –Experience reports, –Frameworks, –Implementation, –new dialects or languages implemented in Smalltalk, –Interaction with other languages, –Meta-programming and Meta-modeling, –Tools Publication •Both submissions and final papers must be prepared using the ACM SIGPLAN 10 point format. Templates for Word and LaTeX are available at http://www.acm.org/sigs/sigplan/authorInformation.htm •Authors of the best accepted papers will also be invited to submit extended versions for publication in a special issue of Elsevier "Science of Computer Programming: Methods of Software Design: Techniques and Applications" •Please submit your paper through EasyChair on http://www.easychair.org/conferences/?conf=iwst2012 Program Chairs •Loïc Lagadec Lab-STICC, UBO, France •Alain Plantec, Lab-STICC, UBO, France Program Committee •Gabriela Arevalo, Universidad Nacional de Quilmes, Agentina •Alexandre Bergel University of Chile •Andrew P. Black Portland State University, US •Marcus
    [Show full text]
  • In Using the GNU Compiler Collection (GCC)
    Using the GNU Compiler Collection For gcc version 6.1.0 (GCC) Richard M. Stallman and the GCC Developer Community Published by: GNU Press Website: http://www.gnupress.org a division of the General: [email protected] Free Software Foundation Orders: [email protected] 51 Franklin Street, Fifth Floor Tel 617-542-5942 Boston, MA 02110-1301 USA Fax 617-542-2652 Last printed October 2003 for GCC 3.3.1. Printed copies are available for $45 each. Copyright c 1988-2016 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with the Invariant Sections being \Funding Free Software", the Front-Cover Texts being (a) (see below), and with the Back-Cover Texts being (b) (see below). A copy of the license is included in the section entitled \GNU Free Documentation License". (a) The FSF's Front-Cover Text is: A GNU Manual (b) The FSF's Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU software. Copies published by the Free Software Foundation raise funds for GNU development. i Short Contents Introduction ::::::::::::::::::::::::::::::::::::::::::::: 1 1 Programming Languages Supported by GCC ::::::::::::::: 3 2 Language Standards Supported by GCC :::::::::::::::::: 5 3 GCC Command Options ::::::::::::::::::::::::::::::: 9 4 C Implementation-Defined Behavior :::::::::::::::::::: 373 5 C++ Implementation-Defined Behavior ::::::::::::::::: 381 6 Extensions to
    [Show full text]
  • Libreoffice 3.4 Draw Guide
    LibreOffice 3.4 Draw Guide Drawing Vector Graphics in LibreOffice Copyright This document is Copyright © 2012 by its contributors as listed below. You may distribute it and/or modify it under the terms of either the GNU General Public License (http://www.gnu.org/licenses/gpl.html), version 3 or later, or the Creative Commons Attribution License (http://creativecommons.org/licenses/by/3.0/), version 3.0 or later. All trademarks in this guide belong to their legitimate owners. Contributors Martin Fox John Cleland Jean Hollis Weber John A Smith Feedback Please direct any comments or suggestions about this document to: [email protected] Acknowledgments This book is based on and updated from OpenOffice.org 3.3 Draw Guide. The contributors to that book are: Agnes Belzunce Daniel Carrera Martin Fox Thomas Hackert Regina Henschel Peter Hillier-Brook Jared Kobos Hazel Russman Gary Schnabl Bernd Schukat Wolfgang Uhlig Jean Hollis Weber Claire Wood Linda Worthington Publication date and software version Published 10 May 2012. Based on LbreOffice 3.4.6. Documentation for LibreOffice is available at http://www.libreoffice.org/get-help/documentation Contents Copyright..................................................................................................................................... 2 Note for Mac users...................................................................................................................... 5 Chapter 1 Introducing Draw..................................................................................................................7
    [Show full text]
  • Strategies for Unbridled Data Dissemination: an Emergency Operations Manual
    Strategies for Unbridled Data Dissemination: An Emergency Operations Manual Nikita Mazurov PhD Thesis Centre for Cultural Studies, Goldsmiths, University of London 1 Declaration To the extent that this may make sense to the reader, I declare that the work presented in this thesis is my own. Nikita Mazurov 2 Acknowledgements The notion that the work in a thesis is ‘one’s own’ doesn’t seem quite right. This work has benefited from countless insights, critiques, commentary, feedback and all potential other manner of what is after all, work, by those who were subjected to either parts or the entirety of it during encounters both formal and informal. To say nothing of the fact that every citation is an acknowledgement of prior contributory work in its own right. I may have, however, mangled some or all of the fine input that I have received, for which I bear sole responsibility. Certain images were copied from other publications for illustrative purposes. They have been referenced when such is the case. Certain other images were provided by sources who will rename anonymous for reasons of safety. Assistance with technical infrastructure in establishing a server for part of the project was provided by another anonymous source; anonymous for the same reason as above. 3 Abstract This project is a study of free data dissemination and impediments to it. Drawing upon post-structuralism, Actor Network Theory, Participatory Action Research, and theories of the political stakes of the posthuman by way of Stirnerian egoism and illegalism, the project uses a number of theoretical, technical and legal texts to develop a hacker methodology that emphasizes close analysis and disassembly of existent systems of content control.
    [Show full text]
  • Mclinker - the final Toolchain Frontier
    MCLinker - the final toolchain frontier J¨orgSonnenberger March 16, 2013 Abstract Google gold on the other hand mixes the first two phases. Symbols that can't be resolved in the first LLVM and Clang provide the top half of an inte- round are retried later. This choice improves the grated BSD licensed cross-platform toolchain. The maintainability of performance of the linker code, MCLinker project implements the remaining parts. but is still more complicated than the design of It is compact, modular and efficient. Currently MCLinker. It is useful to note that gold supports supported platforms are ELF systems running X86 multi-threading during the relocation processing to (32bit and 64bit), ARM and MIPS. MIPS64 and speed up linking large input sets. Hexagon are work-in-progress. 2.1 Input tree 1 Introduction The input tree is the first intermediate representa- Following the GPL3 announcement of the Free Soft- tion (IR) used by MCLinker. It contains vertices ware Foundation, the LLVM project gained a lot for every input file and all positional options. Posi- of traction. The Clang front-end allows replac- tional options are options like {start-group or {as- ing GCC for C and C++ code on many impor- needed that change the handling of a subset of the tant platforms. The Machine Code layer provides input files. Input files can form subtrees, e.g. linker an integrated assembler, replacing the dependency archives form a subtree with a child node for every on external assemblers for most situations. The archive member. Edges in the input graph are ei- combination provides a powerful toolchain with full ther positional relationships for options or inclusion support for cross-compilation.
    [Show full text]
  • What Makes LLD So Fast Slides with Presenter Notes
    What makes LLD so fast? Peter Smith, Linaro Contents and Introduction ● What we are covering Today ○ What job does a linker do? ○ How fast is LLD compared to GNU ld and gold? ○ LLD design and implementation choices. ○ Non technical factors. ● My history with Linkers ○ Working in the Linaro TCWG team on LLVM. ○ Have made contributions to LLD, focusing on Arm and AArch64. ○ Have previously worked on Arm’s embedded linker armlink. What job does a ● Components of an ELF file ● Generic linker design linker do? ● Finding content ● Layout ● Relocation What is a Linker? ● Levine defines in Linkers and Loaders ○ “Binds more abstract names to more concrete names, which permits programmers to write code using more abstract names” ○ In general concrete representations are higher performance but less flexible ● In practice a tool that glues together the outputs of separate compilation into a single output A linker is in many ways a slightly more sophisticated version of cat. The linker must copy the necessary data from all the input objects, rearrange it and resolve fixups. It is worth bearing this in mind when complaining that the linker is slow, just doing a cat of all the object files can also take a significant amount of time, particularly when debug information is involved. Important components of a relocatable object file Sections: Relocations: A calculation done at link time with Contiguous .text value written to contents of section ranges of main: in output. bytes with movabsq $.L.str, %rdi R_X86_64_64 .ro.data.str1.1 + 0 the same ... properties. callq printf R_X86_64_PLT32 printf - 4 ... Sections are the .rodata.str1.1 atoms of .asciz “Hello World” Symbols: linking.
    [Show full text]
  • Shell Scripting Expert Recipes for Linux, Bash, and More.Pdf
    SHELL SCRIPTING EXPERT RECIPES FOR LINUX, BASH, AND MORE INTRODUCTION . .xxix ⊲ PART I AbOUT THE INGREDIENTS CHAPTER 1 The History of Unix, GNU, and Linux . 3 CHAPTER 2 Getting Started . 15. CHAPTER 3 Variables . 33 CHAPTER 4 Wildcard Expansion . .67 CHAPTER 5 Conditional Execution . .83 CHAPTER 6 Flow Control Using Loops . 111 CHAPTER 7 Variables Continued . 139 CHAPTER 8 Functions and Libraries . 16. 1 CHAPTER 9 Arrays . 199 CHAPTER 10 Processes . 219 CHAPTER 11 Choosing and Using Shells . 255 ⊲ PART II RECIPES FOR UsING AND EXTENDING SYSTEM TOOLS CHAPTER 12 File Manipulation . 279 CHAPTER 13 Text Manipulation . 315 CHAPTER 14 Tools for Systems Administration . 353 ⊲ PART III RECIPES FOR SYSTEms ADMINISTRATION CHAPTER 15 Shell Features . 40. 9 CHAPTER 16 Systems Administration . 427 CHAPTER 17 Presentation . 459 CHAPTER 18 Data Storage and Retrieval . .471 CHAPTER 19 Numbers . 483 CHAPTER 20 Processes . 501 CHAPTER 21 Internationalization . .517 Continues ⊲ PART I V REFERENCE APPENDIX Further Reading . 529 GLOssARY . 533 INDEX . 539 Shell Scripting EXPERT ReCIPES FOR LINUX, BASH, AND MORE Shell Scripting EXPERT RECIPES FOR LINUX, BASH, AND MORE Steve Parker Shell Scripting: Expert Recipes for Linux, Bash, and More Published by John Wiley & Sons, Inc. 10475 Crosspoint Boulevard Indianapolis, IN 46256 www.wiley.com Copyright © 2011 by Steve Parker, Manchester, England Published by John Wiley & Sons, Inc., Indianapolis, Indiana Published simultaneously in Canada ISBN: 978-0-470-02448-5 ISBN: 978-1-118-16633-8 (ebk) ISBN: 978-1-118-16632-1
    [Show full text]
  • Open Source Compliance in the Enterprise
    OPEN SOURCE COMPLIANCE IN THE ENTERPRISE Sponsored by for the Open Compliance Summit 2018 IBRAHIM HADDAD, PHD WITH CONTRIBUTIONS FROM SHANE COUGHLAN AND KATE STEWART OPEN SOURCE COMPLIANCE IN THE ENTERPRISE 2nd Edition Ibrahim Haddad, PhD With contributions from Shane Coughlan and Kate Stewart Ibrahim Haddad, PhD Open Source Compliance in the Enterprise 2nd Edition Copyright © 2018 The Linux Foundation. All rights reserved. This book or any portion thereof may not be reproduced or used in any manner whatsoever without the express written permission of the publisher except for the use of brief quotations in a book review and certain other noncommercial uses permitted by copyright law. Printed in the United States of America First Edition, 2016 Second Edition, 2018 1 Letterman Drive Building D Suite D4700 San Francisco CA 94129 Open Source Compliance in the Enterprise Contents Chapter 1 16 INTRODUCTION TO OPEN SOURCE COMPLIANCE 16 A CHANGING BUSINESS ENVIRONMENT 16 ENTER OPEN SOURCE COMPLIANCE 19 Benefits of Ensuring Open Source Compliance 20 FAILURE TO COMPLY 20 Intellectual Property Failures 22 License Compliance Problems 24 Process Failures 26 LESSONS LEARNED 27 Ensure Compliance Prior to Product Shipment/Service Launch 27 Non-Compliance is Expensive 28 Relationships Matter 29 Training is Important 29 Chapter 2 30 ESTABLISHING AN OPEN SOURCE MANAGEMENT PROGRAM 30 OPEN SOURCE COMPLIANCE PROGRAM 30 Compliance Strategy 31 Inquiry Response Strategy 32 Policies and Processes 32 Compliance Teams 33 Tools 34 Web Presence 35 Education 36 Automation
    [Show full text]