# operating-systems Published articles for operating-systems. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Libreboot Build System Audit 5 DevFeed: [Libreboot Build System Audit 5]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: article Language: en Sources: [News about Libreboot releases and development]() Topics: [audit](), [opensource](), [boot](), [POSIX](), [ide](), [systems]() Tags: [audit](), [bios](), [bugs](), [canoeboot](), [clean-code](), [coreboot](), [efficiency](), [firmware](), [free-software](), [libre](), [libreboot](), [linux](), [opensource](), [operating-systems](), [posix](), [uefi]() ### AI overview This article describes the fifth audit of Libreboot's lbmk build system, covering changes made since the Libreboot 20240504 release. It reports a reduction in shell-script size, bug fixes, feature changes, and improvements aimed at cleaner and more efficient code. ### Source excerpt Article: Libreboot Build System Audit 5 Web link: https://libreboot.org/news/audit5.html ## How Solaris' Turnstile Influenced the Modern System Designs of Web Browsers and Language Runtimes DevFeed: [How Solaris' Turnstile Influenced the Modern System Designs of Web Browsers and Language Runtimes]() Original publisher: [Read original article]() Author: Olimpiu Pop Published: 2026-09-15T06:06:00Z Content type: article Language: en Sources: [InfoQ]() Topics: [systems](), [Programming](), [Kernel](), [observability](), [browsers](), [web browsers]() Tags: [architecture](), [architecture-design](), [architectures](), [blocking](), [concurrency](), [development](), [efficiency](), [kernel](), [locking](), [memory](), [news](), [observability](), [operating-systems](), [solaris](), [storage](), [systems](), [turnstile-system-design]() ### AI overview The article examines how Solaris innovations influenced modern systems engineering. It discusses the Slab Allocator, OpenZFS, DTrace, Zones, and turnstiles, focusing on how turnstiles reduce per-lock memory overhead while supporting priority inheritance for contended locks. ### Source excerpt Sun's Solaris influenced modern systems engineering, with key innovations like the Slab Allocator for efficient memory management, OpenZFS for advanced storage, and DTrace for observability. Its turnstile mechanism addressed issues with mutexes, promoting lean locking designs that are reflected in contemporary programming languages and web browsers, enhancing performance and memory efficiency. By Olimpiu Pop ## Amazon Linux 2027 Enters Public Preview with SELinux Enforcing by Default DevFeed: [Amazon Linux 2027 Enters Public Preview with SELinux Enforcing by Default]() Original publisher: [Read original article]() Author: Steef-Jan Wiggers Published: 2026-09-15T03:40:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [Linux](), [SELinux](), [migration](), [Amazon Web Services](), [Kernel](), [amazon]() Tags: [amazon](), [amazon-linux-2027-preview](), [architecture](), [architecture-design](), [aws](), [cloud](), [development](), [devops](), [ec2](), [infrastructure](), [kernel](), [linux](), [migration](), [news](), [operating-systems](), [preview](), [selinux](), [x86-64]() ### AI overview AWS has released Amazon Linux 2027 in public preview with SELinux enforcing by default. The change may require application and migration work because policies that only logged violations on AL2023 can block applications on AL2027. The release has no announced AL2023 end-of-support date, general-availability date, or in-place migration path. ### Source excerpt AWS has released Amazon Linux 2027 in public preview, built on the AL2023 baseline with kernel 7.1 and SELinux in enforcing mode by default. Applications that pass on AL2023's permissive mode may fail under enforcing. The announcement gives no AL2023 end-of-support date, no GA date, and no in-place migration path. By Steef-Jan Wiggers ## Announcement: Xcode16 Deprecation in Semaphore DevFeed: [Announcement: Xcode16 Deprecation in Semaphore]() Original publisher: [Read original article]() Author: Pete Miloravac Published: 2026-08-04T13:47:48Z Content type: release Language: en Sources: [Semaphore Engineering]() Topics: [Xcode](), [macOS](), [ci]() Tags: [announcement](), [ci](), [deprecated](), [end-of-life](), [lifecycle](), [macos](), [operating-systems](), [product-news](), [yaml]() ### AI overview Semaphore is deprecating and retiring its macOS Xcode16 build environments. Brownout periods will run from September 7 through October 4, 2026, before the environments are removed on October 5, 2026. Users are instructed to migrate pipelines to macos-xcode26 and validate them. ### Source excerpt MacOS Xcode16 reached the end of its supported lifecycle on Semaphore. To ensure the security, reliability, and maintainability of our platform, we are announcing the deprecation and end of life of MacOS Xcode16 build environments. Semaphore users should switch to Xcode26. Why We're Deprecating Xcode16 As operating systems age, they cease to receive timely security [...] The post Announcement: Xcode16 Deprecation in Semaphore appeared first on Semaphore. ## TempleOS, mental illness, and open-source spectatorship DevFeed: [TempleOS, mental illness, and open-source spectatorship]() Original publisher: [Read original article]() Author: June 5 Published: 2026-06-05T00:00:00Z Content type: opinion Language: en Sources: [Drew DeVault]() Topics: [Operating system](), [Self-hosted](), [C](), [Compiler]() Tags: [c](), [compiler](), [open-source](), [operating-systems](), [self-hosted]() ### AI overview An opinion article on TempleOS argues that its public prominence stemmed less from its technical achievements than from attention to its creator's mental illness. It describes TempleOS as a self-hosted hobby operating system written in a bespoke C dialect, with an editor, interpreter, compiler, and original games. ### Source excerpt The masterwork of Terry A. Davis is his eclectic operating system, TempleOS, which he worked on until his tragic death in 2018. In terms of technical excellence, TempleOS rates well in some respects and poorly in others. For example, it earns the achievement, coveted in OS dev circles, of being self-hosted.1 TempleOS is written in Terry's own bespoke dialect of C and includes an editor, interpreter, and compiler, as well as a number of original games. In other respects, it compares poorly to many hobby OS projects, some of which have achieved significantly greater levels of technical excellence and sophistication. I would place TempleOS somewhere in, say, the lower middle-class of hobbyist operating systems. Among hobbyist operating systems, TempleOS stands out as one of the most well-known, having attracted considerably more press coverage and a much larger fan-base than any other hobby operating system can boast. The reason TempleOS stands out from the crowd is not due to its modest technical achievements, but because it is clearly the product of severe untreated schizophrenia.2 What makes TempleOS special is that Terry built it to talk to God. Every feature and each technical decision re-enforces his schizophrenic delusions, from its implementation language ("HolyC") to its prophetic "oracle" app. Enthusiasts of TempleOS are drawn to it in part because it affords an opportunity to explore the unique, creative masterwork of a person suffering from mental illness in a way that deeply impacts that work. A curious onlooker will find TempleOS interesting and engaging for the space of perhaps one afternoon before moving on. However, for the less scrupulous fans, turning one's attention to Terry himself never failed to entertain. Terry's public life put his mental illness on display, through frequent outbursts, conspiracy theories, rants and nonsensical discourse, all of which was often laced with slurs, racism, and homophobia, endearing him in particular to the 4chan c ## Top Cache Eviction Strategies DevFeed: [Top Cache Eviction Strategies]() Original publisher: [Read original article]() Author: Saurabh Dashora Published: 2026-04-28T09:03:41Z Content type: tutorial Language: en Sources: [System Design Codex]() Topics: [Caching](), [Cache](), [Latency](), [App](), [Databases](), [Redis]() Tags: [browsers](), [cache](), [caching](), [database](), [operating-systems](), [performance](), [redis](), [strategies](), [ttl]() ### AI overview The article explains cache eviction as a way to manage limited cache memory and reviews TTL, LRU, and LFU strategies, including their operation, use cases, advantages, and drawbacks. ### Source excerpt Caching is a crucial technique for improving application performance and responsiveness. ## RSS vs VSZ in Virtual Memory: What the OOM Killer Actually Counts DevFeed: [RSS vs VSZ in Virtual Memory: What the OOM Killer Actually Counts]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-03-17T00:00:00Z Content type: tutorial Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [Processes](), [Linux](), [Kernel]() Tags: [cpu](), [linux](), [memory](), [observability](), [operating-systems](), [pages](), [performance](), [process](), [virtual-memory]() ### AI overview This tutorial explains the difference between virtual address space (VSZ) and resident memory (RSS). Allocating memory usually reserves virtual addresses without immediately assigning physical pages; pages are committed when accessed, often through page faults. It concludes that Linux's OOM killer primarily responds to physical memory consumption, making RSS more useful than allocation counters when investigating process termination under load. ### Source excerpt malloc() does not hand you RAM, it reserves virtual address space. VSZ is a credit limit; RSS is cash. Physical pages are committed one page fault at a time as you actually touch memory, which is why the reservation is cheap and the memset is expensive. The OOM killer selects on RSS, so virtual promises are not what gets your process killed. ## Redesigning my microkernel from the ground up DevFeed: [Redesigning my microkernel from the ground up]() Original publisher: [Read original article]() Author: January Published: 2026-01-12T00:00:00Z Content type: opinion Language: en Sources: [Drew DeVault]() Topics: [systems](), [Kernel](), [kernels](), [Development](), [Code](), [Unix]() Tags: [code](), [cpu](), [development](), [kernel](), [kernels](), [operating-systems](), [os](), [scheduler](), [systems](), [unix]() ### AI overview The author explains why the Helios microkernel project was abandoned after design and implementation problems, and describes starting Hermes from scratch while reusing selected code from Helios and Bunnix. Hermes is not yet feature-complete, but the author says it has a more robust design and supports symmetric multiprocessing. ### Source excerpt As you may recall, circa 2022-2023 I was working on a microkernel written in Hare named Helios. Helios was largely inspired by and modelled after the design of seL4 and was my first major foray into modern OS development that was serious enough to get to a somewhat useful state of functionality, with drives for some real hardware, filesystems, and an environment for running user programs of a reasonable level of sophistication. Helios development went strong for a while but eventually it slowed and eventually halted in a state of design hell. Since Helios was my first major OS project at this scale and with this much ambition, the design and implementation ended up with a lot of poor assumptions that made it a pretty weak foundation for building a complete OS upon. In late 2023 I more or less gave up on it and moved my OS development work out of the realm of writing code and back into the realm of thinking really hard about how to design operating systems. What followed was a couple of years of design thinking, developing small scale design experiments, and doing deeper research into prior art - reading papers and studying existing kernels. It was also during this period that I wrote Bunnix, a working Unix clone, motivated in part by a desire to gain some first-hand experience working in the design and implementation of Unix-style operating systems - a fertile environment for learning a lot of the nuts and bolts of OS implementations by working against a complete and proven design. In August I was finally prepared to have another go. I decided to start over from scratch, importing and adapting and rewriting code from Helios and Bunnix on an as-needed basis to speed things up, and writing from scratch anything where the lessons learned in hindsight outweighed the benefits of adapting existing code.1 The result is Hermes. Hermes has not yet reached feature parity with Helios, lacking some IPC features and an aarch64 port, but already it's significantly more robust and ## Mmap effects in databases DevFeed: [Mmap effects in databases]() Original publisher: [Read original article]() Published: 2025-04-22T00:00:00Z Content type: article Language: en Sources: [Gaurav Sarma's Blog]() Topics: [Database](), [Operating system](), [data](), [systems](), [file](), [memory pool]() Tags: [database](), [file](), [memory](), [mmap](), [operating-systems](), [performance](), [system]() ### AI overview This article explains how databases use operating-system storage and memory mechanisms, including buffered writes, storage blocks, database pages, and memory mapping, and discusses their effects on performance and data resiliency. ### Source excerpt . [mmap Effects in Databases](mmap-effects-in-databases-cover... ## iBGP Local-AS Next Hop Requirements DevFeed: [iBGP Local-AS Next Hop Requirements]() Original publisher: [Read original article]() Published: 2025-04-08T06:08:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [BGP](), [Network](), [Protocol (disambiguation)]() Tags: [bgp](), [configuration](), [network](), [operating-systems](), [route](), [router](), [test]() ### AI overview This article examines the requirements and caveats of using BGP local-as to simulate an iBGP session between different autonomous systems. Integration testing across multiple platforms found that neighbor next-hop-self is required because the next hop is not changed on an iBGP session and may otherwise be unreachable without an underlying IGP. ### Source excerpt Did you know you could use the neighbor local-as BGP functionality to fake an iBGP session between different autonomous systems? I knew Cisco IOS supported that monstrosity for ages (supposedly "to merge two ISPs that have different AS numbers") and added the appropriate tweaks1 into netlab when I added the BGP local-as support in release 1.3.1. Someone couldn't resist pushing us down that slippery slope, and we ended with IBGP local-as implemented on 18 platforms (almost a dozen network operating systems). I even wrote a related integration test, and all our implementations passed it until I asked myself a simple question: "But does it work?" and the number of correct implementations that passed the test without warnings dropped to zero. Read more ... ## Why Huawei's HarmonyOS Next could matter for small computing devices DevFeed: [Why Huawei's HarmonyOS Next could matter for small computing devices]() Original publisher: [Read original article]() Author: Jasper Morgan Published: 2025-04-03T08:46:50Z Content type: opinion Language: en Sources: [Snapp Mobile - Medium]() Topics: [Operating system](), [huawei](), [Open Source](), [Microcontrollers](), [Robotics]() Tags: [harmony-os](), [huawei](), [microcontrollers](), [mobile-app-development](), [open-source](), [operating-systems](), [os](), [robotics]() ### AI overview This opinion article examines Huawei's HarmonyOS Next, a version of HarmonyOS without Android support, and argues that an operating system designed for small computing devices could have a valuable role as those devices become more widespread. ### Source excerpt Last year Huawei ditched Android and in 2025 will be releasing more and more devices running its HarmonyOS Next software platform. HarmonyOS is based on an open source operating system (OpenHarmony) that started as an R&D project at Huawei in 2012. The operating system has been architected to support a wide array of small computing devices from microcontrollers to tablets. It is already used in several of Huawei's TVs, wearables and wireless router products. In 2024 a 'pure' version of the OS, without Android support, was released. This has been branded HarmonyOS Next. Several questions leap to mind: 1/ Does the world actually need a new OS? 2/ Why should we care about what Huawei is doing -- especially those of us outside China? 3/ Finally, what are the chances of success for a new OS? Let's look a little deeper into these topics and try to understand what's going on in this space. 1/ Does the world need a new OS? YES Let me explain why I have come to this conclusion. Computing needs have changed We have seen a steady growth of small form factor computing. We carry computing devices in our pockets, they are found in devices throughout our homes, they are part of our vehicles, they are in medical devices, and in countless industrial settings. Within this context, one could argue that phones are at the larger end of the spectrum when it comes to small computing devices. Single board computers and microcontrollers can be found in mechanical keyboards, security cameras, hand-held medical equipment, at the checkout in our shops etc. Going further, it's not a huge leap to see that the field of robotics is due to take off with the advent of AI for real time context-aware decision making. My first argument, therefore, is that an operating system specifically designed for small computing devices will have a valuable role to play. (Neither iOS nor Android were designed or have evolved to address this need.) Innovation and competition are good Several operating system innovati ## Announcing Chainguard VMs: Minimal, Zero-CVE Container Host Images DevFeed: [Announcing Chainguard VMs: Minimal, Zero-CVE Container Host Images]() Original publisher: [Read original article]() Published: 2025-03-25T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [cloud-infrastructure](), [Containers](), [Security](), [Vulnerabilities](), [supply-chain-security](), [Linux]() Tags: [announce](), [blog](), [blog-post](), [chainguard](), [chainguard-vms](), [common-vulnerabilities-and-exposures](), [container](), [container-hosts](), [cve](), [images](), [infrastructure](), [kernel](), [multi-cloud](), [operating-systems](), [security](), [software-supply-chain](), [virtual-machines]() ### AI overview Chainguard VMs has entered Early Access as a catalog of guarded, minimal, zero-CVE container host images for ephemeral cloud workloads. The images are built from source, include only required container-host components, and are designed to reduce attack surface and simplify vulnerability remediation. ### Source excerpt Chainguard VMs is a catalog of guarded, minimal, zero-CVE container host images that is now in Early Access. ## How fsync and Linux write paths affect data durability DevFeed: [How fsync and Linux write paths affect data durability]() Original publisher: [Read original article]() Published: 2025-02-20T00:00:00Z Content type: tutorial Language: en Sources: [Gaurav Sarma's Blog]() Topics: [Linux](), [Filesystems](), [Kernel](), [Operating system](), [systems]() Tags: [filesystems](), [fsync](), [kernel](), [linux](), [operating-systems](), [storage]() ### AI overview This technical explainer follows a Linux write from user space through kernel buffers, the virtual file system, and storage. It describes how buffering, lazy flushing, filesystems, and sync-related options affect whether data and metadata reach disk, while noting that behavior varies by filesystem and operating system. ### Source excerpt . [How Safe Is Your fsync... ## Running the operating system that you're currently using in a virtual machine (with Secure Boot and TPM emulation) DevFeed: [Running the operating system that you're currently using in a virtual machine (with Secure Boot and TPM emulation)]() Original publisher: [Read original article]() Author: andreacorbellini Published: 2023-11-19T16:33:00Z Content type: tutorial Language: en Sources: [Andrea Corbellini]() Topics: [Ubuntu](), [Secure Boot](), [qemu](), [Operating system](), [boot](), [Kernel]() Tags: [bootloader](), [information-technology](), [operating-systems](), [qemu](), [secure-boot](), [systems](), [ubuntu](), [virtual]() ### AI overview A tutorial explains how to run the operating system currently in use inside a virtual machine, preserving its settings and files. The procedure targets Ubuntu and uses a copy of the drive, TPM emulation with swtpm, and QEMU; it is intended for testing Secure Boot and predicting TPM state without rebooting. ### Source excerpt In this article I will show you how to start your current operating system inside a virtual machine. That is: launching the operating system (with all your settings, files, and everything), inside a virtual machine, while you're using it. This article was written for Ubuntu, but it can be easily adapted to other distributions, and with appropriate care it can be adapted to ... ## Setting Up netboot.xyz for Network Booting DevFeed: [Setting Up netboot.xyz for Network Booting]() Original publisher: [Read original article]() Author: Techno Tim Published: 2023-11-11T13:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [Network](), [boot](), [DHCP](), [Operating system](), [Docker](), [Windows](), [Ubuntu](), [virtualization]() Tags: [boot](), [dhcp](), [docker](), [github](), [network](), [operating-systems](), [self-hosted](), [ubuntu](), [virtualization](), [windows]() ### AI overview A tutorial on setting up netboot.xyz as a network boot service using Docker, configuring DHCP, and booting operating-system environments over a local network. It also discusses local mirrors, UniFi DHCP settings, PXE boot configuration, and limitations such as unsupported environments. ### Source excerpt Imagine all of your favorite operating systems in one place, available anywhere on your network, and you'll never need to use your flash drive again. That's the promise of netboot.xyz, a network boot service that lets you install or boot to any operating system simply by booting to the network. 📺 Watch Video Disclosures: Nothing in this video was sponsored Don't forget to ⭐ netboot.x... ## The origins of the Idle Scan DevFeed: [The origins of the Idle Scan]() Original publisher: [Read original article]() Published: 2023-10-19T10:40:27Z Content type: article Language: en Sources: [Antirez]() Topics: [Network](), [TCP/IP](), [Operating system](), [Tool](), [Protocol (disambiguation)]() Tags: [attacks](), [network](), [operating-systems](), [protocol](), [research](), [tcp](), [tcp-ip](), [tool](), [udp]() ### AI overview The article recounts how the Idle scan originated in 1998 through experimentation with Hping, a tool for crafting unusual TCP/IP packets. It explains that observing incrementing IP ID values revealed a universal outgoing-packet counter in operating systems, which could be used to estimate a networked computer's outgoing traffic. ### Source excerpt The Idle scan was conceived at the end of 1998, evidenced by emails. I had moved to Milan a few months prior, having been there since September if I recall correctly, brimming with new ideas, unaware that my stay in that city would be brief. I spent the summer on the beaches of Sicily, mainly occupied with reading many books recommended by the folks at Seclab (mostly by David). However, those readings needed a catalyst: the Idle scan was an attack born from theoretical rumination, but the stream of thoughts originated from a rather practical circumstance. I had recently created Hping, a tool whose logo was borrowed from that of Nutella. I mention this to emphasize the seriousness that governed my efforts at that time -- after all, I was only twenty-one and already in Northern Italy with a full-time job on my shoulders; some understanding was warranted. Hping was a Swiss Army knife for the TCP/IP protocol. Its initial use was mostly exploratory, for research. With Hping, you could assemble TCP, UDP, and ICMP packets in the most bizarre manner, and encapsulate them in equally eccentric IP packets, fragmented, with fields set to anomalous values. These packets were sent around to observe the network stack response of different operating systems. This is where Idle scan originates: playing with Hping for just a few minutes revealed a well-known yet (to me) surprising fact. The response packets had an ID field that continuously incremented by some measure. At that time, given that the attacks I would later disclose were not yet known, this ID field behavior aroused no concern. Every time an operating system emitted an IP packet, it first incremented a counter (which reset to zero once it reached the maximum value of two to the sixteenth power minus one), then the packet was sent with the ID set to the counter's value. The counter was universal for all outgoing packets. This allowed, for starters, to estimate the outgoing traffic of any networked computer. This information ## The distributed machine DevFeed: [The distributed machine]() Original publisher: [Read original article]() Author: Derek Wilson Published: 2023-10-19T06:00:00Z Content type: opinion Language: en Sources: [Temporal Blog]() Topics: [Computing](), [Architecture & Design](), [Cloud](), [Operating system](), [virtual machines](), [container](), [Processes]() Tags: [architecture](), [cloud](), [computing](), [container](), [distributed](), [how-to](), [operating-systems](), [reliability](), [virtual-machines]() ### AI overview This developer commentary presents Temporal through the lens of computer architecture. It compares physical and virtual machines, operating systems, and container orchestration before arguing that durable execution abstracts distributed processing from applications and represents a new kind of distributed machine. ### Source excerpt Temporal from the perspective of computer architecture ## Deploying Machines with MaaS and Packer - Metal as a Service + Hashicorp Packer Tutorial DevFeed: [Deploying Machines with MaaS and Packer - Metal as a Service + Hashicorp Packer Tutorial]() Original publisher: [Read original article]() Author: Techno Tim Published: 2023-01-28T14:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [Tutorial](), [canonical](), [systems](), [Cloud](), [Linux](), [Windows](), [virtual machines](), [Oracle-VM-VirtualBox]() Tags: [boot](), [canonical](), [cloud](), [dhcp](), [hashicorp](), [how-to](), [linux](), [maas](), [networking](), [operating-systems](), [systems](), [tutorial](), [ubuntu](), [virtual-machines](), [windows]() ### AI overview A tutorial on installing and configuring Canonical MaaS to provision bare-metal and virtual machines, deploy operating systems, configure networking and network boot, commission machines, and create and upload custom images with Hashicorp Packer. ### Source excerpt MaaS or Metal as a service from Canonical is a great way to provision bare metal machines as well as virtual machines.MaaS allows you to deploy Windows, Linux, ESXi, and many other operating systems to your systems helping you to build a bare metal cloud.You can even use Packer from Hashicorp to configure custom images too! We'll cover all of this and more in this tutorial on how to install an... ## The WebAssembly Component Model DevFeed: [The WebAssembly Component Model]() Original publisher: [Read original article]() Author: Joel Dice Published: 2022-07-01T12:00:00Z Content type: tutorial Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [WebAssembly](), [Code](), [systems]() Tags: [code](), [component](), [native](), [operating-systems](), [webassembly]() ### AI overview This tutorial explains the WebAssembly Component Model proposal and builds intuition for module composition by comparing it with how native code is linked, loaded, and run on popular operating systems. ### Source excerpt The WebAssembly Component Model proposal aims to make module composition easy and efficient. In this post, we'll build an intuition for how it works by analogy with how native code is linked, loaded, and run on popular operating systems. ## PinePhone community poll DevFeed: [PinePhone community poll]() Original publisher: [Read original article]() Published: 2021-12-29T00:00:00Z Content type: news Language: en Sources: [Community blog on PINE64]() Topics: [Pinephone](), [Operating system](), [systems]() Tags: [community](), [operating-systems](), [pinephone](), [pinephone-pro](), [survey]() ### AI overview PINE64 asks the PinePhone community to complete a survey about user demographics, daily driving, and the most popular operating systems. The poll is later reported as closed, with results available through a linked page. ### Source excerpt People pick up a PinePhone for the freedom to choose an operating system, to enjoy privacy by default, and to truly own the device they purchase. From the moment a PinePhone departs from our warehouse we no longer have any insight into what happens to it. I frequently get asked questions about PinePhone's user base, the percentage of people daily-driving it, and the most popular operating systems on our platform. I have no real answers to offer to these questions. Today I am turning to you for help to paint a picture of the PinePhone community by volunteering answers. We'll let the survey stay up for about a month to get the largest possible sample. Once the survey gets taken down, we'll crunch the numbers and share them with you in the February community update. Before I let you get to it, PinePhone and PinePhone Pro related news will be dropping very soon, so I encourage you to subscribe to this blog - the subscription widget can be found at the bottom of the page. The poll is now closed. Thank you to everyone who participated! Poll results available here ## Network UPS Tools (NUT) Ultimate Guide DevFeed: [Network UPS Tools (NUT) Ultimate Guide]() Original publisher: [Read original article]() Author: Techno Tim Published: 2021-09-25T15:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [networking](), [Monitoring](), [Linux](), [Raspberry Pi](), [Windows](), [Docker]() Tags: [docker](), [guide](), [hardware](), [homelab](), [linux](), [logs](), [macos](), [monitoring](), [network](), [networking](), [operating-systems](), [power-management](), [server](), [windows]() ### AI overview A practical guide to Network UPS Tools (NUT) covering server setup on a Raspberry Pi, client configuration on Windows and Linux, data visualization, Docker-based web access, monitoring, alerting, and automated shutdowns. ### Source excerpt Meet NUT Server, or Network UPS Tools.It's an open UPS networking monitoring tool that runs on many different operating systems and processors.This means you can run the server on Linux, MacOS, or BSD and run the client on Windows, MacOS, Linux, and more.It' perfect for your Pi, server, or desktop.It works with hundreds of UPS devices, PDUs, and many other power management systems. This is the... ## Proposed Europe/Oslo timezone alias change could discard pre-1970 data and break Joda-Time behavior DevFeed: [Proposed Europe/Oslo timezone alias change could discard pre-1970 data and break Joda-Time behavior]() Original publisher: [Read original article]() Author: Stephen Colebourne (noreply@blogger.com) Published: 2021-09-25T00:55:00Z Content type: opinion Language: en Sources: [Stephen Colebourne]() Topics: [DateTime](), [Programming](), [systems](), [Operating system]() Tags: [blog](), [jdk](), [joda](), [operating-systems](), [smartphones](), [systems](), [timezone]() ### AI overview The article criticizes a proposed change to the IANA timezone database that would make Europe/Oslo an alias of Europe/Berlin because their post-1970 data matches. It argues that this could replace researched pre-1970 Oslo data with Berlin data and cause Joda-Time tests and timezone identifier handling to fail. ### Source excerpt The last time I wrote about the timezone database on this blog, the database was under threat from a lawsuit. Fortunately that lawsuit went away relatively quickly as the company involved got the message that their action was a big mistake. Unfortunately this time the mess is internal. Paul Eggert is the project lead of the timezone database hosted at IANA, a position referred to as the TZ Coordinator. He is an expert in the field, having been involved in documenting timezone data for decades. Unfortunately, he is currently ignoring all objections to an action only he seems intent on making to solve an invented problem that only he sees as important. The database is the world's principle source of timezone information. The data is included in everything from operating systems to smartphones to programming language development kits such as the JDK. While you may never have heard of it, the sheer pervasiveness of the data makes the potential impact of change or damage pretty huge. The timezone database contains information about how clocks have varies in each region around the world. The mandate of the project is to record this information from 1970 onwards. Of course, computers being what they are, a function that returns the timezone for a given date can be passed in a pre-1970 date as well as a post-1970 one. For this, and reasons of completeness, the timezone database contains pre-1970 data as well as post-1970 data. If you go to your JDK or operating system and ask for the timezone offset for 1920-01-01 for the ID "Europe/Oslo" or "Europe/Berlin" you will get an answer: DateTimeZone oslo = DateTimeZone.forID("Europe/Oslo"); System.out.println(oslo.getOffset(new DateTime(1948, 6, 1, 12, 0))); //prints 3600000 DateTimeZone berlin = DateTimeZone.forID("Europe/Berlin"); System.out.println(berlin.getOffset(new DateTime(1948, 6, 1, 12, 0))); //prints 7200000 The proposed change is to downgrade "Europe/Oslo" to be merely an alias for "Europe/Berlin". The rationale is th ## Article argues that arbitrarily powerful software, not ransomware, is the problem DevFeed: [Article argues that arbitrarily powerful software, not ransomware, is the problem]() Original publisher: [Read original article]() Author: Adam Published: 2021-06-09T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [Software](), [systems](), [ransomware]() Tags: [enterprise](), [operating-systems](), [software]() ### AI overview The article argues that arbitrarily powerful software, including applications and operating systems, is the underlying problem associated with ransomware risks on enterprise systems. ### Source excerpt Arbitrarily powerful software -- applications, operating systems -- is a problem, as is preventing it from running on enterprise systems. ## What is eBPF? | How eBPF works DevFeed: [What is eBPF? | How eBPF works]() Original publisher: [Read original article]() Author: info@goteleport.com (Virag Mody) Published: 2020-11-05T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [eBPF](), [Linux Kernel](), [Kernel](), [Code]() Tags: [bytecode](), [ebpf](), [kernel](), [linux-kernel](), [operating-systems]() ### AI overview This tutorial introduces eBPF, explaining how it lets programmers execute custom bytecode within the Linux kernel without modifying the kernel or loading kernel modules. It also covers kernel space, user space, and the motivation for extending the kernel. ### Source excerpt eBPF lets programmers execute custom bytecode within the kernel without having to change the kernel or load kernel modules. [Next page]()