A crescente oferta de programas de código aberto na rede mundial de computadores expõe potenciais usuários a muitas possibilidades de escolha. Em face da pluralidade de interesses desses indivíduos, mecanismos eficientes que os aproximem daquilo que buscam trazem benefícios para eles próprios, assim como para os desenvolvedores dos programas. Este trabalho apresenta o AppRecommender, um recomendador de aplicativos GNU/Linux que realiza uma filtragem no conjunto de programas disponíveis e oferece sugestões individualizadas para os usuários. Tal feito é alcançado por meio da análise de perfis e descoberta de padrões de comportamento na população estudada, de sorte que apenas os aplicativos considerados mais suscetíveis a aceitação sejam oferecidos aos usuários. / The increasing availability of open source software on the World Wide Web exposes potential users to a wide range of choices. Given the individuals plurality of interests, mechanisms that get them close to what they are looking for would benefit users and software developers. This work presents AppRecommender, a recommender system for GNU/Linux applications which performs a filtering on the set of available software and individually offers suggestions to users. This is achieved by analyzing profiles and discovering patterns of behavior of the studied population, in a way that only those applications considered most prone to acceptance are presented to users.

A crescente oferta de programas de código aberto na rede mundial de computadores expõe potenciais usuários a muitas possibilidades de escolha. Em face da pluralidade de interesses desses indivíduos, mecanismos eficientes que os aproximem daquilo que buscam trazem benefícios para eles próprios, assim como para os desenvolvedores dos programas. Este trabalho apresenta o AppRecommender, um recomendador de aplicativos GNU/Linux que realiza uma filtragem no conjunto de programas disponíveis e oferece sugestões individualizadas para os usuários. Tal feito é alcançado por meio da análise de perfis e descoberta de padrões de comportamento na população estudada, de sorte que apenas os aplicativos considerados mais suscetíveis a aceitação sejam oferecidos aos usuários. / The increasing availability of open source software on the World Wide Web exposes potential users to a wide range of choices. Given the individuals plurality of interests, mechanisms that get them close to what they are looking for would benefit users and software developers. This work presents AppRecommender, a recommender system for GNU/Linux applications which performs a filtering on the set of available software and individually offers suggestions to users. This is achieved by analyzing profiles and discovering patterns of behavior of the studied population, in a way that only those applications considered most prone to acceptance are presented to users.

There is a great variety of software solutions which improve quality of work and increase productivity. Nevertheless there still is a demand for specialized software sollutions, often coupled to particular production systems. In this work author approaches such a concrete subject of computer hardware and repair in small and medium enterprise. Proposed information system not only allows internal administration of service requests within a company, but also provides complete status and process overview for customers accessing company's intranet. This is a unique solution of a kind as others are too general and do not fullfil specific demands posed in the specification. The main subject of this work is software design, development and investigation. Analysis of current software technology platforms was performed and the best deployment platform LAMP (Linux-Apache-MySQL-PHP) was selected. Modular system design provided easy system development and future extendability as well as integration into other portals. Final resulting information system incorporates a number of advanced networking and programming technologies: template engine, certificate based security, data encryption engine and others. Implemented software is customized to meet the needs of particular enterprise and is currently used as part of its' intranet and service network. Legal open source technologies were mostly used for developing the product.

Software reuse is prevalent in software development. It is not uncommon that one software product may depend on numerous libraries/products in order to build, install, or run. Software reuse is difficult due to the complex interdependency relationships between software packages. In this work, we presented four approaches to retrieve such dependency information, each technique focuses on retrieving software dependency from a specific source, including source code, build scripts, binary files, and Debian spec. The presented techniques were realized by a prototype tool, DEx, which is applied to a large collection of Debian projects in a comprehensive evaluation. Through the comprehensive analysis, we evaluate the presented techniques, and compare them from various aspects. / Graduate

