Solving package dependencies: from EDOS to Mancoosi

Mancoosi (Managing the Complexity of the Open Source Infrastructure) is an ongoing research project funded by the European Union for addressing some of the challenges related to the "upgrade problem" of interdependent software components of which Debian packages are prototypical examples. Mancoosi is the natural continuation of the EDOS project which has already contributed tools for distribution-wide quality assurance in Debian and other GNU/Linux distributions. The consortium behind the project consists of several European public and private research institutions as well as some commercial GNU/Linux distributions from Europe and South America. Debian is represented by a small group of Debian Developers who are working in the ranks of the involved universities to drive and integrate back achievements into Debian. This paper presents relevant results from EDOS in dependency management and gives an overview of the Mancoosi project and its objectives, with a particular focus on the prospective benefits for Debian

Novel Data Acquisition System for Silicon Tracking Detectors

We have developed a novel data acquisition system for measuring tracking parameters of a silicon detector in a particle beam. The system is based on a commercial Analog-to-Digital VME module and a PC Linux based Data Acquisition System. This DAQ is realized with C++ code using object-oriented techniques. Track parameters for the beam particles were reconstructed using off-line analysis code and automatic detector position alignment algorithm. The new DAQ was used to test novel Czochralski type silicon detectors. The important silicon detector parameters, including signal size distributions and signal to noise distributions, were successfully extracted from the detector under study. The efficiency of the detector was measured to be 95 %, the resolution about 10 micrometers, and the signal to noise ratio about 10.Comment: Talk from the 2003 Computing in High Energy and Nuclear Physics (CHEP03), La Jolla, Ca, USA, March 2003, 6 pages, LaTeX, 5 eps figures. PSN TUGP00

Analysis of Canon CAPT protocol for Linux printer support improvement

The following paper discusses major deficiencies found in Canon’s own proprietary Advanced Printing Technology(CAPT) driver for Linux distributions. It points out the existence of experimental, but more clean and completely opensource driver based on several previous reverse engineering attempts and poses a problem of its incompatibility with aparticular printer model (LBP3000 in this case) in question. Then it proceeds to describe the effort of analysis throughobservation of captured conversation between Canon's own proprietary driver and the printer to point out thedifferences between the inner workings of original and open source drivers. Finally, it describes the implementation of printer's support in an open source driver and concludes with the successful result of producing a driver that is able to work under modern Linux distributions and share a CAPT printer on a heterogeneous local area network

Testing a priority-based queue model with Linux command histories

We study human dynamics by analyzing Linux history files. The goodness-of-fit test shows that most of the collected datasets belong to the universality class suggested in the literature by a variable-length queueing process based on priority. In order to check the validity of this model, we design two tests based on mutual information between time intervals and a mathematical relationship known as the arcsine law. Since the previously suggested queueing process fails to pass these tests, the result suggests that the modelling of human dynamics should properly consider the statistical dependency in the temporal dimension.Comment: 17 pages, 17 figure

Bug propagation and debugging in asymmetric software structures

Software dependence networks are shown to be scale-free and asymmetric. We then study how software components are affected by the failure of one of them, and the inverse problem of locating the faulty component. Software at all levels is fragile with respect to the failure of a random single component. Locating a faulty component is easy if the failures only affect their nearest neighbors, while it is hard if the failures propagate further.Comment: 4 pages, 4 figure

How good are MatLab, Octave and Scilab for Computational Modelling?

In this article we test the accuracy of three platforms used in computational modelling: MatLab, Octave and Scilab, running on i386 architecture and three operating systems (Windows, Ubuntu and Mac OS). We submitted them to numerical tests using standard data sets and using the functions provided by each platform. A Monte Carlo study was conducted in some of the datasets in order to verify the stability of the results with respect to small departures from the original input. We propose a set of operations which include the computation of matrix determinants and eigenvalues, whose results are known. We also used data provided by NIST (National Institute of Standards and Technology), a protocol which includes the computation of basic univariate statistics (mean, standard deviation and first-lag correlation), linear regression and extremes of probability distributions. The assessment was made comparing the results computed by the platforms with certified values, that is, known results, computing the number of correct significant digits.Comment: Accepted for publication in the Computational and Applied Mathematics journa

Towards maintainer script modernization in FOSS distributions

Free and Open Source Software (FOSS) distributions are complex software systems, made of thousands packages that evolve rapidly, independently, and without centralized coordination. During packages upgrades, corner case failures can be encountered and are hard to deal with, especially when they are due to misbehaving maintainer scripts: executable code snippets used to finalize package configuration. In this paper we report a software modernization experience, the process of representing existing legacy systems in terms of models, applied to FOSS distributions. We present a process to define meta-models that enable dealing with upgrade failures and help rolling back from them, taking into account maintainer scripts. The process has been applied to widely used FOSS distributions and we report about such experiences