DOCSLIB.ORG

Understanding and Auditing the Licensing of Open Source Software Distributions

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Understanding and Auditing the Licensing of Open Source Software Distributions Understanding and Auditing the Licensing of Open Source Software Distributions Daniel M. German†, Massimiliano Di Penta‡, Julius Davies† † Dept. of Computer Science, University of Victoria, Canada ‡ Dept of Engineering, University of Sannio, Italy [email protected], [email protected], [email protected] Abstract—Free and open source software (FOSS) is often When one installs a new application/library in a Unix distributed in binary packages, sometimes part of GNU/Linux system, this is often done from what is known as a bi- operating system distributions, or part of products dis- nary package (such as RPM packages in Fedora/Redhat-like tributed/sold to users. FOSS creates great opportunities for users, developers and distributions or .deb packages in Debian-like distributions). integrators, however it is important for them to understand the Other than the various artifacts composing the applica- licensing requirements of any package they use. Determining tion/library, the package also contains metadata describing, the license of a package and assessing whether it depends among other things, (i) under what open source license the on other software with incompatible licenses is not trivial. package is distributed (which we call the declared license Although this task has been done in a labor intensive manner by software distributions, automatic tools to perform this of the binary package), and (ii) the list of other packages analysis are highly desired. required in order to successfully install and use the current This paper proposes a method to understand licensing com- package (its required packages) [2]. patibility issues in software packages, and reports an empirical From a legal point of view, modifying and redistributing study aimed at auditing licensing issues in binary packages of a FOSS package poses two important issues: the Fedora-12 GNU/Linux distribution. The objective of this study is (i) to understand how the license declared in packages 1) Can we trust the declared license of the package? i.e., is consistent with those of source code files, and (ii) to audit is that license consistent with those of the files the the licensing information of Fedora-12, highlighting cases of package contains? incompatibilities between dependent packages. The obtained results—supported by feedback received from 2) Do the dependency requirements of a binary package Fedora contributors—show that there exist many nuances in create potential legal concerns? Software with different determining the license of a binary package from its source licenses can be combined to create larger systems, but code, as well as cases of license incompatibility issues due to such combinations can increase the chance for license package dependencies. incompatibilities. Keywords: Software licenses, evolution, mining software In this paper we describe a method to help understand repositories, open source systems, empirical study. licensing issues that can arise from changing, combining, and re-distributing packages in open source distributions. I. INTRODUCTION First, we identify the license of all files contained in the The advent of free and open source software (FOSS) has source code from which the binary package is created created a large ecosystem of applications, libraries and com- (the source package). This gives us a detailed overview of ponents that are readily available for download and usage. licenses present in the source code of a package, and allows Often these applications/libraries/components are distributed us to identify possible inconsistencies with the declared together with the operating system, and this happens for the license of the binary package. Second, we combine the various distributions of the GNU/Linux operating system. dependency graph of a binary package with the declared The intellectual property of FOSS is protected by licensing licenses of its dependencies, trying to identify any license mechanisms and copyright notices that determine how an inconsistencies. open source can be used, even impacting the architecture of We have carried out a large empirical study aimed at a system [1]. analyzing licensing issues in the entire Linux-based Fedora- Dealing with issues related to open source licensing is not 12 operating system. Results indicated the presence of trivial, as at the time of writing there are 65 open source some inconsistencies between the declared licenses and the licenses approved by the Open Source Initiative, and many source code ones, as well as problems arising because more in use; each of them imposing particular constraints of dependencies between different packages. For many of concerning how one can use and/or change a software. these potential problems, we contacted Fedora people or the License auditing is usually a manual analysis (assisted by package maintainers, obtaining clarifications and feedback custom scripts) performed by GNU/Linux distributions (such about the problems we pointed out, as reported in the paper. as Debian, OpenSuse, RedHat, and Ubuntu). In many cases, either Fedora or the package maintainers made changes to address such issues. work the finding about licensing change, in fact this is one The main contribution of this paper is a better understand- of the reasons for misalignment between licenses declared ing of how auditing of licenses happens in a large ecology of in the packages and licenses in source code files. packages that use many different licenses. This information There have been some attempts towards the creation is valuable towards the creation of computer support to assist of automatic environments for the verification of software legal auditors in their day-to-day work. licenses [6], [7]. In both cases, they take a simple approach: The paper is organized as follows. After a discussion packages are licensed under a single, well defined license, of related work in Section II, Section III details some of and the dependency data is used to identify potential vi- the problems that can arise when combining open source olations. Alspaugh et al. [7] propose a requirement-based software distributed under different licenses. Section IV approach: the objective is to determine any restrictions describes the proposed method to audit open source distri- in the way components are integrated into a system be- butions for license compatibility issues. Section V describes fore this is built. Instead, Tuunanen et al. [6] propose a the empirical study we carried out on Fedora-12. Results more comprehensive approach: their environment identifies are presented and discussed in Section VI, while Section licenses from source code, uses compiling information to VII discusses the threats to validity. Finally, Section VIII determine if two components are connected to find potential concludes the paper and outlines directions for future work. violations. In both cases the approach has been evaluated against small applications composed of few components, II. RELATED WORK and they do not deal with the complexities of a large Linux This section describes related work concerning (i) the distribution containing more than 10,000 binary applications analysis and understanding of legal issues in software sys- and hundreds of thousands of source code files (we found tems, and (ii) the analysis of software distributions. 327,286 source code files in Fedora-12). In recent years legal issues and problems concerned with Although specific on issues related to software licens- intellectual property have triggered a series of research ing, this is not the first study aimed at analyzing en- works. Licenses impose constraints and thus can be defined tire GNU/Linux distributions. Robles et al. [8] and then as logical formulae constraining what can and cannot be Gonzalez-Barahona´ et al. [9] related the evolution of soft- done with a system. Software licensing patterns have been ware distributions with the evolution of single applications, recently studied by German et al. [1] using such a formal- finding that the former influences the latter. German et ization of licenses. They introduced several legal patterns, al. [2] proposed a method to analyze build dependencies along with examples of occurrences of these patterns. As in software distributions, and used it to analyze the Debian German et al. [1] did, we also consider constraints imposed GNU/Linux distribution. They showed how the retrieved by open source licenses and, in particular, we rely on inter-dependencies helped to understand how packages are these constraints to mine inconsistencies (i) between licenses used and variants in which the package can be installed. declared in the packages and source code licenses, and (ii) Similarly to this work, they used package descriptions to incompatibilities due to dependencies between packages and analyze dependencies—although their study was done on libraries having different licenses. Debian packages, while our study focuses on RPM packages. German et al. [3], presented a study of the influence of Stemming from that idea, we propose to integrate package software licenses on code migration between the FreeBSD, dependency information with license information to identify Linux, and OpenBSD kernels. Their findings support the potential cases of re-distribution with license incompatibili- hypothesis of a preferential code flow induced by permis- ties. sive licenses from FreeBSD and OpenBSD towards Linux. Hindle et al. [4] discovered that many of the largest commits III. CHALLENGES OF COMBINING OPEN SOURCE correspond to changes to the licenses
Load more