The system Spacewalk is a managment tool for the linux operating systems based on RPM package manager. The aim of thesis is adding support to Spacewalk for DEB package managment system, which is connected with Debian, a distribution of linux operating system. The result is native support of managing Debian system by the Spacewalk, what includes a registration of system, distribution of configuration files, remote scripts running and managment of DEB packages.

Package management in Linux systems is a popular way to install and update software and the de facto standard on Ubuntu, Debian, Fedora, RedHat, CentOS and OpenSUSE. The software provided in the repositories can however differ when it comes to fixing vulnerabilities since package maintainers in some cases must implement some specific changes to the source used to build the software to make it compatible with the Linux system it is intended to be executed on. The Common Vulnerabilities and Exposures (CVE) standard provides a way to compare how fixes for vulnerabilities is handled on each Linux system where this work is aimed to examine if there exists different patterns when it comes to the time in days it took for a fix to emerge in the changelog for the software. This data is collected by using scripts in Linux to iterate through the National Vulnerability Database (NVD) which contains CVE entries, the severity score in terms of the impact of the vulnerability and references to which systems that the vulnerability affects. The dates are collected by using another script that iterates through the changelog of all available packages and saves the earliest date when the fix was issued. The results show that there is not enough statistical significance to reliably determine if a difference existed between the Linux distributions except when comparing OpenSUSE with Ubuntu, Debian and Fedora where significance was found which suggests that further study is needed. The comparison showed that Ubuntu, Debian and Fedora was slightly better than RedHat on average regarding the time windows between when a CVE was published to when a fix was mentioned in the changelog and OpenSUSE was slower than all other Linux distributions. / Att använda pakethanterare i Linux system är ett populärt sätt att installera och uppdatera mjukvara och är det främsta sättet som används av Ubuntu, Debian, Fedora, RedHat, CentOS och OpenSUSE. Mjukvaran som finns i Linux repositories kan dock skilja sig när det gäller att fixa sårbarheter eftersom package maintainers som är ansvariga för att bygga paketen ibland måste implementera specifika ändringar i källkoden för att mjukvaran skall vara kompatibel med den Linux distribution som den ämnad att köras på. Common Vulnerabilities and Exposures (CVE) standarden möjliggör att kunna jämföra hur en fix för sårbarheter i mjukvaran hanteras på varje Linux distribution där detta arbete ämnar att undersöka om det finns olika mönster när det gäller hur många dagar det tog för en fix att hittas i ändringsloggen för mjukvaran.     Den data som kommer användas samlas in genom att använda script i Linux som itererar genom National Vulnerability Database (NVD) som innehåller CVE poster, en poäng som innebär vilken allvarlighetsgrad sårbarheten har och referenser till systemen som sårbarheten påverkar. Datumen samlas in med ett annat script som itererar genom alla ändringsloggar för alla tillgängliga paket och sparar det tidigaste datumet då en matchande fix hittades. Resultatet visar att det inte finns tillräckligt med statistisk signifikans för att tillförlitligt fastställa om en skillnad existerade mellan Linux distributionerna förutom när OpenSUSE jämfördes med Ubuntu, Debian och Fedora där signifikans hittades vilket tyder på ett behov av ytterligare studier inom ämnet. Jämförelsen visade att Ubuntu, Debian och Fedora var lite bättre än RedHat i genomsnitt när det gäller tidsfönstret mellan när en CVE publicerades till när en fix nämndes i ändringsloggen och sist kom OpenSUSE som var långsammare än alla andra Linux distributioner.

