Search

Linux has emerged as a popular alternative to proprietary operating systems like Windows and macOS. However, it is often perceived as a niche operating system that only suits tech-savvy users. This research paper assesses the feasibility of Linux as a daily use operating system by examining its features, performance, and usability. We conducted a study with four participants who used different Linux distributions, such as Ubuntu, Pop! OS, OpenSuse and Fedora, and performed various tasks, including installing applications, customizing desktop environments, and testing hardware compatibility. Our results demonstrate that Linux is a practical option for everyday use, with multiple advantages over proprietary operating systems, such as customization options, improved security, and better performance on older hardware. Furthermore, our survey of college students indicates that most of them are disinclined to pay for proprietary operating systems such as Windows. Nevertheless, Linux poses some challenges, such as software incompatibility and a more complex learning curve for inexperienced users. In conclusion, this research paper suggests that Linux is a viable alternative for those willing to learn and looking for a secure and customizable operating system.

The operating system is the most important software on a computer, currently there are several operating systems that are very commonly used in the world of work including Windows, Linux. With these various options, users need to know the characteristics of the OS in running graphic design applications with efficient memory consumption. One of the papers that will be used as a reference in analyzing the OS is a paper with experimental quantitative methods. Referring to the paper, this research will use a quantitative approach with experimental methods, the testing phase is by running a graphic design application on the same hardware but different operating systems, from the experiment a value will be obtained in the form of memory usage numbers when running the application then calculations are carried out using a table. comparison to see which one is more efficient in memory usage, from these results it will be concluded that the characteristics of each OS have their respective advantages and disadvantages.

International audience; Several practical privacy issues have been uncovered in Wi-Fi technologies since 2016 [20], [23]. Those issues allow an attacker to defeat address randomization, an anti-tracking mechanism, and thus to track users of wireless devices in the physical world. As recently demonstrated by Martin et. al [12], OS developers and vendors are deploying fixes, and the number of vulnerable devices is progressively decreasing. After presenting a comprehensive overview of three active attacks, we conduct a number of experiments to assess whether those issues have been fixed. Using a sample of Wi-Fi enabled devices we found that although some issues have been corrected, some devices remain vulnerable and expose their users to tracking. We analyze the implementation of countermeasures in wpa_supplicant, the software component in charge of Wi-Fi features in Linux and Android. We found that, even if countermeasures have been available for several years in wpa_supplicant, they are still not always included or activated in deployed OS. We discuss the reasons behind this lack of protection.

Open-source software and its components are widely used in various products, solutions, and applications, even in closed-source. Majority of them are made on Linux or Unix based systems. Netfilter framework is one of the examples. It is used for packet filtering, load-balancing, and many other manipulations with network traffic. Netfilter based packet filter iptables has been most common firewall tool for Linux systems for more than two decades. Successor of iptables – nftables was introduced in 2014. It was designed to overcome various iptables limitations. However, it hasn’t received wide popularity and transition is still ongoing. In recent years researchers and developers around the world are searching for solution to increase performance of packet processing tools. For that purpose, many of them trying to utilize eBPF (Extended Berkeley Packet Filter) with XDP (Express Data Path) data path. This paper focused on analyzing Linux OS packet filters and comparing their performances in different scenarios. Article in English. Linux OS paketų filtravimo ir apdorojimo saugumo priemonų analizė Santrauka Atvirojo kodo priemonės plačiau naudojamos skirtinguose produktuose ir programose. Dauguma iš jų yra padaryta panaudojant Linux arba Unix sistemas. Netfiler tvarkyklė yra vienas iš pavyzdžių. Ji naudojama paketams filtruoti, apkrovai paskirstyti ir kitoms manipuliacijoms su paketais atlikti. Netfilter paketų filtras ipatables jau du dešimtmečius yra populiariausia Linux ugniasienė. Nauja ugniasienė nftables buvo pristatyta 2014 metais ir turėjo įveikti iptables trūkumus. Tačiau nftables taip ir negavo visuotinio pripažinimo, daug sistemų taip ir nebuvo perkeltos į iptables. Todėl pastaruosius metus mokslininkai ir programinės įrangos kūrėjai ieško naujo sprendimo padidinti paketų apdorojimo našumą. Tam jie bando išnaudoti tokias technologijas kaip eBPF ir XDP. Šio straipsnio tikslas padaryti Linux OS paketų filtro analizę ir palyginti jų našumą skirtinguose scenarijuose. Reikšminiai žodžiai: Linux, Netfilter, iptables, nftables, eBPF, XDP, ugniasienė, paketų filtrai.

