DOCSLIB.ORG

Conference Reports

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Conference Reports structure. Novell does this by pro- viding complementary packages (open or closed) that interact with those developed by the open source community. By focusing on com- USENIX ANNUAL plementing existing projects, rather than providing substitutes, they conference TECHNICAL avoid competing with open source developers, an arrangement that reports CONFERENCE benefits all involved. (USENIX ’04) At Novell, this has required reworking the legal framework Boston, Massachusetts This issue’s reports under which licenses are sold, June 27–July 2, 2004 focus on the USENIX expending significant effort in con- Annual Technical vincing customers to accept solu- Conference (USENIX PLENARY SESSION tions combining proprietary and ’04), held in Boston, open components, and changing Massachusetts, Summarized by Richard S. Cox the focus of the organization. June 27–July 2, 2004. Open Source and Proprietary Soft- Greg Mitchell asked how the soci- Our thanks to the ware: A Blending of Cultures ology of the company changed as scribe coordinator: Alan Nugent, Novell more open source developers were Alan Nugent opened the USENIX brought in. Alan responded that, Rik Farrow Annual Technical Conference with while some employees were upset Our thanks to the his plenary session addressing the and a few even left, the acquisition summarizers: integration of open source software of open source teams has been very and procedures at Novell. successful and brought more Bill Bogstad energy throughout the company. Many people believe that open Novell was able to do very well Ming Chow source will destroy the software retaining employees from acquired industry; that it is developed by Brian Cornell companies. hackers without discipline; that it Richard S. Cox is a fad; or that there is no money in open source. Seeking to debunk GENERAL SESSION PAPERS: Todd Deshane these myths, Alan first suggested INSTRUMENTATION AND Patty Jablonski that, rather than wrecking the DEBUGGINGOOOOOO O industry, open source has increased Rob Martin Summarized by Swaroop Sridhar diversity and thus has created Martin Michlmay opportunities. Second, open source Making the “Box” Transparent: software can be of very high quality, System Call Performance as a Adam S. Moskowitz since a majority of open source First-Class Result Peter Nilsson contributors are professional devel- Yaoping Ruan and Vivek Pai, Prince- opers working on projects that G. Jason Peng ton University interest them. The community is Mr. Yaoping Ruan presented the Calicrates Policroniades growing daily, and contributors are “DeBox”ing technique for debug- quick to realize important initia- David Reveman ging OS-intensive applications. He tives. While open source software is began the talk with a motivating Matt Salter free, there is a market for selling example of monitoring system call the support and maintenance con- Swaroop Sridhar performance on a server running tracts that large customers require the SpecWeb99 benchmark. He Sudarshan Srinivasan before they are willing to build pointed out that system call profile mission-critical systems using a Matus Telgarsky as measured from user space some- package. Wanghong Yuan times indicated anomalous kernel The adoption of open source has behavior. He identified the trade-off Ningning Zhu allowed Novell to work with cus- between speed, completeness, and tomers to build solutions that more accuracy among various profiling closely match their needs and infra- tools. Later, Ruan presented the ;LOGIN: OCTOBER 2004 USENIX ’04 ANNUAL TECHNICAL CONFERENCE 41 design of the DeBox system. The that for a tool to be used in produc- question, Cantrill said that there key idea is to make the system call tion, the necessary constraints are was no extra effort required to use performance a first-class result and that there should be zero probe this tool with third-party kernel- return it in-band (like errno). effect when disabled, and the sys- level modules. When asked Proposing a split between the tem must be absolutely safe. To whether there were any plans to measurement policy and mecha- have systemic scope, both kernel port their system to Linux or any nism, Ruan said that the applica- and applications must be instru- other operating system, Cantrill tions should be able to interactively mentable, and the system must be answered in the negative and profile interesting events. able to prune and coalesce the quipped, “Use the best OS avail- Later, Ruan gave details about the enormous amount of data into use- able!” The authors can be con- implementation of DeBox. He gave ful information. tacted at [email protected]. the details of profiling primitives Later, Cantrill introduced the vari- sum.com. added to the kernel and the inter- ous concepts and features of Flashback: A Lightweight Exten- face available to the applications. DTrace: dynamic-only instrumenta- sion for Rollback and Determinis- He also provided details about the tion, unified instrumentation, arbi- tic Replay for Software Debugging various kinds of information that trary context kernel instrumenta- Sudarshan M. Srinivasan, Srikanth the system offered, the amount of tion, high-level control language, Kandula, Christopher R. Andrews, change that had to be done to the predicate and arbitrary action spec- and Yuanyuan Zhou, University of kernel and applications, and so on. ification, data-integrity constraints, Illinois, Urbana-Champaign Ruan went on to present a case facility for user-defined variables, study on Flash Web server per- data aggregation, speculative trac- With the increase in volume and formance. He presented various ing, scripting capacity, boot-time complexity of software develop- optimizations with a step-by-step tracing, virtualized consumers, etc. ment, there is a proportional performance analysis. Next, Cantrill elaborated on the D increase in software bugs, their language: syntax and use, D inter- effects, and the difficulty in tracing Ruan concluded by stating that or even reproducing them. Various DeBox is very effective on OS- mediate form, probes, providers and actions, aggregations and scala- checkpointing and logging mecha- intensive applications and complex nisms and their applications have workloads. He also claimed that the bility of the architecture. Cantrill also shared some experiences with received a lot of research attention results showed that the system was in the last decade. Mr. Sudarshan portable. During the Q&A session, DTrace and gave some examples of D scripts and analyzed their results. Srinivasan presented Flashback, a Ruan said that they were investigat- lightweight OS extension to facili- ing the use of DeBox on other OS- Finally, using the example of a bug in gtik2 applet2—a stock ticker for tate rollback and replay, as applied intensive applications such as data- to software debugging. base systems, but the results were GNOME desktop—he showed how not yet available. More information a small programmer error could After providing a brief general about DeBox can be found at cause widespread damage in a pro- background and motivation for http://www.cs.princeton.edu/~yruan/ duction system such as SunRay lightweight checkpointing, Srini- debox, or by contacting {yruan, server. Cantrill challenged the idea vasan went straight into the main vivek}@cs.princeton.edu. that no other existing tool could idea of Flashback. Flashback trace this problem to its root cause, achieves checkpointing by forking Dynamic Instrumentation of Pro- and that a trace was possible only a shadow process, thus replicating duction Systems by the extensive use of aggregation the in-memory state of the process. Bryan M. Cantrill, Michael W. functions and thread local variables The processes’ interactions with the Shapiro, and Adam H. Leventhal, Sun provided by DTrace. system are logged so that, during Microsystems During the Q&A session, Jonathan replay from a checkpoint, the In introducing Bryan Cantrill, ses- Shapiro said that he believed that (shadow) process gets an execution sion chair Val Henson—also from the gtik2 applet2 problem should environment similar to the original Sun Microsystems—said that she be attributed to the fundamental run. Srinivasan presented some could definitely confirm Sun’s use problems in monolithic kernel challenges posed due to multi- of DTrace in production. Cantrill design, and asked the speaker to threading, memory-mapped files, began his power-packed speech by comment on the use of DTrace for and shared memory and signals. He stating that all of today’s tools were debugging kernel bugs. Cantrill did also presented the approaches targeted at development and not not totally agree with Shapiro’s adopted in Flashback toward production. As a result, the systems views, but only asserted that solving these problems. are incapable of dealing with sys- DTrace was effective in tracing ker- Srinivasan went on to present some temic problems. Cantrill asserted nel-level bugs. Answering another details of the present Linux imple- 42 ;LOGIN: VOL. 29, NO. 5 mentation regarding modifications gent Orchestrator for Service Opti- ule.” Estimating individual task to the kernel, changes to GDB, etc. mization. duration is crucial, and CHAMPS Srinivasan identified incorporating uses “past deployments” to calcu- replay support for multi-threaded The CHAMPS system consists of two late future durations for individual applications as an area for future subcomponents: the Task Graph Builder tasks. work. Later, responding to Val Hen- and the Planner and Scheduler. The end Multiple task graphs, each repre- son’s question
Load more