Software has been studied at a variety of granularities. Code, classes, groups of classes, programs and finally large scale applications have been examined in detail. What lies beyond is the study of software collections that group together many individual applications. Collecting software and distributing it via a central repository has been popular for a while in the open source world, and only recently caught on commercially with Apple’s Mac app store and Microsoft’s Windows store. In many of these software collections, there is normally a complex process that must be followed in order to fully integrate new applications into the system. Moreover, in the case of open source software collections, applications frequently rely on each other for functionality and their interactions can be complex. We know that there are thousands of applications in these software collections that people depend on worldwide, but research in this area has been limited compared to other areas and granularities of software. In this thesis, we explore the evolution and architecture of a large open source software collections by using Debian as a case study. Debian is a software collection based off the Linux kernel with a large number of packages spread over multiple hardware platforms. Each package provides a particular service or application and is actively maintained by one or more developers. This thesis investigates how these packages evolve through time and their interactions with one another. The first half of the thesis describes the life cycle of a package from inception to end by carrying out a longitudinal study using the Ultimate Debian Database (UDD). The birth of packages is examined to see how Debian is growing. Conversely, package death is also analyzed to determine the lifespan of these packages. Moreover, four different package attributes are examined. They are package age, package bugs, package maintainers and package popularity. These four attributes combine to give us the overall biography of Debian packages. Debian’s architecture is explored in the second part of the thesis, where we analyze how packages interact with each other by examining the package dependencies in detail. The dependencies within Debian are extensive, which makes for an interesting architecture, but they are complex to analyze. This thesis provides a close look at the layered pattern. This pattern categorizes each package into one of five layers based on how they are used. These layers may also be visualized to give a concise view of how an application is structured. Using these views, we define five architectural subpatterns and anti-subpatterns which can aid developers in creating and maintaining packages.

Während sich der Chemnitzer Linux-Tag über die vergangenen fünf Jahre mit jedem Mal in der Zahl der Aussteller, Helfer und Gäste steigerte, wuchs auch in jedem Jahr das Tagungsnetzwerk. Den Informatikern wird häufig nachgesagt, daß sie wenig dokumentieren würden. Dieses Vorurteil traf auch für das Netzwerk der vergangenen Chemnitzer Linux-Tage zu. Unter anderem, um diesem Mißstand abzuhelfen, haben wir uns bemüht, möglichst detailliert Informationen über Konzept, eingesetzte Technologieen und konkrete Konfiguration des Tagungsnetzwerks des Chemnitzer Linux-Tags 2004 zusammenzutragen.

Software has been studied at a variety of granularities. Code, classes, groups of classes, programs and finally large scale applications have been examined in detail. What lies beyond is the study of software collections that group together many individual applications. Collecting software and distributing it via a central repository has been popular for a while in the open source world, and only recently caught on commercially with Apple’s Mac app store and Microsoft’s Windows store. In many of these software collections, there is normally a complex process that must be followed in order to fully integrate new applications into the system. Moreover, in the case of open source software collections, applications frequently rely on each other for functionality and their interactions can be complex. We know that there are thousands of applications in these software collections that people depend on worldwide, but research in this area has been limited compared to other areas and granularities of software. In this thesis, we explore the evolution and architecture of a large open source software collections by using Debian as a case study. Debian is a software collection based off the Linux kernel with a large number of packages spread over multiple hardware platforms. Each package provides a particular service or application and is actively maintained by one or more developers. This thesis investigates how these packages evolve through time and their interactions with one another. The first half of the thesis describes the life cycle of a package from inception to end by carrying out a longitudinal study using the Ultimate Debian Database (UDD). The birth of packages is examined to see how Debian is growing. Conversely, package death is also analyzed to determine the lifespan of these packages. Moreover, four different package attributes are examined. They are package age, package bugs, package maintainers and package popularity. These four attributes combine to give us the overall biography of Debian packages. Debian’s architecture is explored in the second part of the thesis, where we analyze how packages interact with each other by examining the package dependencies in detail. The dependencies within Debian are extensive, which makes for an interesting architecture, but they are complex to analyze. This thesis provides a close look at the layered pattern. This pattern categorizes each package into one of five layers based on how they are used. These layers may also be visualized to give a concise view of how an application is structured. Using these views, we define five architectural subpatterns and anti-subpatterns which can aid developers in creating and maintaining packages.

Chemnitz, Techn. Univ., Studienarb., 2004.