Performance interference between QoS and best-effort applications is getting more aggravated as data-intensive applications are rapidly and widely spreading in recently emerging computing systems. While the completely fair scheduler (CFS) of the Linux kernel has been extensively used to support performance isolation in a multitasking environment, it falls short of addressing memory-related interference due to memory access contention and insufficient cache coverage. Though quite a few memory-aware performance isolation mechanisms have been proposed in the literature, many of them rely on hardware-based solutions, inflexible resource management or ineffective execution throttling, which makes it difficult for them to be used in widely deployed operating systems like Linux running on a COTS SoC platform. We propose a memory-aware fair-share scheduling algorithm that can make QoS applications less susceptible to memory-related interference from other co-running applications. Our algorithm carefully separates the genuine memory-related stall from a running task’s CPU cycles and compensates the task for the memory-related interference so that the task gets the desired share of CPU before it is too late. The proposed approach is adaptive, effective and efficient in the sense that it does not rely on any static allocation or partitioning of memory hardware resources and improves the performance of QoS applications with only a negligible runtime overhead. Moreover, it is a software-only solution that can be easily integrated into the kernel scheduler with only minimal modification to the kernel. We implement our algorithm into the CFS of Linux and name the end result mCFS. We show the utility and effectiveness of the approach via extensive experiments.

We describe an efficient system for ensuring code integrity of an operating system (OS), both its own code and application code. The proposed system can protect from an attacker who has full control over the OS kernel. An evaluation of the system's performance suggests the induced overhead is negligible. peerReviewed

In modern smartphones, system performances are tightly related to a variety of underlying subsystems. In particular, internal storage, along the years, has become crucial because it is extensively used to access content relevant to the system and, finally, to the end user. To understand its role in a commercial Android smartphone and to evaluate its effects on the User experience, within the context of a real usage, we analyzed Linux page fault handling, a critical mechanism that puts pressure on storage devices and may cause system inefficiencies. A kernel tracing technique has been conceived for real-time measurement of Android applications and services on commercial smartphones. The experimental results presented in this work are derived from the use of this kernel tracing on a 64-bit Android smartphone, equipped with a ufs storage subsystem. The main subject of the study is major page fault handling, a kernel mechanism behind many end-user actions recognized at industry level as source of possible performance deterioration in a smartphone. The analysis shows that major page fault handling is dominated by read accesses to ufs (between 30% and 40% of the total time), and that the related storage traffic is significantly affected by the ReadAhead mechanism, which is not always efficient.

International audience; Compared to full virtualization, containerization reduces virtualization overhead and resource usage, offers reduced deployment latency and improves reusability. For these reasons, containerization is massively used in an increasing number of applications. However, because containers share a full kernel with the host, they are more vulnerable to attacks that may compromise the host and the other containers on the system.In this paper, we present SNAPPY (Safe Namespaceable And Programmable PolicY), a new framework that allows even unprivileged processes such as containers to safely and dynamically enforce in the kernel fine-grained, stackable and programmable eBPF security policies at runtime. This is done by making working coordinately a new LSM (Linux Security Module) Module, a new security Linux namespace abstraction (policy_NS) and eBPF policies enriched with ’dynamic helpers’. This design especially allows to minimize containers’ attack surface. Our design may be applied to any processes but is particularly suitable for container-based use cases. We show that SNAPPY can effectively increase the security level of containers for different use cases, can be easily integrated with the most relevant norms (OCI, Open Container Initiative) and containerization engines (Docker and runC) and has a performance overhead lower than 0.09% in realistic scenarios.

Nowadays, deploying and executing applications in the cloud is a reality.The cloud can not exist without virtualization.This concept consists of slicing physical machines into several sub-machines, isolated from one another, known as virtual machines.Recently, containers emerged as a viable alternative to virtual machines.Containers are lighter than virtual machines and bring the same isolation and security guarantees.Nonetheless, the isolation they offer is maybe too important.Indeed, existing mechanisms enforce memory isolation by ensuring that no container starves the others; however, they do not adapt to changes in workload.Thus, it is impossible to consolidate memory, i.e. to reclaim memory unused by some containers to make a better use of it.To answer this problem and ensure both isolation and consolidation, we introduce MemOpLight.This mechanism adapts to workload changes thanks to application feedback.Each container tells the kernel whether it has good or bad performance to guide memory reclaim.Memory is first reclaimed from containers with good performance in the hope that the others can improve their own performance.The idea is to find a balance where all containers have satisfying performance.MemOpLight increases container satisfactions by 13% compared to existing mechanisms.; Le déploiement et l'exécution d'applications dans le cloud sont aujourd'hui une réalité.L'existence de celui-ci est intrinsèquement liée à celle de la virtualisation.Ce concept consiste à découper une machine physique en plusieurs sous-machines, dites machines virtuelles, isolées les unes des autres.Plus récemment, les conteneurs se sont posés comme une alternative viable aux machines virtuelles.Les conteneurs sont plus légers que ces dernières et apportent les mêmes garanties d'isolation et de sécurité.Néanmoins, l'isolation, un conteneur ne peut affamer ses congénères, proposée est peut-être trop poussée.En effet, les mécanismes existants permettant l'isolation mémoire ne s'adaptent pas aux changements de charge de travail.Il n'est donc pas possible de consolider la mémoire, c'est-à-dire récupérer la mémoire inutilisée d'un conteneur pour en faire un meilleur usage.Pour répondre à ce problème et garantir, à la fois, l'isolation et la consolidation mémoire, nous proposons MemOpLight.Ce mécanisme s'adapte aux changements de charge de travail grâce à un retour applicatif.Chaque conteneur indique donc s'il a de bonnes performances pour guider la répartition de la mémoire.Celle-ci est récupérée aux conteneurs ayant de bonnes performances pour que les autres conteneurs puissent augmenter celles-ci.L'idée étant de trouver un équilibre mémoire où tous les conteneurs ont des performances satisfaisantes.MemOpLight permet d'augmenter la satisfaction des conteneurs de 13% comparé aux mécanismes existants.