Recommended publications
  • R&S®BBA100 Broadband Amplifier Open
    R&S®BBA100 Broadband Amplifier Open Source Acknowledgment 5353.8300.00 – 01 /RL/1/EN 01.00 / Broadcasting 3575.4620.02 M: - T - PAD Open Source Acknowledgment R&S BBA100 Introduction Contents 1 Introduction ......................................................................................... 3 1.1 Disclaimer ..................................................................................................................... 3 1.2 How to obtain the source code .................................................................................. 3 2 Software packages ............................................................................. 4 3 Verbatim license texts ........................................................................ 7 3.1 Apache License 2.0 ..................................................................................................... 7 3.2 GNU Library General Public License, Version 2.0 (LGPL 2.0) ..............................10 3.3 Boost Software License ............................................................................................18 3.4 GNU General Public License, Version 2.0 (GPL 2.0) ..............................................18 3.5 GNU Lesser General Public License, Version 2.1 (LGPL 2.1) ...............................24 3.6 Mozilla Public License, Version 1.1 (MPL 1.1) ........................................................32 3.7 MIT ...............................................................................................................................40 3.8 JDOM License
    [Show full text]
  • A Political History of X Or How I Stopped Worrying and Learned to Love the GPL
    A Political History of X or How I Stopped Worrying and Learned to Love the GPL Keith Packard SiFive [email protected] Unix in !"# ● $SD Everywhere – $'t not actually BS% ● )*+* want, to make Sy,tem V real – S'rely they still matter ● .o Free So/tware Anywhere The 0rigins of 1 ● $rian Reid and Pa'l Asente at Stan/ord – - kernel → VGTS → W window system – Ported to VS100 at Stan/ord ● $o4 Scheifler started hacking W→ X – Working on Argus with Barbara Liskov at LCS – 7ade it more Unix friendly (async9, renamed X -AXstation 00 (aka v, 339 Unix Workstation Market ● Unix wa, closed source ● Most vendors ,hipped a proprietary 0S 4ased on $SD #.x ● S'n: HP: Digita(: )po((o: *ektronix: I$7 ● ;congratu(ation,: yo'<re not running &'nice=. – Stil(: so many gratuito', di/ference, -AXstation II S'n >?@3 Early Unix Window Systems ● S'n-iew dominated (act'al commercial app,A De,ktop widget,A9 ● %igital had -WS/UIS (V7S on(y9 ● )pollo had %omain ● *ektronix demon,trating Sma((*alk 1 B1@ ● .onB/ree so/tware ● U,ed internally at MIT ● Shared with friend, in/ormally 1 3 ● )(mo,t u,able ● %elivered by Digital on V)1,tation, ● %i,trib'tion was not all free ,o/tware – Sun port relied on Sun-iew kernel API – %igital provided binary rendering code – IB7 PC?2T support act'ally complete (C9 Why 1 C ● 1 0 had wart, – rendering model was pretty terrible ● ,adly, X1 wa,n't m'ch better... – External window management witho't borders ● Get everyone involved – Well, at lea,t every workstation vendor willing to write big checks X as Corporate *ool ● Dim Gettys and Smokey
    [Show full text]
  • Herramientas En GNU/Linux Para Estudiantes Universitarios
    Herramientas en GNU/Linux para estudiantes universitarios El Escritorio KDE David Vaquero Santiago Herramientas en GNU/Linux para estudiantes universitarios: El Escritorio KDE por David Vaquero Santiago Copyright (c) 2.003 David Vaquero Santiago Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License". Tabla de contenidos 1. El Escritorio KDE..............................................................................................................................................1 1.1. La Historia de KDE.................................................................................................................................1 1.2. .................................................................................................................................................................1 2. ..............................................................................................................................................................................3 2.1. El escritorio KDE....................................................................................................................................3 3. Konqueror: La herramienta polivalente..........................................................................................................8
    [Show full text]
  • The Design and Implementation of Multiprocessor Support for an Industrial Operating System Kernel
    Blekinge Institute of Technology Research Report 2005:06 The Design and Implementation of Multiprocessor Support for an Industrial Operating System Kernel Simon Kågström Håkan Grahn Lars Lundberg Department of Systems and Software School of Engineering Blekinge Institute of Technology The Design and Implementation of Multiprocessor Support for an Industrial Operating System Kernel Simon Kågström, Håkan Grahn, and Lars Lundberg Department of Systems and Software Engineering School of Engineering Blekinge Institute of Technology P.O. Box 520, SE-372 25 Ronneby, Sweden {ska, hgr, llu}@bth.se Abstract The ongoing transition from uniprocessor to multiprocessor computers requires support from the op- erating system kernel. Although many general-purpose multiprocessor operating systems exist, there is a large number of specialized operating systems which require porting in order to work on multipro- cessors. In this paper we describe the multiprocessor port of a cluster operating system kernel from a producer of industrial systems. Our initial implementation uses a giant locking scheme that serializes kernel execution. We also employed a method in which CPU-local variables are placed in a special sec- tion mapped to per-CPU physical memory pages. The giant lock and CPU-local section allowed us to implement an initial working version with only minor changes to the original code, although the giant lock and kernel-bound applications limit the performance of our multiprocessor port. Finally, we also discuss experiences from the implementation. 1 Introduction A current trend in the computer industry is the transition from uniprocessors to various kinds of multipro- cessors, also for desktop and embeddedsystems. Apart from traditional SMP systems, many manufacturers are now presenting chip multiprocessors or simultaneous multithreaded CPUs [9, 15, 16] which allow more efficient use of chip area.
    [Show full text]
  • Implementation of Proactive Spam Fighting Te Niques
    Implementation of Proactive Spam Fighting Teniques Masterarbeit von Martin Gräßlin Rupret-Karls-Universität Heidelberg Betreuer: Prof. Dr. Gerhard Reinelt Prof. Dr. Felix Freiling 03. März 2010 Ehrenwörtlie Erklärung I versiere, dass i diese Masterarbeit selbstständig verfasst, nur die angegebenen ellen und Hilfsmiel verwendet und die Grundsätze und Empfehlungen „Verantwortung in der Wissensa“ der Universität Heidelberg beatet habe. Ort, Datum Martin Gräßlin Abstract One of the biggest allenges in global communication is to overcome the problem of unwanted emails, commonly referred to as spam. In the last years many approaes to reduce the number of spam emails have been proposed. Most of them have in common that the end-user is still required to verify the filtering results. ese approaes are reactive: before mails can be classified as spam in a reliable way, a set of similar mails have to be received. Spam fighting has to become proactive. Unwanted mails have to be bloed before they are delivered to the end-user’s mailbox. In this thesis the implementation of two proactive spam fighting teniques is discussed. e first concept, called Mail-Shake, introduces an authentication step before a sender is allowed to send emails to a new contact. Computers are unable to authenticate themselves and so all spam messages are automatically bloed. e development of this concept is discussed in this thesis. e second concept, called Spam Templates, is motivated by the fact that spam messages are generated from a common template. If we gain access to the template we are able to identify spam messages by mating the message against the template.
    [Show full text]
  • Examining the Viability of MINIX 3 As a Consumer Operating
    Examining the Viability of MINIX 3 as a Consumer Operating System Joshua C. Loew March 17, 2016 Abstract The developers of the MINIX 3 operating system (OS) believe that a computer should work like a television set. You should be able to purchase one, turn it on, and have it work flawlessly for the next ten years [6]. MINIX 3 is a free and open-source microkernel-based operating system. MINIX 3 is still in development, but it is capable of running on x86 and ARM processor architectures. Such processors can be found in computers such as embedded systems, mobile phones, and laptop computers. As a light and simple operating system, MINIX 3 could take the place of the software that many people use every day. As of now, MINIX 3 is not particularly useful to a non-computer scientist. Most interactions with MINIX 3 are done through a command-line interface or an obsolete window manager. Moreover, its tools require some low-level experience with UNIX-like systems to use. This project will examine the viability of MINIX 3 from a performance standpoint to determine whether or not it is relevant to a non-computer scientist. Furthermore, this project attempts to measure how a microkernel-based operating system performs against a traditional monolithic kernel-based OS. 1 Contents 1 Introduction 5 2 Background and Related Work 6 3 Part I: The Frame Buffer Driver 7 3.1 Outline of Approach . 8 3.2 Hardware and Drivers . 8 3.3 Challenges and Strategy . 9 3.4 Evaluation . 10 4 Progress 10 4.1 Compilation and Installation .
    [Show full text]
  • The Flightgear Manual
    The FlightGear Manual Michael Basler, Martin Spott, Stuart Buchanan, Jon Berndt, Bernhard Buckel, Cameron Moore, Curt Olson, Dave Perry, Michael Selig, Darrell Walisser, and others The FlightGear Manual February 22, 2010 For FlightGear version 2.0.0 2 Contents 0.1 Condensed Reading.........................6 0.2 Instructions For the Truly Impatient................6 0.3 Further Reading...........................6 I Installation9 1 Want to have a free flight? Take FlightGear! 11 1.1 Yet Another Flight Simulator?................... 11 1.2 System Requirements........................ 14 1.3 Choosing A Version......................... 15 1.4 Flight Dynamics Models...................... 16 1.5 About This Guide.......................... 16 2 Preflight: Installing FlightGear 19 2.1 Installing scenery.......................... 19 2.1.1 MS Windows Vista/7.................... 20 2.1.2 Mac OS X......................... 20 2.1.3 FG_SCENERY....................... 20 2.1.4 Fetch Scenery as you fly.................. 21 2.1.5 Creating your own Scenery................. 22 2.2 Installing aircraft.......................... 22 2.3 Installing documentation...................... 22 II Flying with FlightGear 25 3 Takeoff: How to start the program 27 3.1 Environment Variables....................... 27 3.1.1 FG_ROOT......................... 27 3.1.2 FG_SCENERY....................... 27 3.1.3 Environment Variables on Windows and Mac OS X.... 27 3.2 Launching the simulator under Unix/Linux............ 28 3.3 Launching the simulator under Windows.............. 29 3.3.1 Launching from the command line............. 30 3 4 CONTENTS 3.4 Launching the simulator under Mac OS X............. 30 3.4.1 Selecting an aircraft and an airport............. 31 3.4.2 Enabling on-the-fly scenery downloading......... 31 3.4.3 Enabling Navigation Map (Atlas)............
    [Show full text]
  • Microkernels in a Bit More Depth • Early Operating Systems Had Very Little Structure • a Strictly Layered Approach Was Promoted by Dijkstra
    Motivation Microkernels In a Bit More Depth Early operating systems had very little structure A strictly layered approach was promoted by Dijkstra THE Operating System [Dij68] COMP9242 2007/S2 Week 4 Later OS (more or less) followed that approach (e.g., Unix). UNSW Such systems are known as monolithic kernels COMP9242 07S2 W04 1 Microkernels COMP9242 07S2 W04 2 Microkernels Issues of Monolithic Kernels Evolution of the Linux Kernel E Advantages: Kernel has access to everything: all optimisations possible all techniques/mechanisms/concepts implementable Kernel can be extended by adding more code, e.g. for: new services support for new harwdare Problems: Widening range of services and applications OS bigger, more complex, slower, more error prone. Need to support same OS on different hardware. Like to support various OS environments. Distribution impossible to provide all services from same (local) kernel. COMP9242 07S2 W04 3 Microkernels COMP9242 07S2 W04 4 Microkernels Approaches to Tackling Complexity Evolution of the Linux Kernel Part 2 A Classical software-engineering approach: modularity Software-engineering study of Linux kernel [SJW+02]: (relatively) small, mostly self-contained components well-defined interfaces between them Looked at size and interdependencies of kernel "modules" enforcement of interfaces "common coupling": interdependency via global variables containment of faults to few modules Analysed development over time (linearised version number) Doesn't work with monolithic kernels: Result 1:
    [Show full text]
  • Filesystem Performance on Freebsd
    Filesystem Performance on FreeBSD Kris Kennaway [email protected] BSDCan 2006, Ottawa, May 12 Introduction ● Filesystem performance has many aspects ● No single metric for quantifying it ● I will focus on aspects that are relevant for my workloads (concurrent package building) ● The main relevant filesystem workloads seem to be – Concurrent tarball extraction – Recursive filesystem traversals ● Aim: determine relative performance of FreeBSD 4.x, 5.x and 6.x on these workloads – Overall performance and SMP scaling – Evaluate results of multi-year kernel locking strategy as it relates to these workloads Outline ● SMP architectural differences between 4/5/6.x ● Test methodology ● Hardware used ● Parallel tarball extraction test – Disk array and memory disk ● Scaling beyond 4 CPUs ● Recursive filesystem traversal test ● Conclusions & future work SMP Architectural Overview ● FreeBSD 4.x; rudimentary SMP support – Giant kernel lock restricts kernel access to one process at a time – SPL model; interrupts may still be processed in parallel ● FreeBSD 5.x; aim towards greater scalability – Giant-locked to begin with; then finer-grained locking pushdown ● FreeBSD 5.3; VM Giant-free ● FreeBSD 5.4; network stack Giant-free (mostly) ● Many other subsystems/drivers also locked – Interrupts as kernel threads; compete for common locks (if any) with everything else ● FreeBSD 6.x; – Consolidation; further pushdown; payoff! – VFS subsystem, UFS filesystem Giant-free FreeBSD versions ● FreeBSD 4.11-STABLE (11/2005) – Needed for amr driver fixes after 4.11-RELEASE ● FreeBSD 5.4-STABLE (11/05) – No patches needed ● FreeBSD 6.0-STABLE (11/05) – patches: ● Locking reworked in amr driver by Scott Long for better performance ● All relevant changes merged into FreeBSD 6.1 – A kernel panic was encountered at very high I/O loads ● Also fixed in 6.1 Test aims and Methodology ● Want to measure – overall performance difference between FreeBSD branches under varying (concurrent process I/O) loads – scaling to multiple CPUs ● Avoid saturating hardware resources (e.g.
    [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]
  • Australian Open Source Industry & Community Report 2008
    The Australian Open Source Industry & Community Report 2008 Sponsors & Industry Community Map of Education & Supporters Respondents Skills 5 9 11 12 15 Careers & Innovation The Market Business Opinion Employment Development 17 19 19 21 23 Methodology. The Australian Open Source Industry & Community Report was Promotion commissioned and executed by Waugh Partners, with the financial support of sponsors, NICTA, IBM and Fujitsu. The Census was directly promoted through a national roadshow which traveled to every capital city, on several mailing lists including Linux We worked closely with psychometricians and statisticians provided by Australia, Open Source Industry Australia and user groups around the NICTA, our primary research partner, to ensure the end-to-end quality country, and through direct contact with Open Source community of the research. While our sponsors and supporters provided feedback members and companies. Indirect promotion included blogging, media at numerous points throughout the project lifecycle, this report is the coverage, and notification to members of the Australia Computer result of independent analysis by Waugh Partners. It is based on data Society, AIIA, OzZope and numerous other organisations. collected through a pair of online surveys held between October and December 2007. Projections Community We have been very careful to make conservative projections, particularly related to industry revenue. The community survey was aimed at “individuals who contribute to Open Source projects and communities in any capacity, not just Our projected industry and export revenue figures are based upon software development”, and received 315 complete and legitimate the projected industry size and spread of companies compared to the responses, with 66 incomplete.
    [Show full text]
  • Apg Zope-Plone3 Zope-Externaleditor 0. Poppler-Utils 0. Apache2.2
    deluge-core libmagickcore2 libecpg6 libcvaux-dev libcairo-perl 0.655021834061 0. 0. libisc50 libfindlib-ocaml-dev 0. libparrot1.4.0 libjaxp1.3-java-gcj 0. 0. libgssrpc4 peercast 0. gcj-4.4-jre 0. libxfconf-0-2 0. 0. 0. libbind9-50 deluge-common 0. 0. liblqr-1-0 libecpg-compat3 0. libcv-dev libavahi-common-data libgtk2-perl 0. 1.03092783505 1.5873015873 0. 0. libasm0 2.94117647059 2.40963855422 libacl1 coreutils 0.0842023447114 0. 0.655021834061 0. 0. libplasma-ruby1.8 0. 0. 0. 0. 2.38095238095 libxalan2-java-gcj 0. 0. 0. 0. libfindlib-ocaml 0. librevm0 python-poker-engine 0. peercast-geekast 1.03092783505 0. libxfcegui4-4 0.1941370607650.278515447892 0. libisccc50 0. 0.0971754340503 libparrot-dev parrot 0.0226346763241 0. 0. geoip-database 0. libhighgui-dev 0. libmagickwand2 libpango-perl libpgtypes3 0. gcj-4.4-jdk libgcj10-awt 2.94117647059 libkdb5-4 libkadm5srv6 0. 0. 0. 0. 0.01295672454 libasn1-8-heimdal 0.340676811265 kamera python 1.61290322581 libpoconet8-dbg python-alsaaudio 0. 0. libedfmt0 0. 0. step 1.3314094576 0. 0. libxerces2-java-gcj 0. 0. xfconf ocaml-findlib 3.79746835443 dpkg libattr1 0. peercast-servent 3.75283079909 0. libplasma-ruby gnustep-base-runtime 0.2915263021511.24614678297 libdns50 0. 0. 3.79746835443 apg python-poker-network 0. libdigest-bubblebabble-perl 0. libloader-java-openoffice.org libhx509-4-heimdal libavahi-client3 libavahi-common3 0. libdb4.5 0. libcrypt-openssl-dsa-perl libpococrypto8-dbg 0.3179650238473.05646290247 0. 0. 0. 0. 1.23302944842 2.63157894737 0. kcolorchooser libisccfg50 0. libetrace0 libgcj10-dev 0. marble libkrb5-dev 1.52816947596 parrot-minimal 0.
    [Show full text]