# Unix UNIX is a standard of The Open Group. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Kubernetes v1.37: Hardening Container Storage with Bind Mount Options and EmptyDir Permissions DevFeed: [Kubernetes v1.37: Hardening Container Storage with Bind Mount Options and EmptyDir Permissions]() Original publisher: [Read original article]() Author: Nispriha Jagan; Neeraj Krishna Gopalakrishna Published: 2026-09-16T18:30:00Z Content type: article Language: en Sources: [Kubernetes Blog]() Topics: [Kubernetes](), [Security](), [mount](), [Filesystems](), [chmod](), [Unix]() Tags: [chmod](), [container](), [containers](), [filesystem](), [hardening](), [kubernetes](), [linux](), [mount](), [permissions](), [storage](), [volume](), [volumes]() ### AI overview Kubernetes v1.37 adds bind mount options and emptyDir permission modes to strengthen storage security. The article explains how noexec, nosuid, nodev, Unix permissions, and the sticky bit can help enforce security policies on writable volumes. ### Source excerpt Kubernetes v1.37 brings important storage security features: emptyDir permission modes and bind mount options. They help application programmers and security professionals implement rigorous security policies, for example, prohibiting deletion of files across containers or execution of arbitrary binaries from writable volumes, directly in Kubernetes without any complicated circumvention. Linux storage and permission fundamentals Before diving into the new Kubernetes features, let us briefly review the low-level Linux security mechanisms that make them possible. Bind mount flags When Linux mounts or remounts a directory, Virtual File System (VFS) flags control what actions are permitted on that filesystem: noexec: Do not permit direct execution of any binaries on the mounted filesystem. nosuid: Do not allow set-user-identifier or set-group-identifier bits to take effect. nodev: Do not interpret character or block special devices on the file system. Directory permissions and the sticky bit Standard Unix permissions regulate access across three scopes: Owner, Group, and Others (e.g., 0755 or 0777). Beyond standard read, write, and execute bits, Linux supports the sticky bit (as in mode 01777). When applied to a directory, the sticky bit ensures that a file inside that directory can only be deleted or renamed by the file's owner or root. This is essential for shared writable directories like /tmp. Motivation for the improvements Why does Kubernetes need bind mount options and emptyDir permissions? The primary goal of these features is to increase the security of Kubernetes workloads by allowing security-related bind mount options on volume mounts. By default, volumes are bind-mounted into containers by the container runtime and kubelet without noexec, nosuid, or nodev flags. This default can undermine security. For example, with noexec missing, a compromised process can use any writable volume (emptyDir, PersistentVolume, etc.) to download, chmod +x, and execute arbitra ## BFS File-System Being Removed For Linux 7.4 DevFeed: [BFS File-System Being Removed For Linux 7.4]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-13T11:03:26Z Content type: news Language: en Sources: [Phoronix]() Topics: [Filesystems](), [Linux](), [kernels](), [Unix](), [boot]() Tags: [boot](), [bootloader](), [desktop-linux](), [filesystem](), [filesystems](), [kernels](), [linux](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [open-source-graphics](), [os](), [phoronix](), [phoronix-test-suite](), [systems](), [technical](), [ubuntu-benchmarks](), [ubuntu-hardware]() ### AI overview BFS, the obsolete UnixWare boot-partition filesystem, is slated for removal from the Linux kernel in version 7.4. The article cites its extremely limited functionality, lack of likely users, and broader efforts to reduce maintenance burdens from rarely used filesystems. ### Source excerpt The latest upstream file-system to be removed from the mainline Linux kernel is... BFS... ## \[Crypto\] Time-based one-time password (TOTP) for 2FA, part I DevFeed: [\[Crypto\] Time-based one-time password (TOTP) for 2FA, part I]() Original publisher: [Read original article]() Published: 2026-09-09T22:00:00Z Content type: tutorial Language: en Sources: [Dennis Yurichev]() Topics: [passwords](), [QR Code](), [Google](), [Python](), [Unix](), [App](), [email](), [Code]() Tags: [account](), [app](), [argument](), [backup](), [code](), [crypto](), [env-file-security](), [github](), [google](), [password](), [protection](), [python](), [run](), [server](), [smartphone](), [unix]() ### AI overview This tutorial explains how time-based one-time passwords work for two-factor authentication. It covers importing a base32-encoded secret from a QR code into Google Authenticator, generating 6-digit login codes, and calculating them with HMAC-SHA-1 from the secret and Unix time. It also discusses backup codes and securely storing TOTP secrets separately from passwords. ### Source excerpt [Crypto] Time-based one-time password (TOTP) for 2FA, part I ## Before NTP there were Time and Daytime DevFeed: [Before NTP there were Time and Daytime]() Original publisher: [Read original article]() Author: jeff@jeffgeerling.com (Jeff Geerling) Published: 2026-08-30T22:09:00Z Content type: article Language: en Sources: [Jeff Geerling]() Topics: [networking](), [Protocol (disambiguation)](), [Unix]() Tags: [apple](), [bug](), [daytime](), [history](), [network](), [ntp](), [rfc-867](), [rfc-868](), [server](), [time]() ### AI overview The article examines the pre-NTP Time and Daytime protocols, RFC 868 and RFC 867, and explains how they provided simple network-based time retrieval. It describes the protocols' low overhead and limitations, including one-second resolution, lack of network-delay measurement, and the 2036 32-bit rollover bug. ### Source excerpt In building an NTP time demo on old Macs for VCF Midwest, I came across RFC 867 and RFC 868, for the 'Daytime' and 'Time' Protocols, respectively. My first exposure to any form of network time was when I upgraded from a used PowerBook 180c to my first 'new' computer, a Power Mac G3, in 2000. With the introduction of Mac OS 8.5, Apple added a 'Network Time Server' option in the Date & Time Control Panel. ## The lingering legacy of 'reserved' ports DevFeed: [The lingering legacy of 'reserved' ports]() Original publisher: [Read original article]() Author: George Michaelson Published: 2026-08-27T23:29:48Z Content type: article Language: en Sources: [APNIC Blog]() Topics: [Protocol (disambiguation)](), [Network](), [Process](), [Operating system](), [Unix](), [ssh](), [Firewall](), [Internet]() Tags: [dns](), [firewall](), [history](), [internet](), [network](), [ntp](), [opinion](), [process](), [processes](), [ssh](), [systems](), [tech-matters]() ### AI overview An exploration of why reserved TCP and UDP ports persist, tracing conventions such as ports 22, 53, 80, and 443 to early Internet services on multi-user systems. It explains the relationship between ports, protocol-specific daemons, operating-system administration, and modern firewall and service-discovery practices. ### Source excerpt Modern service discovery mechanisms increasingly allow services to run on arbitrary ports, yet DNS may remain the one protocol that cannot fully escape its dependency on the long-established convention of port 53. ## Vim: por qué merece la pena frente a nano DevFeed: [Vim: por qué merece la pena frente a nano]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-08-01T13:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Vim](), [POSIX](), [Unix]() Tags: [alpine](), [distro](), [editor](), [posix](), [unix](), [vim]() ### AI overview A practical Spanish tutorial explaining why Vim is worth learning instead of nano. It covers how to exit, save, undo, and redo, then argues that Vim is widely available on Unix systems because vi is required by POSIX. It also discusses BusyBox, Alpine, and Vim's modes. ### Source excerpt Vim parece complicado pero no lo es: aprende a salir, moverte y editar con lo mínimo imprescindible, sin miedo y sin memorizar todo de golpe. ## Linus Torvalds's Shift from Writing Linux Code to Leading the Project DevFeed: [Linus Torvalds's Shift from Writing Linux Code to Leading the Project]() Original publisher: [Read original article]() Published: 2026-07-25T11:20:55Z Content type: article Language: en Sources: [Antirez]() Topics: [Linux](), [Kernel](), [Maintainers](), [Open Source](), [Unix](), [C](), [ESP32](), [Raspberry Pi](), [Rust]() Tags: [c](), [esp32](), [linux](), [linux-kernel](), [maintainers](), [open-source](), [raspberry-pi](), [rust](), [unix]() ### AI overview The article argues that Linus Torvalds's distinctive contribution was not only writing the first Linux kernel, but also shifting early to project leadership, coordination, and delegation. ### Source excerpt (This blog post was adapted from the transcription obtained from my YouTube video at https://www.youtube.com/watch?v=l6lxgYeVZqs) When Linus Torvalds developed the first Linux kernel, he had studied the Minix sources, he had studied computer architecture, he had the base knowledge needed, and he was obviously a very brilliant programmer. But that operation of writing a minimal yet working Unix kernel for the 386 (at the beginning Linux was, let's say, mono-architecture) was something within the reach of many other programmers and students. Many in the sense of, I don't know, 0.1%, one in a thousand, one in ten thousand. Obviously most people are not able to do this kind of feat, but a lot of people are. If you look at Hacker News in the latest years, you'll see how many projects of kernels written in C, microkernels implemented from scratch, kernels written in Rust, kernels made in all sauces and manners, small Unix systems created vertically for the Raspberry Pi, operating systems for the ESP32 and so forth. Writing a kernel is not something within everybody's reach, but it is something that many can complete, if they put enough effort into it. Then, of course, not everybody will do it well. He is a genius programmer, without any doubt, so he did it better. And yet, of Linus there is only one. This implementative capacity of his, in fact, would not tell us much about him: what we should focus on, instead, is what happened later. ## He stopped writing code Among the maintainers of the famous open source projects, he was one of the very few that, very early in the history of the development of Linux, almost completely stopped writing code in order to concentrate on the leading of the project. On being the leader, the coordinator, the single mind holding the clarity about what the goals of the project must be, and so on. And this is a rare thing. Many maintainers (myself included, for a long time) continue instead to implement things directly, to not delegate much, an ## Coding Challenge #127 - Tmux DevFeed: [Coding Challenge #127 - Tmux]() Original publisher: [Read original article]() Author: John Crickett Published: 2026-07-18T08:00:26Z Content type: tutorial Language: en Sources: [Coding Challenges]() Topics: [Code Challenge](), [systems](), [Programming](), [Terminal](), [Unix](), [Shell]() Tags: [coding](), [programming](), [shell](), [ssh](), [systems](), [terminal](), [the-challenge](), [unix]() ### AI overview A coding challenge asks readers to build a simplified version of tmux, a terminal multiplexer. The project covers named sessions, detaching and reattaching, multiple windows, panes, shells, pseudo-terminals, Unix domain sockets, raw terminal modes, and screen rendering. ### Source excerpt This challenge is to build your own tmux. ## How GitHub improved Copilot code review by reshaping agent workflows DevFeed: [How GitHub improved Copilot code review by reshaping agent workflows]() Original publisher: [Read original article]() Author: Napalys Klicius Published: 2026-07-10T15:57:47Z Content type: article Language: en Sources: [GitHub]() Topics: [GitHub Copilot code review](), [Code review](), [Pull Request](), [GitHub](), [GitHub Copilot](), [Command-line interface](), [Unix]() Tags: [agentic-coding](), [agentic-workflows](), [ai-ml](), [architecture-optimization](), [cli](), [code-review](), [copilot](), [developer-tools](), [engineering](), [github](), [github-copilot](), [github-copilot-code-review](), [llms](), [pull-request](), [review](), [unix](), [workflows]() ### AI overview GitHub describes how migrating Copilot code review to shared Unix-style exploration tools initially increased review costs and reduced issue detection in benchmarks. Rewriting the reviewer instructions around pull request workflows led to roughly 20% lower average review cost while maintaining the same review quality. ### Source excerpt How migrating Copilot code review to shared Unix-style code exploration tools reduced review cost by reshaping agent workflows around pull request evidence. The post Better tools made Copilot code review worse. Here's how we actually improved it. appeared first on The GitHub Blog. ## Symlinks Are Still Scary (And Yes, You Can Commit Them to Git) DevFeed: [Symlinks Are Still Scary (And Yes, You Can Commit Them to Git)]() Original publisher: [Read original article]() Author: Randall Degges Published: 2026-07-09T00:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Git](), [ai-coding](), [AI Agent](), [Unix](), [GitHub]() Tags: [ai](), [ai-agent](), [ai-coding](), [application-security](), [article](), [awareness](), [code](), [developer](), [devops](), [devsecops](), [git](), [github](), [scm](), [secrets](), [security](), [security-labs](), [snyk-security-intel]() ### AI overview Symlink attacks exploit the way operating systems transparently redirect symbolic links to other paths. A malicious symlink committed to a Git repository can cause build scripts, editors, or AI coding tools to access unintended files, potentially enabling remote code execution. ### Source excerpt A harmless-looking symlink in a Git repo can redirect a tool into reading or writing anywhere on your machine. That old trick is now showing up in AI coding assistants, with nasty results. ## Coding Challenge #124 - Du DevFeed: [Coding Challenge #124 - Du]() Original publisher: [Read original article]() Author: John Crickett Published: 2026-06-13T08:01:14Z Content type: tutorial Language: en Sources: [Coding Challenges]() Topics: [Code Challenge](), [POSIX](), [Unix](), [Utility Software](), [Programming]() Tags: [coding](), [exercise](), [filesystem](), [posix](), [programming](), [programming-language](), [run](), [unix](), [utilities]() ### AI overview A coding challenge asks readers to build their own POSIX-compatible du utility. It covers recursively traversing directories, calculating disk usage, handling hard links and symbolic links, and presenting results in multiple formats. ### Source excerpt This challenge is to build your own du. ## Coding Challenge #121 - Dd DevFeed: [Coding Challenge #121 - Dd]() Original publisher: [Read original article]() Author: John Crickett Published: 2026-05-23T08:00:59Z Content type: tutorial Language: en Sources: [Coding Challenges]() Topics: [Code Challenge](), [Unix](), [coding](), [Programming](), [Software](), [Mainframe]() Tags: [coding](), [mainframe](), [programming](), [programming-language](), [testing](), [unix](), [usb]() ### AI overview A coding challenge asks readers to build their own version of dd, the Unix utility for copying and converting fixed-size data blocks. The article introduces dd's history, operand-based syntax, common uses, and an initial setup step for implementing and testing the tool. ### Source excerpt This challenge is to build your own dd unix tool. ## Why cURL is a practical debugger for HTTP problems DevFeed: [Why cURL is a practical debugger for HTTP problems]() Original publisher: [Read original article]() Author: fidelitas.io Published: 2026-05-17T08:15:00Z Content type: opinion Language: en Sources: [fidelitas.io]() Topics: [cURL](), [debug](), [Command-line interface](), [Unix]() Tags: [curl](), [debugging](), [headers](), [http](), [tooling](), [unix]() ### AI overview This opinionated developer article argues that cURL is especially useful for debugging HTTP problems in production and remote environments where graphical clients may be unavailable. It contrasts cURL's debugging role with GUI clients' strengths in exploration, sharing, onboarding, and code generation, and introduces commonly useful command-line flags. ### Source excerpt Postman is great. Insomnia is great. But the moment something goes wrong in production, the tool I reach for first is the one that's been on every Unix box since 1996. ## From Plaintext, to BLESS, to Identity: The Evolution of Secure Remote Access DevFeed: [From Plaintext, to BLESS, to Identity: The Evolution of Secure Remote Access]() Original publisher: [Read original article]() Author: info@goteleport.com (Leon Fong) Published: 2026-04-09T00:00:00Z Content type: article Language: en Sources: [Teleport]() Topics: [remote access](), [Security](), [ssh](), [Unix](), [MFA]() Tags: [mfa](), [remote-access](), [security](), [ssh]() ### AI overview A historical developer article traces secure UNIX remote access from plaintext telnet and rsh to SSH encryption and key-based login, then discusses the operational risks of long-lived SSH keys. It also describes Netflix's use of MFA and signed SSH certificates as a more secure remote-access approach. ### Source excerpt A senior Adobe security engineer traces the evolution of secure remote access from telnet to SSH keys, Netflix's BLESS, and modern certificate-based identity. ## Gentoo GNU/Hurd Released with QEMU Boot Image Build Scripts DevFeed: [Gentoo GNU/Hurd Released with QEMU Boot Image Build Scripts]() Original publisher: [Read original article]() Published: 2026-04-01T00:00:00Z Content type: release Language: en Sources: [GNU Hurd]() Topics: [GNU/Hurd](), [Unix](), [Kernel](), [qemu]() Tags: [2026](), [announcement](), [distributed](), [gnu-hurd](), [ipc](), [linux](), [qemu](), [replacement](), [unix]() ### AI overview Gentoo GNU/Hurd has been released. The announcement points to scripts for building a working image that can boot in QEMU and describes GNU Hurd as a replacement for the Unix kernel. ### Source excerpt Gentoo GNU/Hurd released! Details. " The year is 2026 and Gentoo is perhaps ready for an advanced kernel: the GNU Hurd. [...] Scripts to build a working image that can be booted in QEMU can be found at https://codeberg.org/thesamesam/gentoo-hurd (will move that to Gentoo infra). " Read the announcement email. The GNU Hurd is the GNU project's replacement for the Unix kernel. It is a collection of servers that run on the Mach microkernel to implement file systems, network protocols, file access control, and other features that are implemented by the Unix kernel or similar kernels (such as Linux). More detailed. GNU Mach is the microkernel upon which a GNU Hurd system is based. It provides an Inter Process Communication (IPC) mechanism that the Hurd uses to define interfaces for implementing in a distributed multi-server fashion the services a traditional operating system kernel provides. More detailed. ## How we built a virtual filesystem for our Assistant DevFeed: [How we built a virtual filesystem for our Assistant]() Original publisher: [Read original article]() Author: Dens Sumesh Published: 2026-03-24T00:00:00Z Content type: article Language: en Sources: [Mintlify Blog]() Topics: [Filesystems](), [Retrieval Augmented Generation (RAG)](), [Database](), [Bash](), [Unix](), [TypeScript]() Tags: [ai](), [developer](), [engineering](), [filesystem](), [github](), [latency](), [pricing](), [rag](), [typescript](), [unix](), [vercel](), [virtual]() ### AI overview The article explains how Mintlify built ChromaFs, a virtual filesystem for its documentation assistant. ChromaFs translates UNIX commands into queries against an existing Chroma database, allowing the assistant to search, read, and traverse documentation without cloning a repository into a sandbox. ### Source excerpt We replaced expensive sandboxes with ChromaFs, a virtual filesystem over Chroma, to give our docs AI assistant the ability to explore documentation like a developer would. ## netlab: Switch to Lab Directory After an SSH Session Loss DevFeed: [netlab: Switch to Lab Directory After an SSH Session Loss]() Original publisher: [Read original article]() Published: 2026-03-23T07:31:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [ssh](), [Bash](), [Scripting, bash](), [Unix](), [Command-line interface](), [Script](), [Server]() Tags: [bash](), [netlab](), [script](), [server](), [ssh]() ### AI overview This tutorial shows how to use netlab status and jq in a Bash alias to return to the directory of a lab after reconnecting to a netlab server following an SSH session loss. ### Source excerpt I work on a laptop that loves to power down when not used (the right thing to do), which often breaks the SSH session to my netlab server (not so good). Reconnecting is trivial. Figuring out which lab I was working on and where it lives on the disk after a few hours? That's the annoying part. We solved most of that ages ago with the netlab status --all command. It shows all running labs1 and their directories, so you can quickly jump back to where you were. However, even that gets tedious the 100th time you have to do it. Read more ... ## GNU and the AI reimplementations DevFeed: [GNU and the AI reimplementations]() Original publisher: [Read original article]() Published: 2026-03-08T16:08:41Z Content type: opinion Language: en Sources: [Antirez]() Topics: [Artificial Intelligence](), [Unix](), [Linux](), [Programming](), [Software]() Tags: [ai](), [legal](), [linux](), [programming](), [software](), [unix]() ### AI overview This opinion compares contemporary AI-assisted reimplementations of software projects with the GNU project's reimplementation of the UNIX userspace. It discusses behavioral reimplementation, added features, copyright concerns, and the distinction between copying ideas or behavior and copying source code. ### Source excerpt Those who cannot remember the past are condemned to repeat it. A sentence that I never really liked, and what is happening with AI, about software projects reimplementations, shows all the limits of such an idea. Many people are protesting the fairness of rewriting existing projects using AI. But, a good portion of such people, during the 90s, were already in the field: they followed the final part (started in the '80s) of the deeds of Richard Stallman, when he and his followers were reimplementing the UNIX userspace for the GNU project. The same people that now are against AI rewrites, back then, cheered for the GNU project actions (rightly, from my point of view - I cheered too). Stallman is not just a programming genius, he is also the kind of person that has a broad vision across disciplines, and among other things he was well versed in the copyright nuances. He asked the other programmers to reimplement the UNIX userspace in a specific way. A way that would make each tool unique, recognizable, compared to the original copy. Either faster, or more feature rich, or scriptable; qualities that would serve two different goals: to make GNU Hurd better and, at the same time, to provide a protective layer against litigations. If somebody would claim that the GNU implementations were not limited to copying ideas and behaviours (which is legal), but "protected expressions" (that is, the source code verbatim), the added features and the deliberate push towards certain design directions would provide a counter argument that judges could understand. He also asked to always reimplement the behavior itself, avoiding watching the actual implementation, using specifications and the real world mechanic of the tool, as tested manually by executing it. Still, it is fair to guess that many of the people working at the GNU project likely were exposed or had access to the UNIX source code. When Linus reimplemented UNIX, writing the Linux kernel, the situation was somewhat more compli ## Nothing new under the sun: everything is a file DevFeed: [Nothing new under the sun: everything is a file]() Original publisher: [Read original article]() Author: Glauber Costa Published: 2026-01-15T00:00:00Z Content type: opinion Language: en Sources: [Turso Blog]() Topics: [Unix](), [Large Language Model](), [Artificial Intelligence](), [Programming]() Tags: [agents](), [ai](), [ai-agents](), [linux](), [llms](), [programming]() ### AI overview An essay connecting Unix's "everything is a file" principle with the resurgence of file-based workflows in the age of AI agents and LLMs. It explains how files, pipes, and composable tools created a unified interface for software. ### Source excerpt The Unix revolution was built on a key principle: everything is a file. Now, with the rise of AI Agents, LLMs have access to half a century of file-based arcana. The result? Everything is becoming a file again. ## 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 ## \[Unix\]\[C\] Similarities between Unix symlinks and C/C++ pointers/references DevFeed: [\[Unix\]\[C\] Similarities between Unix symlinks and C/C++ pointers/references]() Original publisher: [Read original article]() Published: 2025-12-03T23:00:00Z Content type: comparison Language: en Sources: [Dennis Yurichev]() Topics: [Unix](), [C](), [C++](), [Programming]() Tags: [blog-post](), [c](), [c-plus-plus](), [unix]() ### AI overview This article compares Unix symbolic links with C and C++ pointers and references. It explains the analogy between copying a symlink and dereferencing it, and between copying a pointer and copying the referenced object. ### Source excerpt [Unix][C] Similarities between Unix symlinks and C/C++ pointers/references ## Lookat 2.1.0 released DevFeed: [Lookat 2.1.0 released]() Original publisher: [Read original article]() Author: Staf Wagemakers Published: 2025-09-14T18:04:00Z Content type: release Language: en Sources: [stafwag Blog]() Topics: [Unix](), [color](), [browser](), [changelog]() Tags: [2](), [2025](), [ansi](), [browser](), [bsd](), [changelog](), [color](), [freebsd](), [git](), [linux](), [lookat](), [manpage](), [ncurses](), [netbsd](), [openbsd](), [release](), [unix]() ### AI overview Lookat/Bekijk 2.1.0 is the latest stable release of a Unix file browser and viewer that supports colored man pages. The release adds ANSI color support and includes updates to color handling, documentation, directory organization, and related scripts. ### Source excerpt Lookat 2.1.0 is the latest stable release of Lookat/Bekijk, a user-friendly Unix file browser/viewer that supports colored man pages. The focus of the 2.1.0 release is to add ANSI Color support. News 14 Sep 2025 Lookat 2.1.0 Released Lookat / Bekijk 2.1.0rc2 has been released as Lookat / Bekijk 2.1.0 3 Aug 2025 Lookat 2.1.0rc2 Released Lookat 2.1.0rc2 is the second release candicate of Lookat 2.1.0 ChangeLog Lookat / Bekijk 2.1.0rc2 Corrected italic color Don't reset the search offset when cursor mode is enabled Renamed strsize to charsize ( ansi_strsize -> ansi_charsize, utf8_strsize -> utf8_charsize) to be less confusing Support for multiple ansi streams in ansi_utf8_strlen() Update default color theme to green for this release Update manpages & documentation Reorganized contrib directory Moved ci/cd related file from contrib/* to contrib/cicd Moved debian dir to contrib/dist Moved support script to contrib/scripts ## The 90s UNIX Utility That Fell Out of Favour DevFeed: [The 90s UNIX Utility That Fell Out of Favour]() Original publisher: [Read original article]() Author: Alex Ellis Published: 2025-08-15T08:09:48Z Content type: opinion Language: en Sources: [Alex Ellis' Blog]() Topics: [Unix](), [Linux](), [macOS](), [Bash]() Tags: [bash](), [linux](), [macos](), [network](), [remote-access](), [terminal](), [unix]() ### AI overview An essay revisits the UNIX finger utility, explaining its origins in a high-trust environment where it exposed user information such as login status, idle time, phone numbers, and email activity. It also reflects on the author's early experiences with Linux, MUD servers, telnet, and bash. ### Source excerpt I reminisce of the days of i386, Slackware Linux, and forgotten plaintext UNIX utilities that are still on modern Macs today. ## Lookat 2.1.0rc2 released DevFeed: [Lookat 2.1.0rc2 released]() Original publisher: [Read original article]() Author: Staf Wagemakers Published: 2025-08-03T09:48:50Z Content type: release Language: en Sources: [stafwag Blog]() Topics: [Unix](), [color](), [changelog](), [Documentation](), [CI/CD]() Tags: [bsd](), [changelog](), [ci-cd](), [color](), [documentation](), [freebsd](), [linux](), [lookat](), [manpage](), [ncurses](), [netbsd](), [openbsd](), [release](), [unix]() ### AI overview Lookat 2.1.0rc2 is the second release candidate for Lookat/Bekijk 2.1.0, a Unix file browser and viewer focused on ANSI color support. The release corrects italic color handling, changes character-size naming, supports multiple ANSI streams, updates the default color theme, revises documentation, and reorganizes contribution directories. ### Source excerpt Lookat 2.1.0rc2 is the second release candicate of release of Lookat/Bekijk 2.1.0, a user-friendly Unix file browser/viewer that supports colored man pages. The focus of the 2.1.0 release is to add ANSI Color support. News 3 Aug 2025 Lookat 2.1.0rc2 Released Lookat 2.1.0rc2 is the second release candicate of Lookat 2.1.0 ChangeLog Lookat / Bekijk 2.1.0rc2 Corrected italic color Don't reset the search offset when cursor mode is enabled Renamed strsize to charsize ( ansi_strsize -> ansi_charsize, utf8_strsize -> utf8_charsize) to be less confusing Support for multiple ansi streams in ansi_utf8_strlen() Update default color theme to green for this release Update manpages & documentation Reorganized contrib directory Moved ci/cd related file from contrib/* to contrib/cicd Moved debian dir to contrib/dist Moved support script to contrib/scripts [Next page]()