Nowadays, deploying and executing applications in the cloud is a reality.The cloud can not exist without virtualization.This concept consists of slicing physical machines into several sub-machines, isolated from one another, known as virtual machines.Recently, containers emerged as a viable alternative to virtual machines.Containers are lighter than virtual machines and bring the same isolation and security guarantees.Nonetheless, the isolation they offer is maybe too important.Indeed, existing mechanisms enforce memory isolation by ensuring that no container starves the others; however, they do not adapt to changes in workload.Thus, it is impossible to consolidate memory, i.e. to reclaim memory unused by some containers to make a better use of it.To answer this problem and ensure both isolation and consolidation, we introduce MemOpLight.This mechanism adapts to workload changes thanks to application feedback.Each container tells the kernel whether it has good or bad performance to guide memory reclaim.Memory is first reclaimed from containers with good performance in the hope that the others can improve their own performance.The idea is to find a balance where all containers have satisfying performance.MemOpLight increases container satisfactions by 13% compared to existing mechanisms.; Le déploiement et l'exécution d'applications dans le cloud sont aujourd'hui une réalité.L'existence de celui-ci est intrinsèquement liée à celle de la virtualisation.Ce concept consiste à découper une machine physique en plusieurs sous-machines, dites machines virtuelles, isolées les unes des autres.Plus récemment, les conteneurs se sont posés comme une alternative viable aux machines virtuelles.Les conteneurs sont plus légers que ces dernières et apportent les mêmes garanties d'isolation et de sécurité.Néanmoins, l'isolation, un conteneur ne peut affamer ses congénères, proposée est peut-être trop poussée.En effet, les mécanismes existants permettant l'isolation mémoire ne s'adaptent pas aux changements de charge de travail.Il n'est donc pas possible de consolider la mémoire, c'est-à-dire récupérer la mémoire inutilisée d'un conteneur pour en faire un meilleur usage.Pour répondre à ce problème et garantir, à la fois, l'isolation et la consolidation mémoire, nous proposons MemOpLight.Ce mécanisme s'adapte aux changements de charge de travail grâce à un retour applicatif.Chaque conteneur indique donc s'il a de bonnes performances pour guider la répartition de la mémoire.Celle-ci est récupérée aux conteneurs ayant de bonnes performances pour que les autres conteneurs puissent augmenter celles-ci.L'idée étant de trouver un équilibre mémoire où tous les conteneurs ont des performances satisfaisantes.MemOpLight permet d'augmenter la satisfaction des conteneurs de 13% comparé aux mécanismes existants.

Ovaj završni rad testira performanse stolnog računala koje ima operacijski sustav Linux koji je skup osnovnih sustavnih programa koji omogućuje vezu između sklopovlja i korisničkih programa. Pogledom na popularnost distribucija operacijskog sustava Linux odabrane su sljedeće distribucije operacijskog sustava Linux: Ubuntu 20.04. LTS, Linux Mint 19.3. Tricia i PopOS 20.04. Ideja završnog rada je detaljno proučiti i usporediti rad s procesorom, memorijom, grafičkim sustavom i SSD diskom između različitih distribucija Linux operacijskog sustava, te usporediti njihove performanse. Mjerenja su provedena s više različitih testnih alata specijaliziranih za točno određenu komponentu računala. Na osnovu rezultata mjerenja performansi dobivenih koristeći razne testne alate rezultati su analizirani i uspoređeni. Na istom stolnom računalu instalirane su sve distribucije Linux operacijskog sustava i najbolje rezultate uz određene komponente ostvaruje Pop OS 20.04. This bachelor tesis tests the performance of a desktop computer running Linux operating system, which is a set of basic system programs that provides a connection between hardware and user programs. Looking at the popularity of Linux distributions, the following Linux distributions have been selected: Ubuntu 20.04. LTS, Linux Mint 19.3. Tricia and PopOS 20.04. The idea of the final work is to study in detail and compare the work with the processor, memory, graphics system and SSD disk between different distributions of the Linux operating system, and compare their performance. Measurements were performed with a number of different benchmark tools specializing in a specific computer component. Based on the performance measurement results obtained using various benchmark tools, the results were analyzed and compared. All Linux operating system distributions are installed on the same desktop computer, and Pop OS 20.04 achieves the best results with certain components.