Recommended publications
  • SUSE® Linux Enterprise Desktop 12 and the Workstation Extension: What's New ?
    SUSE® Linux Enterprise Desktop 12 and the Workstation Extension: What's New ? Frédéric Crozat <[email protected]> Enterprise Desktop Release Manager Scott Reeves <[email protected]> Enterprise Desktop Development Manager Agenda • Design Criteria • Desktop Environment in SUSE Linux Enterprise 12 • GNOME Shell • Desktop Features and Applications 2 Design Criteria SUSE Linux Enterprise Desktop Interoperability Ease of Use Security Ease of Management Lower Costs 4 SUSE Linux Enterprise Desktop 12 • Focus on technical workstation ‒ Developers and System administrators • One tool for the job • Main desktop applications will be shipped: ‒ Mail client, Office Suite, Graphical Editors, ... • SUSE Linux Enterprise Workstation Extension ‒ Extend SUSE Linux Enterprise Server with packages only available on SUSE Linux Enterprise Desktop. (x86-64 only) 5 Desktop in SUSE Linux Enterprise 12 As Part of the Common Code Base SUSE Linux Enterprise 12 Desktop Environment • SUSE Linux Enterprise 12 contains one primary desktop environment • Additional light-weight environment for special use-cases: ‒ Integrated Systems • Desktop environment is shared between the server and desktop products 7 SUSE Linux Enterprise 12 Desktop Environment • GNOME 3 is the main desktop environment ‒ SLE Classic mode by default ‒ GNOME 3 Classic Mode and GNOME 3 Shell Mode also available • SUSE Linux Enterprise 12 ships also lightweight IceWM ‒ Targeted at Integrated Systems • QT fully supported: ‒ QT5 supported for entire SLE12 lifecycle ‒ QT4 supported, will be removed in future
    [Show full text]
  • Speech Recognition Systems: a Comparative Review
    IOSR Journal of Computer Engineering (IOSR-JCE) e-ISSN: 2278-0661,p-ISSN: 2278-8727, Volume 19, Issue 5, Ver. IV (Sep.- Oct. 2017), PP 71-79 www.iosrjournals.org Speech Recognition Systems: A Comparative Review Rami Matarneh1, Svitlana Maksymova2, Vyacheslav V. Lyashenko3 , Nataliya V. Belova 3 1(Department of Computer Science, Prince Sattam Bin Abdulaziz University, Al-Kharj, Saudi Arabi) 2(Department of Computer-Integrated Technologies, Automation and Mechatronics, Kharkiv National University of RadioElectronics, Kharkiv, Ukraine) 3(Department of Informatics, Kharkiv National University of RadioElectronics, Kharkiv, Ukraine) Abstract: Creating voice control for robots is very important and difficult task. Therefore, we consider different systems of speech recognition. We divided them into two main classes: (1) open-source and (2) close-source code. As close-source software the following were selected: Dragon Mobile SDK, Google Speech Recognition API, Siri, Yandex SpeechKit and Microsoft Speech API. While the following were selected as open-source software: CMU Sphinx, Kaldi, Julius, HTK, iAtros, RWTH ASR and Simon. The comparison mainly based on accuracy, API, performance, speed in real-time, response time and compatibility. the variety of comparison axes allow us to make detailed description of the differences and similarities, which in turn enabled us to adopt a careful decision to choose the appropriate system depending on our need. Keywords: Robot, Speech recognition, Voice systems with closed source code, Voice systems with open source code --------------------------------------------------------------------------------------------------------------------------------------- Date of Submission: 13-10-2017 Date of acceptance: 27-10-2017 --------------------------------------------------------------------------------------------------------------------------------------- I. Introduction Voice control will make your application more convenient for user especially if a person works with it on the go or his hands are busy.
    [Show full text]
  • Speech-To-Text System for Phonebook Automation
    Speech-to-Text System for Phonebook Automation Thesis submitted in partial fulfillment of the requirements for the award of degree of Master of Engineering in Computer Science and Engineering Submitted By Nishant Allawadi (Roll No. 801032017) Under the supervision of: Mr. Parteek Bhatia Assistant Professor COMPUTER SCIENCE AND ENGINEERING DEPARTMENT THAPAR UNIVERSITY PATIALA – 147004 June 2012 i ii Abstract In the daily use of electronic devices, generally, the input is given by pressing keys or touching the screen. There are a lot of devices which give output in the form of speech but the way of giving input by speech is very new and it has been seen in a few of our latest devices. The speech input technology needs a Speech-to-Text system to convert input speech into its corresponding text and speech output technology needs a Text-to- Speech system to convert input text into its corresponding speech. In the work presented, a Speech-to-Text system has been developed with a Text-to- Speech module to enable speech as input as well as output. A phonebook application has also been developed to add new contacts, update previously saved contacts, delete saved contacts and call the saved contacts. This phonebook application has been integrated with Speech-to-Text system and Text-to-Speech module to convert the phonebook application into a complete speech interactive system. The first chapter, the basic introduction of the Speech-to-Text system has been presented. The second chapter discusses about the evolution of the Speech-to-Text technology along with the existing Speech-to-Text systems.
    [Show full text]
  • Remote Desktop Server: XDMCP
    SUSE® Linux Enterprise Setup and Optimization for Remote Graphical Access Frédéric Crozat <[email protected] Enterprise Desktop Release Manager Scott Reeves <[email protected] Enterprise Desktop Development Manager Agenda • Remote Desktop Methods • Demo • Other Remote Access Methods • Session monitoring and Management • Additional settings 2 Remote Desktop Server: XDMCP • Highly discouraged by SUSE ‒ Not secure: traffic is not encrypted ‒ Not adapted to modern desktops, causing huge latency • But still available 3 Remote Desktop server: VNC • Recommended protocol (security, caching) • Available through several means: ‒ Independent session with XVNC (configured through YaST Remote Administration module) ‒ Sharing existing GNOME session, through vino (GNOME Control Center / Sharing) 4 Remote Desktop Server: RDP • Microsoft protocol, always available on Windows products (both as client and server) • xrdp is providing independent graphical sessions support 5 Remote Desktop Clients • Vinagre ‒ Connect to VNC / SSH / Spice / RDP sessions • Vncviewer • Browser ‒ Java ‒ HTML5 • Security ‒ TLS support • Situations for alternative display and window managers 6 Demo Other Remote Access Methods • Connection via ssh ‒ Only for applications ‒ not full desktop ‒ Can't attach to running applications • Graphical apps in containers ‒ Can be done but not supported • Beware, X11 socket is NOT secure ‒ In the future, xdg-app and wayland will help 8 Accessing SUSE Linux Enterprise systems from Windows • For RDP: built-in • For X11: ‒ Micro Focus Reflection X 2014: ‒ Standalone X server or Domain mode (distributes workload and connectivity across multiple tiers) ‒ Xming (Free X server for Windows) ‒ Exceed ‒ Cygwin X server • For VNC: ‒ Vncviewer ‒ Libvirt Virt-viewer (TLS support) 9 Session monitoring and management • Systemd-loginctl 10 Session monitoring and management • systemd-loginctl is replacing ConsoleKit • loginctl [list-sessions]: output all sessions • loginctl session-status <session-number>: 2 - fcrozat (1000) Since: lun.
    [Show full text]
  • Multipurpose Large Vocabulary Continuous Speech Recognition Engine Julius
    Multipurpose Large Vocabulary Continuous Speech Recognition Engine Julius rev. 3.2 (2001/12/03) Copyright (c) 1997-2000 Information-Technology Promotion Agency, Japan Copyright (c) 1991-2001 Kyoto University Copyright (c) 2000-2001 Nara Institute of Science and Technology All rights reserved. Translated from the original Julius-3.2-book by Ian Lane – Kyoto University Julius Julius is a high performance continuous speech recognition software based on word N-grams. It is able to perform recognition at the sentence level with a vocabulary in the tens of thousands. Julius realizes high-speed speech recognition on a typical desktop PC. It performs at near real time and has a recognition rate of above 90% for a 20,000-word vocabulary dictation task. The best feature of the Julius system is that it is multipurpose. By recombining the pronunciation dictionary, language and acoustic models one is able to build various task specific systems. The Julius code also is open source so one should be able to recompile the system for other platforms or alter the code for one's specific needs. Platforms currently supported include Linux, Solaris and other versions of Unix, and Windows. There are two Windows versions, a Microsoft SAPI 5.0 compatible version and a Windows DLL version. This documentation relates to the Unix version of Julius. For documentation on the Windows versions see the Julius for SAPI README (CSRC CD-ROM) (Japanese), or the Julius for SAPI homepage (Kyoto University) (Japanese). 1 Contacts/Links Contacts/Links Home Page: http://winnie.kuis.kyoto-u.ac.jp/pub/julius/ (Japanese) E-mail: [email protected] Developers Original System/Unix version: Akinobu Lee ([email protected]) Windows Microsoft SAPI version: Takashi Sumiyoshi Windows (DLL version): Hideki Banno 2 System Structure and Features System Structure The structure of the Julius speech recognition system is shown in the diagram below: N-gram language models and a HMM acoustic model are used.
    [Show full text]
  • Indicators for Missing Maintainership in Collaborative Open Source Projects
    TECHNISCHE UNIVERSITÄT CAROLO-WILHELMINA ZU BRAUNSCHWEIG Studienarbeit Indicators for Missing Maintainership in Collaborative Open Source Projects Andre Klapper February 04, 2013 Institute of Software Engineering and Automotive Informatics Prof. Dr.-Ing. Ina Schaefer Supervisor: Michael Dukaczewski Affidavit Hereby I, Andre Klapper, declare that I wrote the present thesis without any assis- tance from third parties and without any sources than those indicated in the thesis itself. Braunschweig / Prague, February 04, 2013 Abstract The thesis provides an attempt to use freely accessible metadata in order to identify missing maintainership in free and open source software projects by querying various data sources and rating the gathered information. GNOME and Apache are used as case studies. License This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported (CC BY-SA 3.0) license. Keywords Maintenance, Activity, Open Source, Free Software, Metrics, Metadata, DOAP Contents List of Tablesx 1 Introduction1 1.1 Problem and Motivation.........................1 1.2 Objective.................................2 1.3 Outline...................................3 2 Theoretical Background4 2.1 Reasons for Inactivity..........................4 2.2 Problems Caused by Inactivity......................4 2.3 Ways to Pass Maintainership.......................5 3 Data Sources in Projects7 3.1 Identification and Accessibility......................7 3.2 Potential Sources and their Exploitability................7 3.2.1 Code Repositories.........................8 3.2.2 Mailing Lists...........................9 3.2.3 IRC Chat.............................9 3.2.4 Wikis............................... 10 3.2.5 Issue Tracking Systems...................... 11 3.2.6 Forums............................... 12 3.2.7 Releases.............................. 12 3.2.8 Patch Review........................... 13 3.2.9 Social Media............................ 13 3.2.10 Other Sources..........................
    [Show full text]
  • The Wavesurfer Automatic Speech Recognition Plugin
    The WaveSurfer Automatic Speech Recognition Plugin Giampiero Salvi and Niklas Vanhainen KTH, School of Computer Science and Communication, Department of Speech Music and Hearing, Stockholm, Sweden fgiampi, [email protected] Abstract This paper presents a plugin that adds automatic speech recognition (ASR) functionality to the WaveSurfer sound manipulation and visualisation program. The plugin allows the user to run continuous speech recognition on spoken utterances, or to align an already available orthographic transcription to the spoken material. The plugin is distributed as free software and is based on free resources, namely the Julius speech recognition engine and a number of freely available ASR resources for different languages. Among these are the acoustic and language models we have created for Swedish using the NST database. Keywords: Automatic Speech Recognition, Free Software, WaveSurfer 1. Introduction Automatic Speech Recognition (ASR) is becoming an im- portant part of our lives, both as a viable alternative for humans-computer interaction, but also as a tool for linguis- tics and speech research. In many cases, however, it is trou- blesome, even in the language and speech communities, to have easy access to ASR resources. On the one hand, com- mercial systems are often too expensive and not flexible enough for researchers. On the other hand, free ASR soft- ware often lacks high quality resources such as acoustic and language models for the specific languages and requires ex- pertise that linguists and speech researchers cannot afford. In this paper we describe a plugin for the popular sound manipulation and visualisation program WaveSurfer1 (Sjolander¨ and Beskow, 2000) that attempts to solve the above problems.
    [Show full text]
  • Speech Phonetization Alignment and Syllabification (SPPAS): a Tool for the Automatic Analysis of Speech Prosody Brigitte Bigi, Daniel Hirst
    SPeech Phonetization Alignment and Syllabification (SPPAS): a tool for the automatic analysis of speech prosody Brigitte Bigi, Daniel Hirst To cite this version: Brigitte Bigi, Daniel Hirst. SPeech Phonetization Alignment and Syllabification (SPPAS): a tool for the automatic analysis of speech prosody. Speech Prosody, May 2012, Shanghai, China. pp.19-22. hal-00983699 HAL Id: hal-00983699 https://hal.archives-ouvertes.fr/hal-00983699 Submitted on 25 Apr 2014 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. SPeech Phonetization Alignment and Syllabification (SPPAS): a tool for the automatic analysis of speech prosody. Brigitte Bigi, Daniel Hirst Laboratoire Parole et Langage, CNRS & Aix-Marseille Université [email protected], [email protected] Abstract length, pitch and loudness of the individual sounds which make up an utterance”. [7] SPASS, SPeech Phonetization Alignment and Syllabifi- cation, is a tool to automatically produce annotations Linguists need tools for the automatic analysis of at which include utterance, word, syllable and phoneme seg- least these three prosodic features of speech sounds. In mentations from a recorded speech sound and its tran- this paper we concentrate on the tool for the automatic scription.
    [Show full text]
  • List of Application Added in ARL #2607
    List of Application added in ARL #2607 Application Name Publisher .NET Framework 19.0 Microsoft .NET Runtime 6 Preview Microsoft .NET SDK 6 Preview Microsoft 3DMark UL 3uTools 2.35 3uTools 4D 17.6 4D 4K Stogram 3.0 OpenMedia ABACUS Studio 8.0 Avolution ABCpdf .NET 11.1 WebSupergoo Software ACQUITY Column Manager 1.7 Waters Acrobat Elements 17.1 Adobe ACT Enterprise Client 2.12 Access Control ACT Enterprise Client 2.3 Access Control ACTEnterprise 2.3 Vanderbilt Actiance Vantage OpenText Actional Agent 9.0 Progress Software Active Directory (AD) Bridge 8.5 Enterprise BeyondTrust Active Directory/LDAP Connector 5.0 Auth0 Active Intelligence Engine 4.4 Attivio ActivePresenter 8.1 Atomi Systems ActivePython 3.8 ActiveState ActivInspire 2.17 Promethean Activity Monitor 4.0 STEALTHbits Technologies Activity Monitor Agent 2.4 STEALTHbits Technologies ActiViz.NET 8.2 Supported Kitware SAS ActiViz.NET 8.2 Trial Kitware SAS ActiViz.NET 9.0 Supported Kitware SAS Acumen Cumulative 8.5 Deltek AD Tidy 2.6 Cjwdev AdAnalytics Adslytic Add-in Express for Microsoft Office and .NET 8.3 Professional Add-in Express Add-in Express for Microsoft Office and .NET 9.4 Premium Add-in Express Adlib PDF 5.1 Enterprise Adlib AdminStudio 2021 Flexera AdminStudio 2021 ZENworks Flexera Advance Design 2020 GRAITEC Advance Design 2021 GRAITEC Advanced SystemCare 14.0 IObit Advertising Editor 11.29 Microsoft Advisor 9.5 Belarc AFP Viewer 7.50 ISIS Papyrus Europe AG Agile Requirements Designer 3.1 Broadcom Alfresco Content Services 6.0 Alfresco Software AltspaceVR 4.1 Microsoft
    [Show full text]
  • Debian and Ubuntu
    Debian and Ubuntu Lucas Nussbaum lucas@{debian.org,ubuntu.com} lucas@{debian.org,ubuntu.com} Debian and Ubuntu 1 / 28 Why I am qualified to give this talk Debian Developer and Ubuntu Developer since 2006 Involved in improving collaboration between both projects Developed/Initiated : Multidistrotools, ubuntu usertag on the BTS, improvements to the merge process, Ubuntu box on the PTS, Ubuntu column on DDPO, . Attended Debconf and UDS Friends in both communities lucas@{debian.org,ubuntu.com} Debian and Ubuntu 2 / 28 What’s in this talk ? Ubuntu development process, and how it relates to Debian Discussion of the current state of affairs "OK, what should we do now ?" lucas@{debian.org,ubuntu.com} Debian and Ubuntu 3 / 28 The Ubuntu Development Process lucas@{debian.org,ubuntu.com} Debian and Ubuntu 4 / 28 Linux distributions 101 Take software developed by upstream projects Linux, X.org, GNOME, KDE, . Put it all nicely together Standardization / Integration Quality Assurance Support Get all the fame Ubuntu has one special upstream : Debian lucas@{debian.org,ubuntu.com} Debian and Ubuntu 5 / 28 Ubuntu’s upstreams Not that simple : changes required, sometimes Toolchain changes Bugfixes Integration (Launchpad) Newer releases Often not possible to do work in Debian first lucas@{debian.org,ubuntu.com} Debian and Ubuntu 6 / 28 Ubuntu Packages Workflow lucas@{debian.org,ubuntu.com} Debian and Ubuntu 7 / 28 Ubuntu Packages Workflow Ubuntu Karmic Excluding specific packages language-(support|pack)-*, kde-l10n-*, *ubuntu*, *launchpad* Missing 4% : Newer upstream
    [Show full text]
  • Portuguese Flash Cards
    A B C D E F G H puxar 2001 to pull 2001 narrar 2002 to recount 2002 suportar 2003 to endure 2003 desejar 2004 to wish 2004 suplicar 2005 to beg 2005 cozinhar 2006 to cook 2006 dialogar 2007 to talk 2007 costurar 2008 to sew 2008 guardar 2009 to keep 2009 assegurar 2010 to assure 2010 placa 2011 plate 2011 guarda-chuva 2012 umbrella 2012 escova 2013 broom 2013 cobra 2014 snake 2014 ‡gua 2015 water 2015 cama 2016 bed 2016 boneca 2017 doll 2017 aldeia 2018 village 2018 testa 2019 forehead 2019 terra 2020 earth 2020 Liberation Philology [email protected] http://members.aol.com/libphil/ Software for Portuguese, Catalan, Latin, Irish, Old English, Old Norse, Old Occitan, Gothic, Greek, Sanskrit etc. A B C D E F G H correcto 2021 right 2021 muito 2022 very 2022 mesmo 2023 same 2023 jovem 2024 young 2024 nunca 2025 never 2025 branco 2026 white 2026 negro 2027 black 2027 tambŽm 2028 also 2028 rid’culo 2029 ridiculous 2029 bonito 2030 pretty 2030 estudante 2031 student 2031 hoje 2032 today 2032 parede 2033 wall 2033 sorte 2034 luck 2034 vinagre 2035 vinegar 2035 m‡rmore 2036 marble 2036 atitude 2037 attitude 2037 pr’ncipe 2038 prince 2038 bebe 2039 baby 2039 juventude 2040 youth 2040 Liberation Philology [email protected] http://members.aol.com/libphil/ Software for Portuguese, Catalan, Latin, Irish, Old English, Old Norse, Old Occitan, Gothic, Greek, Sanskrit etc. A B C D E F G H conhecer 2041 to know 2041 permanecer 2042 to remain 2042 compreender 2043 to understand 2043 dizer 2044 to say 2044 fazer 2045 to do 2045 ver 2046 to see 2046 poder 2047 to be able 2047 querer 2048 to want 2048 correr 2049 to run 2049 dever 2050 to have to 2050 filho 2051 son 2051 amigo 2052 friend 2052 dinheiro 2053 money 2053 esposo 2054 spouse 2054 anjo 2055 angel 2055 juramento 2056 oath 2056 tesouro 2057 treasure 2057 mŽdico 2058 doctor 2058 mercado 2059 market 2059 diabo 2060 devil 2060 Liberation Philology [email protected] http://members.aol.com/libphil/ Software for Portuguese, Catalan, Latin, Irish, Old English, Old Norse, Old Occitan, Gothic, Greek, Sanskrit etc.
    [Show full text]
  • Xrdp.Log.Pdf
    Printed by Stephen Quinney Feb 05, 19 13:46 xrdp.log.txt Page 1/3 * Wednesday 31st January 2018 Stephen has imported the XRDP configuration from SEE. Most of it has been put into lcfg−level headers so that it can be shared. At the top level the service is configured using the dice/options/external−xrdp−server.h header. There is a test service accessible at xrdp.inf.ed.ac.uk which seems to work well. A quick survey of clients for Linux suggests that the best is remmina. Stephen will be talking about the project at the next Development meeting so before then he will collect all his notes on a wiki page for the project. * Wednesday 7th February 2018 Since SEE has already put together a remote desktop solution which works well and is freely available, there seemed little point in trying other possible solutions; so a small test version of SEE’s RDP−based remote desktop service has been set up here in Informatics. It uses HAProxy as a load−balancing front end. In the trial service at xrdp.inf.ed.ac.uk, the front end routes connection requests to the less loaded of the two backend machines, or to an existing session if there is one. The test service will be open to computing staff. It’s envisaged that the full service will use real hardware rather than virtual, and that there will be separate staff and student services. The next work on this project will be to add some Informatics identity to the login screen; to change access controls on the PAM stack for the backend machines, to permit differences between staff and student services; and to document the services on computing.help.
    [Show full text]