DOCSLIB.ORG

Uncorrected Proof

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

JSS 8229 No. of Pages 12, Model 5G ARTICLE IN PRESS 20 November 2008 Disk Used The Journal of Systems and Software xxx (2008) xxx–xxx 1 Contents lists available at ScienceDirect The Journal of Systems and Software journal homepage: www.elsevier.com/locate/jss 2 Identifying exogenous drivers and evolutionary stages in FLOSS projects 3 Karl Beecher *, Andrea Capiluppi, Cornelia Boldyreff 4 Q1 Centre of Research on Open Source Software – CROSS, Department of Computing and Informatics, University of Lincoln, UK 5 article info abstract 187 8 Article history: The success of a Free/Libre/Open Source Software (FLOSS) project has been evaluated in the past through 19 9 Received 11 January 2008 the number of commits made to its configuration management system, number of developers and num- 20 10 Received in revised form 22 October 2008 ber of users. Most studies, based on a popular FLOSS repository (SourceForge), have concluded that the 21 11 Accepted 24 October 2008 vast majority of projects are failures. 22 12 Available online xxxx This study’s empirical results confirm and expand conclusions from an earlier and more limited work. 23 Not only do projects from different repositories display different process and product characteristics, but 24 13 Keywords: PROOF a more general pattern can be observed. Projects may be considered as early inceptors in highly visible 25 14 Open source software repositories, or as established projects within desktop-wide projects, or finally as structured parts of 26 15 Software evolution 16 Software repositories FLOSS distributions. These three possibilities are formalized into a framework of transitions between 27 17 repositories. 28 The framework developed here provides a wider context in which results from FLOSS repository mining 29 can be more effectively presented. Researchers can draw different conclusions based on the overall char- 30 acteristics studied about an Open Source software project’s potential for success, depending on the repos- 31 itory that they mine. These results also provide guidance to OSS developers when choosing where to host 32 their project and how to distribute it to maximize its evolutionary success. 33 Ó 2008 Published by Elsevier Inc. 34 35 36 37 1. Introduction cluded that the majority of projects housed there should be 59 considered ‘‘tragedies” by virtue of their failure to initiate a steady 60 38 The environment in which software is deployed is known to series of releases (English and Schweik, 2007). 61 39 have a direct effect on its subsequent evolution. Lehman’s first The general success of open source software projects has 62 40 law of software evolution anticipates that useful real-world soft- accompanied the wider establishment of organized repositories 63 41 ware systems (i.e., E-type) must undergo continuing change in aiming to facilitate their development and management. In a pre- 64 42 response to various requirements, in other words they must evolve vious work Beecher (XXXX) the authors examined a collection of 65 43 (Lehman et al., 1997). The LAMP stack (Linux, Apache, MySQL, Perl/ open source projects, and studied instead the exogenous drivers 66 44 PHP/Python), the Mozilla Foundation and the BSDs family are well- acting upon them and established to what extent the repositories 67 45 known examples of open source E-type software systems, and as in which a project is located affects its evolutionary characteristics. 68 46 such are no exception to this rule. By comparing equally sized random samples from two open source 69 47 The successful evolution of such open source software projects repositories and also tracking the evolution of projects that moved 70 48 has been made possible (among other factors) also by their attrac- between them, this earlier study concluded that a repository typi- 71 49 tion of large communities of both users and developers, two cate- cally has statistically significant effects upon characteristics such 72 50 gories that notably are not mutually exclusive in open source as the number of contributing developers as well as the period 73 51 software. Users initiate the need for change and the developers and amount of development activity. 74 52 implement it (Mockus et al., 2002). The extent to which an open This work extends and expands the previous study in two ways. 75 53 source project is successful hasUNCORRECTED often been evaluated empirically First, it encompasses a greater number of repositories; instead of 76 54 by measuring endogenous characteristics, such as the amount of the original two, this paper formulates hypotheses and gathers 77 55 developer activity, the number of developers, or the size of the pro- empirical evidence from data extracted from six different FLOSS 78 56 ject (Crowston et al., 2006; Godfrey and Tu, 2000; Robles et al., repositories, and provides further empirical evidence for the earlier 79 57 2003). As an example, a thorough study of Sourceforge.net (a pop- assertions. By making multiple comparisons between them, a 80 58 ular repository of more than 200,000 open source projects) con- structured body of knowledge has been constructed regarding 81 the key practical differences between the individual FLOSS reposi- 82 Q2 * Corresponding author. Tel.: +44 01522 886858. tories being studied. Secondly, the paper formulates a framework 83 E-mail address: [email protected] (K. Beecher). of evolution for FLOSS projects, based on the repository to which 84 0164-1212/$ - see front matter Ó 2008 Published by Elsevier Inc. doi:10.1016/j.jss.2008.10.026 Please cite this article in press as: Beecher, K. et al., Identifying exogenous drivers and evolutionary stages in FLOSS projects, J. Syst. Soft- ware (2008), doi:10.1016/j.jss.2008.10.026 JSS 8229 No. of Pages 12, Model 5G ARTICLE IN PRESS 20 November 2008 Disk Used 2 K. Beecher et al. / The Journal of Systems and Software xxx (2008) xxx–xxx 85 they belong, comprising a typical path of evolution between repos- than their SourceForge counterparts; in addition, it was found that, 148 86 itories, which exploits better process and product characteristics of within the Debian sample, these increased measures could be ob- 149 87 projects in particular repositories. served typically after the projects were included in the Debian 150 88 The paper is articulated as follows: Section 2 explores previous repository. The present study expands the previous data base and 151 89 work and shows how the findings of this paper extend and expand results by considering four other repositories (KDE, GNOME, Ruby- 152 90 upon past literature on the subject. Section 3 tailors the Goal-Ques- Forge and Savannah), extracts similar samples from each of the 153 91 tion-Metric methodology to this specific case study, and introduces resulting six repositories (50 projects each from the repository’s 154 92 the empirical hypotheses on which this study is based, the null ‘‘stable” pool), and studies four product and process characteristics 155 93 hypotheses and their alternative counterparts, and discusses how of the projects in the samples. Based on these experiments, this 156 94 they have been operationalized. It also describes which reposito- study also provides a more general framework for the evolution 157 95 ries have been selected, how the data has been extracted from of FLOSS projects. 158 96 them, and which attributes have been used to characterize their There are several tools and data sources which are used to ana- 159 97 process and product aspects. Sections 4 and 5 illustrate the results lyze FLOSS projects. FLOSSmole1 is a single point of access to data 160 98 gathered, and verifies whether the hypotheses have to be rejected. gathered from a number of FLOSS repositories (e.g., SourceForge, 161 99 Section 6 provides the discussion for the empirical findings and Freshmeat, Rubyforge). While FLOSSmole provides a simple querying 162 100 introduces the framework for the evolution of FLOSS projects along tool, its main function is to act as a source of data for others to ana- 163 101 repositories; Section 7 explores the threats to the external and lyze. CVSAnaly2 is a tool which is used to measure any analyses from 164 102 internal validity of this empirical study, while Section 8 provides large FLOSS projects (Robles et al., 2004). It is used in this paper to 165 103 the key findings of this research. determine such measures as the number of commits and developers 166 associated with a particular project. 167 104 2. Previous work 3. Empirical study definition and planning 168 105 There are two main types studies found in the FLOSS literature, 106 one termed external and the other internal to the FLOSS phenome- The Goal-Question-Metric method (GQM) Basili et al. (1994) 169 107 non (Beecher, XXXX). Based on the availability of FLOSS data, the evaluates whetherPROOF a goal has been reached by associating that goal 170 108 former has traditionally used FLOSS artefacts in order to propose with questions that explain it from an operational point of view 171 109 models (Hindle and German, 2005), test existing or new frame- and provide the basis for applying metrics to answer these ques- 172 110 works (Canfora et al., 2007; Livieri et al., 2007), or build theories tions. The aim of the method is to determine the information and 173 111 (Antoniol et al., 2001) to provide advances in software engineering. metrics needed to be able to draw conclusions on the achievement 174 112 The latter includes several other studies that have analyzed the of the goal. 175 113 FLOSS phenomenon per se (Capiluppi, 2003; German, 2004; Herraiz In this study, the GQM method is applied firstly to identify the 176 114 et al., 2008; Stamelos et al., 2002) with their results aimed at both overall goals of this research; then to formulate a number of ques- 177 115 building a theory of FLOSS, and characterizing the results and their tions related to FLOSS repositories and their exogenous (or exter- 178 116 validity specifically as inherent to this type of software and style of nal) effects on the underlying process and product characteristics 179 117 development.
Recommended publications
  • Ultumix GNU/Linux 0.0.1.7 32 Bit!

    Ultumix GNU/Linux 0.0.1.7 32 Bit!

    Welcome to Ultumix GNU/Linux 0.0.1.7 32 Bit! What is Ultumix GNU/Linux 0.0.1.7? Ultumix GNU/Linux 0.0.1.7 is a full replacement for Microsoft©s Windows and Macintosh©s Mac OS for any Intel based PC. Of course we recommend you check the system requirements first to make sure your computer meets our standards. The 64 bit version of Ultumix GNU/Linux 0.0.1.7 works faster than the 32 bit version on a 64 bit PC however the 32 bit version has support for Frets On Fire and a few other 32 bit applications that won©t run on 64 bit. We have worked hard to make sure that you can justify using 64 bit without sacrificing too much compatibility. I would say that Ultumix GNU/Linux 0.0.1.7 64 bit is compatible with 99.9% of all the GNU/Linux applications out there that will work with Ultumix GNU/Linux 0.0.1.7 32 bit. Ultumix GNU/Linux 0.0.1.7 is based on Ubuntu 8.04 but includes KDE 3.5 as the default interface and has the Mac4Lin Gnome interface for Mac users. What is Different Than Windows and Mac? You see with Microsoft©s Windows OS you have to defragment your computer, use an anti-virus, and run chkdsk or a check disk manually or automatically once every 3 months in order to maintain a normal Microsoft Windows environment. With Macintosh©s Mac OS you don©t have to worry about fragmentation but you do have to worry about some viruses and you still should do a check disk on your system every once in a while or whatever is equivalent to that in Microsoft©s Windows OS.
  • Resurrect Your Old PC

    Resurrect Your Old PC

    Resurrect your old PCs Resurrect your old PC Nostalgic for your old beige boxes? Don’t let them gather dust! Proprietary OSes force users to upgrade hardware much sooner than necessary: Neil Bothwick highlights some great ways to make your pensioned-off PCs earn their keep. ardware performance is constantly improving, and it is only natural to want the best, so we upgrade our H system from time to time and leave the old ones behind, considering them obsolete. But you don’t usually need the latest and greatest, it was only a few years ago that people were running perfectly usable systems on 500MHz CPUs and drooling over the prospect that a 1GHz CPU might actually be available quite soon. I can imagine someone writing a similar article, ten years from now, about what to do with that slow, old 4GHz eight-core system that is now gathering dust. That’s what we aim to do here, show you how you can put that old hardware to good use instead of consigning it to the scrapheap. So what are we talking about when we say older computers? The sort of spec that was popular around the turn of the century. OK, while that may be true, it does make it seem like we are talking about really old hardware. A typical entry-level machine from six or seven years ago would have had something like an 800MHz processor, Pentium 3 or similar, 128MB of RAM and a 20- 30GB hard disk. The test rig used for testing most of the software we will discuss is actually slightly lower spec, it has a 700MHz Celeron processor, because that’s what I found in the pile of computer gear I never throw away in my loft, right next to my faithful old – but non-functioning – Amiga 4000.
  • Red Hat Enterprise Linux 6 Developer Guide

    Red Hat Enterprise Linux 6 Developer Guide

    Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Dave Brolley William Cohen Roland Grunberg Aldy Hernandez Karsten Hopp Jakub Jelinek Developer Guide Jeff Johnston Benjamin Kosnik Aleksander Kurtakov Chris Moller Phil Muldoon Andrew Overholt Charley Wang Kent Sebastian Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Edition 0 Author Dave Brolley [email protected] Author William Cohen [email protected] Author Roland Grunberg [email protected] Author Aldy Hernandez [email protected] Author Karsten Hopp [email protected] Author Jakub Jelinek [email protected] Author Jeff Johnston [email protected] Author Benjamin Kosnik [email protected] Author Aleksander Kurtakov [email protected] Author Chris Moller [email protected] Author Phil Muldoon [email protected] Author Andrew Overholt [email protected] Author Charley Wang [email protected] Author Kent Sebastian [email protected] Editor Don Domingo [email protected] Editor Jacquelynn East [email protected] Copyright © 2010 Red Hat, Inc. and others. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
  • Ubuntu Kung Fu

    Ubuntu Kung Fu

    Prepared exclusively for Alison Tyler Download at Boykma.Com What readers are saying about Ubuntu Kung Fu Ubuntu Kung Fu is excellent. The tips are fun and the hope of discov- ering hidden gems makes it a worthwhile task. John Southern Former editor of Linux Magazine I enjoyed Ubuntu Kung Fu and learned some new things. I would rec- ommend this book—nice tips and a lot of fun to be had. Carthik Sharma Creator of the Ubuntu Blog (http://ubuntu.wordpress.com) Wow! There are some great tips here! I have used Ubuntu since April 2005, starting with version 5.04. I found much in this book to inspire me and to teach me, and it answered lingering questions I didn’t know I had. The book is a good resource that I will gladly recommend to both newcomers and veteran users. Matthew Helmke Administrator, Ubuntu Forums Ubuntu Kung Fu is a fantastic compendium of useful, uncommon Ubuntu knowledge. Eric Hewitt Consultant, LiveLogic, LLC Prepared exclusively for Alison Tyler Download at Boykma.Com Ubuntu Kung Fu Tips, Tricks, Hints, and Hacks Keir Thomas The Pragmatic Bookshelf Raleigh, North Carolina Dallas, Texas Prepared exclusively for Alison Tyler Download at Boykma.Com Many of the designations used by manufacturers and sellers to distinguish their prod- ucts are claimed as trademarks. Where those designations appear in this book, and The Pragmatic Programmers, LLC was aware of a trademark claim, the designations have been printed in initial capital letters or in all capitals. The Pragmatic Starter Kit, The Pragmatic Programmer, Pragmatic Programming, Pragmatic Bookshelf and the linking g device are trademarks of The Pragmatic Programmers, LLC.
  • Historical Dictionary of Sufism

    Historical Dictionary of Sufism

    04-655 (1) FM.qxd 4/18/05 12:39 PM Page i HISTORICAL DICTIONARIES OF RELIGIONS, PHILOSOPHIES, AND MOVEMENTS Jon Woronoff, Series Editor 1. Buddhism, by Charles S. Prebish, 1993 2. Mormonism, by Davis Bitton, 1994. Out of print. See No. 32. 3. Ecumenical Christianity, by Ans Joachim van der Bent, 1994 4. Terrorism, by Sean Anderson and Stephen Sloan, 1995. Out of print. See No. 41. 5. Sikhism, by W. H. McLeod, 1995 6. Feminism, by Janet K. Boles and Diane Long Hoeveler, 1995. Out of print. See No. 52. 7. Olympic Movement, by Ian Buchanan and Bill Mallon, 1995. Out of print. See No. 39. 8. Methodism, by Charles Yrigoyen Jr. and Susan E. Warrick, 1996. Out of Print. See No. 57. 9. Orthodox Church, by Michael Prokurat, Alexander Golitzin, and Michael D. Peterson, 1996 10. Organized Labor, by James C. Docherty, 1996. Out of print. See No. 50. 11. Civil Rights Movement, by Ralph E. Luker, 1997 12. Catholicism, by William J. Collinge, 1997 13. Hinduism, by Bruce M. Sullivan, 1997 14. North American Environmentalism, by Edward R. Wells and Alan M. Schwartz, 1997 15. Welfare State, by Bent Greve, 1998 16. Socialism, by James C. Docherty, 1997 17. Bahá’í Faith, by Hugh C. Adamson and Philip Hainsworth, 1998 18. Taoism, by Julian F. Pas in cooperation with Man Kam Leung, 1998 19. Judaism, by Norman Solomon, 1998 20. Green Movement, by Elim Papadakis, 1998 21. Nietzscheanism, by Carol Diethe, 1999 22. Gay Liberation Movement, by Ronald J. Hunt, 1999 23. Islamic Fundamentalist Movements in the Arab World, Iran, and Turkey, by Ahmad S.
  • Release Notes for Fedora 15

    Release Notes for Fedora 15

    Fedora 15 Release Notes Release Notes for Fedora 15 Edited by The Fedora Docs Team Copyright © 2011 Red Hat, Inc. and others. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. For guidelines on the permitted uses of the Fedora trademarks, refer to https:// fedoraproject.org/wiki/Legal:Trademark_guidelines. Linux® is the registered trademark of Linus Torvalds in the United States and other countries. Java® is a registered trademark of Oracle and/or its affiliates. XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries. All other trademarks are the property of their respective owners.
  • Family by NEIL SPEARS Requests Contributing Writer Donates VCSD Chancellor Robert C

    Family by NEIL SPEARS Requests Contributing Writer Donates VCSD Chancellor Robert C

    FEATURES Ughts & Sirens 2 SPORTS Opinion 4 Baseball swi~ away Meet the candidates Features • the competition A.S. presidential profiles 9 Features takes a look at this year's A.S. presidential candidates, Triton baseball went 4-1 over the their slates and independent campaigns - and finds out who Classifieds 12 break, beating CSU Dominguez Hills they are and what they staoo for. page 9 Campus Calendar 11 and Azusa PaCific. P~e 16 UC SAN DIEGO MONDAY, MARCH 11, 2001 VOLU,\IE 109, [ seE I 2003 A.S. ELEOIONS WATCH War advisory group formed Jacobs Appeal Committee to oversee campus climate family By NEIL SPEARS requests Contributing Writer donates VCSD Chancellor Robert C. denied Dynes announced the formation of the pecial Advisory Committee on War Related $110 M Matters on March 19. The goal Committee of me commirree is to advise the chancellor about the impact of Gift part of hears cases of global conflict on the campus community. $1 billion 3 applicants "I want to reassure you that we have developed comprehen­ By GAELLE FAURE sive plans for enhancing campu fundraising Associate News Editor safety, sustaining campus opera­ tions, and issuing timely news campalgn Three A.. elections candidates updates," Dynes stated in a who had filed appeals to the elec­ March 20 campus norice. tions committee Jskll1g to be rein­ The committee is composed By LISA MAK stated in the race were denied their of a dozen representatives from Staff Writer requests prior to the end of winter different areas of campu opera­ Irwin Jacobs. former C 'D quarter.
  • The Linux Command Line

    The Linux Command Line

    The Linux Command Line Fifth Internet Edition William Shotts A LinuxCommand.org Book Copyright ©2008-2019, William E. Shotts, Jr. This work is licensed under the Creative Commons Attribution-Noncommercial-No De- rivative Works 3.0 United States License. To view a copy of this license, visit the link above or send a letter to Creative Commons, PO Box 1866, Mountain View, CA 94042. A version of this book is also available in printed form, published by No Starch Press. Copies may be purchased wherever fine books are sold. No Starch Press also offers elec- tronic formats for popular e-readers. They can be reached at: https://www.nostarch.com. Linux® is the registered trademark of Linus Torvalds. All other trademarks belong to their respective owners. This book is part of the LinuxCommand.org project, a site for Linux education and advo- cacy devoted to helping users of legacy operating systems migrate into the future. You may contact the LinuxCommand.org project at http://linuxcommand.org. Release History Version Date Description 19.01A January 28, 2019 Fifth Internet Edition (Corrected TOC) 19.01 January 17, 2019 Fifth Internet Edition. 17.10 October 19, 2017 Fourth Internet Edition. 16.07 July 28, 2016 Third Internet Edition. 13.07 July 6, 2013 Second Internet Edition. 09.12 December 14, 2009 First Internet Edition. Table of Contents Introduction....................................................................................................xvi Why Use the Command Line?......................................................................................xvi
  • Kde-Guide-De-Developpement.Web.Pdf

    Kde-Guide-De-Developpement.Web.Pdf

    KDE Published : 2017-06-26 License : GPLv2+ 1 KDE DU POINT DE VUE D'UN DÉVELOPPEUR 1. AVEZ-VOUS BESOIN DE CE LIVRE ? 2. LA PHILOSOPHIE DE KDE 3. COMMENT OBTENIR DE L'AIDE 2 1. AVEZ-VOUS BESOIN DE CE LIVRE ? Vous devriez lire ce livre si vous voulez développer pour KDE. Nous utilisons le terme développement très largement pour couvrir tout ce qui peut conduire à un changement dans le code source, ce qui inclut : Soumettre une correction de bogue Écrire une nouvelle application optimisée par la technologie KDE Contribuer à un projet existant Ajouter de la fonctionnalité aux bibliothèques de développement de KDE Dans ce livre, nous vous livrerons les bases dont vous avez besoin pour être un développeur productif. Nous décrirons les outils que vous devrez installer, montrer comment lire la documentation (et écrire la vôtre propre, une fois que vous aurez créé la nouvelle fonctionnalité !) et comment obtenir de l'aide par d'autres moyens. Nous vous présenterons la communauté KDE, qui est essentielle pour comprendre KDE parce que nous sommes un projet « open source », libre (gratuit). Les utilisateurs finaux du logiciel n'ont PAS besoin de ce livre ! Cependant, ils pourraient le trouver intéressant pour les aider à comprendre comment les logiciels complexes et riches en fonctionnalités qu'ils utilisent ont vu le jour. 3 2. LA PHILOSOPHIE DE KDE Le succès de KDE repose sur une vue globale, que nous avons trouvée à la fois pratique et motivante. Les éléments de cette philosophie de développement comprennent : L'utilisation des outils disponibles plutôt que de ré-inventer ceux existants : beaucoup des bases dont vous avez besoin pour travailler font déjà partie de KDE, comme les bibliothèques principales ou les « Kparts », et sont tout à fait au point.
  • Native Libraries Lecture 10

    Native Libraries Lecture 10

    Native Libraries Lecture 10 Operating Systems Practical 11 January 2017 This work is licensed under the Creative Commons Attribution 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by/4.0/. OSP Native libraries, Lecture 10 1/35 Bionic SQLite SSL WebKit Surface Manager Audio Manager Media Framework OpenGL ES OSP Native libraries, Lecture 10 2/35 Outline Bionic SQLite SSL WebKit Surface Manager Audio Manager Media Framework OpenGL ES OSP Native libraries, Lecture 10 3/35 Bionic I Custom C library I Replacement for glibc I Not POSIX compliant I Goals I BSD license I Avoid GPL and LGPL in userspace I Small size I glibc is very large I High speed I Designed for low CPU frequencies OSP Native libraries, Lecture 10 4/35 Bionic vs. glibc I Bionic routines do not throw, pass and handle C++ exceptions I Support for exceptions adds a great overhead I Exceptions can be used internally in C++ code, if they do not cross the libc routine I No C++ Standard Template Library I Native code developers can use gnustl or stlport I New pthread implementation I No wchar_t and no support for LOCALE OSP Native libraries, Lecture 10 5/35 Bionic vs. glibc I A shared memory region is used for configuration I Also used by the applications through property_get() and property_set() I No openlog() or syslog() I __libc_android_log_print() used for logging I Specific malloc implementation I A hash table used for tracking allocations to discover leaks I No pty support OSP Native libraries, Lecture 10 6/35 Bionic vs.
  • Developer Guide

    Developer Guide

    Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Last Updated: 2017-10-20 Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Robert Krátký Red Hat Customer Content Services [email protected] Don Domingo Red Hat Customer Content Services Jacquelynn East Red Hat Customer Content Services Legal Notice Copyright © 2016 Red Hat, Inc. and others. This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent.
  • Milax - Opensolaris Small Livecd Distro Alexander R

    Milax - Opensolaris Small Livecd Distro Alexander R

    USE IMPROVE EVANGELIZE MilaX - OpenSolaris small LiveCD distro Alexander R. Eremin MilaX Developer USE IMPROVE EVANGELIZE Can Solaris become as small as DSL? Solaris 2 USE IMPROVE EVANGELIZE DSS 0.1 Feb 2008 CDDL v.1 MilaX 0.1, 0.1.1 Feb 2008 MilaX 0.2 Mar 2008 Milax 0.3 May 2008 June 2008 MilaX 0.3.1 MilaX 0.3.1 server 3 USE IMPROVE EVANGELIZE Last version released June 10 2008 4 USE IMPROVE EVANGELIZE MilaX LiveCD, LiveUSB USE IMPROVE EVANGELIZE Virtualizing MilaX LiveCD,LiveUSB Qemu VirtualBox VMware USE IMPROVE EVANGELIZE MilaX advantages ● Small size ● Fast boot ● Loading live image from RAM ● Booting from various storage devices ● People can try small Solaris without installing on the harddisk. ● All Solaris features: dtrace,zfs, zones,e.t.c ● Latest drivers and bugfixes ● Two versions: desktop and server USE IMPROVE EVANGELIZE When MilaX is the best choice? ● Old PC's ● Not enough RAM ● Not enough free disk space ● Fast and small server (0.3.1 server) ● Fast developing (0.3.1 server) ● Virtual testing USE IMPROVE EVANGELIZE MilaX Filesystem Ramdisk 105mb, UFS Root FS /,/lib,/dev,/devices,/var Ramdisk Swap RAM /usr (RAM < 512mb) /usr, /alex, /root, /tmp Ram > 512MB HSFS Filesystem (/usr mount) LOFI Pseudo Device /.cdrom/usr.zlib HSFS Filesystem (/.cdrom mount) MilaX Live CD USE IMPROVE EVANGELIZE Milax 0.3.1 Apps Desktop version ● Gtk-Terminal, Beaver, Netsurf, Sylpheed, Midnight Commander, emelFM, XMMS, Xpdf, VNC viewer, Rdesktop, Nmap, gFTP, gPicview, Conky, XChat, Xpad. Server version ● Apache, PHP, Samba and NFS servers, GCC, GMake, Midnight Commander, Pine, Mutt, Elinks, Lynx.