Sodobne IOT naprave in vgrajeni sistemi pogosto uporabljajo kompleksno strojno-programsko opremo in operacijske sisteme ki morajo biti posebej prevedeni za uporabo na ciljni platformi, in prilagojeni s popravki, gonilniki in aplikacijami za končni produkt. Zaradi tega se je razvila vrsta postopkov in orodij, ki omogočajo avtomatizacijo in poenostavitev konfiguracije takih sistemov. V delu predstavimo nekaj najpogosteje uporabljenih postopkov priprave zagonskih diskovnih slik za vgrajene platforme na osnovi operacijskega sistema Linux in opišemo prilagajanje sistema in pripravljalnega postopka za specifičen sistem, osnovan na modulu proizvajalca Variscite. Postopek vsebuje več nivojev konfiguracije, od določanja funkcionalnosti perifernih vmesnikov, preko prilagajanja jedrnih modulov vse do priprave uporabe lastne aplikacije na produktu. V zaključku dela povzamemo izboljšave postopka priprave zagonske slike operacijskega sistema glede na začetni ročni postopek. Za konec predstavimo še nekaj možnih izboljšav postopka. Celoten postopek se že uporablja pri pripravi naprav, ki jih Adria Mobil, slovenski proizvajalec rekreativnih vozil, vgrajuje v svoje produkte, Modern IOT devices and embedded systems often make use of complex firmware and operating systems, which must be specifically compiled for use on target platforms. Often, custom patches, drivers and product applications are required. For this reasons, multiple tools and processes for automatic configuration and process simplification were developed. In our work, we present some of the most common tools used in system image preparation for embedded platforms based on the Linux operating system. We describe customization process of the operating system and preparation process for a specific system, based on system-on-chip by a manufacturing company Variscite. The process includes multiple configuration layers, from configuring peripheral interfaces via device tree files, to customizing kernel modules and deploying a proprietary application in userspace. In conclusion, we summarize the improvements of the preparation and customization process compared to the inital semi-manual process. Finally, we present some of the ideas for future improvements. The process is already being used for preparation of devices, being used by the Slovenian recreational vehicles manufacturer, Adria Mobil, in their premium product lines.

Windows and Linux both are operating system. Windows is the famous operating system in market but it is not safe than Linux. With growing concern over operating system security, Linux got famous in the familial market place with that safety and efficiency. Lots of companies have been migrated from Windows towards Linux. The shortage of Linux experts has limited the development of Linux. If cost is deliberated than better is Linux than Windows. Windows is suitable for small matrices while Linux is suitable for large matrices. The aim of this paper is to conduct the survey over Linux and Windows. Basically this paper is comparative in this paper we have compared different methodologies related to Windows and Linux that are used in different researches. The results of different experiments related to Windows and Linux have been compared. Different approaches have been presented in previous researches to solve problems related to Windows and Linux., This article has been published at www.ijarbas.com , Issue and Vol.#2, February, 2020.

It is challenging to achieve a consistent real-time (RT) response time in commodity virtual machine (VM) environments because they have longer and more complex network protocol stacks. This paper analyzes such network stacks and proposes a method that achieves consistent latency in a Linux KVM-based hosted environment. The analysis identifies a priority inversion in the interrupt-first host kernel of vanilla Linux, and the proposed method addresses it by using the PREEMPT_RT patch. Subsequently, the analysis identifies another priority inversion in softirq handling of the host kernel. The proposed method addresses it by dividing softirq handling into RT and non-RT types. The analysis then identifies the cache pollution problem by co-located non-RT servers and the latter priority inversion in a guest kernel. The proposed method addresses them by socket outsourcing, in which a guest kernel delegates network processing to the host kernel. The proposed method achieved consistent latency. Compared to the threaded interrupt handling method, the proposed method reduced the standard deviation (SD) of the latencies of a simple RT server by a factor of 6, achieving 5.6% higher throughput and 32% lower CPU utilization. Compared to the exclusive CPU method, the proposed method reduced the SD by a factor of 2 and prevented underutilization of the exclusive CPU. The proposed method was more scalable in terms of the number of RT VMs. A four-CPU host was able to execute 40 RT VMs using the proposed method while maintaining the throughputs of non-RT servers.