# Arch Linux Arch Linux is an independently developed, x86-64 general-purpose GNU/Linux distribution focused on simplicity, minimalism, and code elegance. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Vercel Sandbox now runs on Vercel Managed Images DevFeed: [Vercel Sandbox now runs on Vercel Managed Images]() Original publisher: [Read original article]() Author: Luke Phillips-Sheard Published: 2026-08-10T18:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [releases](), [SDKs](), [Node.js](), [Python](), [Security](), [Ubuntu](), [Python 3.14](), [Tooling](), [Arch Linux]() Tags: [claude-code](), [codex](), [coding-agents](), [linux](), [node-js](), [open-source](), [python](), [python-3-14](), [releases](), [sdk](), [security](), [ubuntu](), [vercel]() ### AI overview Vercel introduces Managed Images, versioned open-source base images for Vercel Sandbox that replace deprecated runtimes. The default universal image runs on Ubuntu and includes Node.js, Python, coding agents, and common utilities, with rolling releases, pinned dependencies, and digest-based immutability options. ### Source excerpt Today we are introducing Vercel Managed Images (VMI), a set of versioned, open-source base images you can use as-is or extend. The source for every image lives in the public vercel/sandbox repository. Managed images replace Sandbox runtimes, which are now deprecated. Starting with version 3 of the Sandbox SDK, new sandboxes default to vercel/sandbox/universal:latest. It ships with Node.js, Python, common coding agents and standard utilities, so most users never build a custom image or install packages at boot. The universal image switches our default operating system from Amazon Linux to Ubuntu, a lighter and more widely used system across the industry. Secure by default Every managed image gets a nightly release. Rolling tags such as latest and the major-version tags pick up operating system and dependency updates automatically, including security patches and new releases of Node.js, Python, and the preinstalled coding agents. Within each release, dependencies are pinned to specific versions wherever possible, so a given image version stays consistent. If you need a fully immutable, reproducible environment, pin to an image digest (SHA). Digest-pinned images opt out of automatic updates. Choose a managed image from the catalog Each managed image targets a different starting point: vercel/sandbox/universal:latest is the new default, a rolling release on Ubuntu 26.04 with Node.js 24, Python 3.14 with uv, the opencode, claude-code, codex, and pi coding agents, and utilities including git, vim, nano, tmux, ripgrep, jq, and fzf. vercel/sandbox/node:22, node:24, and node:26 provide Node.js versions on Ubuntu 26.04. vercel/sandbox/python:3.14 provides Python on Ubuntu 26.04. vercel/sandbox/ubuntu:latest provides base Ubuntu 26.04 with no extra tooling. vercel/sandbox/arch:latest provides Arch Linux, regularly updated, with no Node.js or Python preinstalled. Its large package repository makes it useful for agents that install tools on the fly. Reference an image and migrat ## August Update: Note-able Tablet Updates DevFeed: [August Update: Note-able Tablet Updates]() Original publisher: [Read original article]() Published: 2025-08-16T00:00:00Z Content type: news Language: en Sources: [Community blog on PINE64]() Topics: [Pinephone-Pro](), [Arch Linux](), [Linux](), [Kernel](), [Nix](), [GPU](), [Hardware]() Tags: [community-update](), [gpu](), [hardware](), [kernel](), [linux](), [pinenote](), [pinephone-pro](), [pinetab2](), [software](), [update]() ### AI overview Pine64's August 2025 community update announces a new community manager and covers the discontinuation of the PinePhone Pro, planned refurbished sales and spare-parts availability. It also reports updates involving the PineNote, PineTab2, operating systems, GPU software, PinePhone Pro patches, FreeBSD, and Pinecil. ### Source excerpt Table of contents Housekeeping PinePhone Pro discontinuation New community manager About me My goals as community manager PineNote Current status Operating Systems Arch PostmarketOS Nix WiFi Compatibility The issue Workaround #1 Workaround #2 Some words of warning with this workaround PineTab2 Kernel OS (DanctNIX's Arch Linux ARM port) Mesa (GPU) PinePhone Pro Mainlining project FreeBSD port Contributors welcome! Blisp Want to contribute to the next community update? Housekeeping Welcome back to another community update! In this update we announce a new community manager, updates to the PineTab2 and PineNote, FreeBSD on the PinePhone Pro, a guide on upstreaming PinePhone Pro patches and a small bit for you Pinecil users. PinePhone Pro discontinuation Recently PineStore has also discontinued the PinePhone Pro which was talked about in the last recent blog post. TLDR, sales were low which lead to the discontinuation of the device. Spare parts will be available for purchase for up to two years depending on if they sell well. If you still want a PinePhone Pro, refurbished ones will be put up for sale on the PineStore around the end of the month, similar to how it worked for the PineBook Pro. For more details, people can find it at the link below. https://pine64.org/2025/08/14/august_2025_short_update/ New community manager Authors: Caffeine Today I would like to formally announce that I have stepped up to take the roll as the community manager. This decision was made a few months ago as life has become a lot busier for Gamiee. We would like to thank him for the work he has done maintaining our community cluster and the countless hours spent on helping the community. Gamiee will continue maintaining the cluster for the foreseeable future. About me Hello everyone, my name is Camden, but you may also know me by my online alias CarbonatedCaffeine. I am a computing student from New Zealand (that country next to Australia) and I have been an active part of the Pine64 communit ## How to Identify the Package Manager of a Linux System DevFeed: [How to Identify the Package Manager of a Linux System]() Original publisher: [Read original article]() Author: Umara Mushtaq Published: 2025-07-14T02:13:11Z Content type: tutorial Language: en Sources: [Baeldung - Linux]() Topics: [Package Management](), [Linux](), [apt](), [Bash](), [Scripting, bash](), [Ubuntu](), [Automation](), [Debian](), [Arch Linux](), [dnf](), [Fedora](), [pacman]() Tags: [apt](), [automation](), [bash](), [debian](), [dependency](), [dnf](), [efficiency](), [errors](), [how-to](), [installation](), [linux](), [linux-how-to](), [package-management](), [package-management-scripting-apt-dnf-pacman-snap-yum](), [pacman](), [scripting](), [snap](), [ubuntu]() ### AI overview This tutorial explains how to identify the package manager used by a Linux system. It covers inferring the manager from the distribution, checking distribution metadata with /etc/os-release or lsb_release, verifying an installed manager with which, and using Bash scripts to detect package managers in automated or multi-distribution environments. ### Source excerpt Learn different ways to guess or identify the default package manager of a Linux system. The post How to Identify the Package Manager of a Linux System first appeared on Baeldung on Linux. Related Stories How to Check for Available Package Updates in Linux How to Properly Install Valgrind? Background Jobs in a Loop in Bash ## Reproducible Builds at FOSDEM 2024 DevFeed: [Reproducible Builds at FOSDEM 2024]() Original publisher: [Read original article]() Published: 2024-02-08T00:00:00Z Content type: news Language: en Sources: [reproducible-builds.org]() Topics: [reproducible builds](), [FOSDEM](), [Arch Linux](), [Debian](), [Fedora](), [coreboot](), [software bill of materials]() Tags: [coreboot](), [debian](), [fedora](), [fosdem](), [org](), [reproducible-builds](), [software-bill-of-materials]() ### AI overview The article reports on Reproducible Builds activities at FOSDEM 2024. It highlights Holger Levsen's talk covering the project's history, current state, and future goals, along with other talks on reproducibility, confidential computing, RISC-V bootstrapping, reproducible development environments, HPC experiments, configuration options, and software bills of materials. ### Source excerpt Core Reproducible Builds developer Holger Levsen presented at the main track at FOSDEM on Saturday 3rd February this year in Brussels, Belgium. Titled Reproducible Builds: The First Ten Years... In this talk Holger 'h01ger' Levsen will give an overview about Reproducible Builds: How it started with a small BoF at DebConf13 (and before), then grew from being a Debian effort to something many projects work on together, until in 2021 it was mentioned in an Executive Order of the President of the United States. And of course, the talk will not end there, but rather outline where we are today and where we still need to be going, until Debian stable (and other distros!) will be 100% reproducible, verified by many. h01ger has been involved in reproducible builds since 2014 and so far has set up automated reproducibility testing for Debian, Fedora, Arch Linux, FreeBSD, NetBSD and coreboot. More information can be found on FOSDEM's own page for the talk, including a video recording and slides. Separate from Holger's talk, however, there were a number of other talks about reproducible builds at FOSDEM this year: Reproducible builds for confidential computing: Why remote attestation is worthless without it by Malte Poll and Paul Meyer. RISC-V Bootstrapping in Guix and Live-Bootstrap by Ekaitz. rix: an R package for reproducible dev environments with Nix by Bruno Rodrigues. Making reproducible and publishable large-scale HPC experiments by Philippe Swartvagher. Documenting and Fixing Non-Reproducible Builds due to Configuration Options by RANDRIANAINA Georges Aaron. ... and there was even an entire track on Software Bill of Materials. ## Clojure Sound 3 - Hello MIDI Controller DevFeed: [Clojure Sound 3 - Hello MIDI Controller]() Original publisher: [Read original article]() Published: 2022-06-30T21:59:00Z Content type: tutorial Language: en Sources: [Dragan Djuric]() Topics: [Clojure](), [MIDI](), [Arch Linux](), [Linux]() Tags: [clojure](), [connectivity](), [core](), [music](), [sound](), [tutorial](), [usb]() ### AI overview A Clojure Sound tutorial that introduces MIDI controller input and explains how to use it to control software on a computer. It discusses MIDI device connectivity, Clojure Sound, and example hardware such as the Faderfox MX12. ### Source excerpt You may not know that music instrument were connected devices even in the Stone Age, that is, many decades ago. In the 80's that even resulted in the standard that facilitated connectivity of heterogeneous devices. Typically, you'd have a keyboard, a synthesizer, some external knobs, maybe effect boxes, and many of them could be connected by cable and talk to each other, even though that synth might be 27 years old, and the keyboard 2 years old. That's the power of standard. MIDI might not be technically impressive. Especially for 2022, its transfer rate is unbelievably slow. On the other hand, a random device that you'd pick up at the store, on a yard sale, e-bay, or even at the dumpster, is almost guaranteed to have a MIDI connector. So, even though you'd have a hard time connecting your iPhone with your Linux laptop, my guitar can talk with my Arch Linux desktop just fine (I'm not kidding, it really does!). Making that guitar send a meaningful data to my computer is another pair of shoes. MIDI is very basic, and it's up to the user program to make sense of the data it receives. It is likely that you'll want to use a random exotic device in a very specific way; after all, music and art are all about originality. But, to walk on the Moon, we first have to get up from our bed. That's today's objective: taking input from a MIDI device, and controlling something on our computer by twisting knobs. The software As for the software, we need nothing more than Clojure Sound(), of course! You can read how to prepare a fairly basic Clojure project in the first article in Clojure Sound tutorial series. (require '[uncomplicate.commons.core :refer [close! info]] '[uncomplicate.clojure-sound [core :refer :all] [midi :refer :all] [sampled :refer :all]]) The hardware It is unlikely that you'll have the same controller that I do, but so what? Any MIDI device that has a button or a knob on it will do! At this moment, I'm using Faderfox MX12, not because it's a great device (which it ## Arch Linux System Maintainance. DevFeed: [Arch Linux System Maintainance.]() Original publisher: [Read original article]() Author: Fernando Cejas (me@fernandocejas.com) Published: 2022-03-30T00:00:00Z Content type: tutorial Language: en Sources: [Fernando Cejas Blog]() Topics: [Arch Linux](), [Linux](), [Package manager](), [pacman](), [maintenance](), [upgrade]() Tags: [android](), [culture](), [development](), [engineering](), [guide](), [infrastructure](), [ios](), [java](), [kotlin](), [linux](), [maintenance](), [open-source](), [pacman](), [programming](), [python](), [rust](), [scala](), [software](), [software-development](), [upgrade](), [web-development]() ### AI overview A guide to maintaining Arch Linux installations. It covers system updates, troubleshooting keyring issues, cleaning the pacman cache, removing orphaned and unwanted packages, and managing cache data in the home directory. ### Source excerpt In this guide we will walk through the most important practices **regarding system maintainance for Linux home computers.** Most of them are **Arch Linux** (and variants) specific but we can get ideas on how other distros can use and apply the same principles. ## July update: community developers portal DevFeed: [July update: community developers portal]() Original publisher: [Read original article]() Published: 2021-07-15T00:00:00Z Content type: news Language: en Sources: [Community blog on PINE64]() Topics: [Development](), [Pinephone](), [Embedded Software Dev](), [RIOT](), [Arch Linux](), [Linux]() Tags: [announcements](), [code](), [community](), [developers](), [discord](), [driver](), [embedded](), [firmware](), [i2c](), [pine64](), [pinedio](), [pinephone](), [quartz64](), [update](), [wireless]() ### AI overview PINE64's July community update announces the upcoming PINE64 DevZone developer portal and reports hardware and software progress across PineTime, PinePhone, and Quartz64. It covers InfiniTime 1.2, WaspOS, the Malila firmware project, PinePhone accessories and software, Arch Linux with Plasma Mobile, and Quartz64 upstreaming work. ### Source excerpt This month's big news isn't a piece of hardware or software but rather an upcoming platform aimed at community developers called the PINE64 DevZone. But fret not, I also have a number of hardware news to report - including a new LoRa device called PineDio Stack - as well as an overview of the software progress on our flagship devices. Let's get to it. You can watch the synopsis of this month's community update on YouTube (embedded below) as well as on Odysee and PeerTube. To stay up-to-date with PINE64 news make sure to subscribe to this blog (subscription widget at the bottom of the webpage), follow PINE64 Telegram News channel, the announcements channel in Discord as well as our Twitter and Mastodon. I'd like to thank JF, Alex (clover), Danct12, Peter (pgwipeout), Martijn Braam, Brian (33YN2) and PizzaLovingNerd for their contributions to this community update. N.B. Comments on the blog post need to be in English and follow our Community Rules and Code of Conduct. Note: This image preview protects your privacy. Click to load the video from the Google servers. Link to the video & Community update video summary by PizzaLovingNerd TL;DR Housekeeping: we're creating a community developers portal called the PINE64 DevZone; sign-ups are open PineTime: sealed PineTime units with InfiniTime 1.2 & newest bootloader are now available in the PineStore for $26.99 PineTime: InfniTime 1.2 brings new apps, improvements to RAM and ROM memory and various bug fixes; upcoming release will feature a new watchface PineTime: WaspOS gets a sports app, a watch face chooser and a visual overhaul PineTime: New firmware announced - Malila is based on RIOT and in early stages of development PinePhone Hardware: final keyboard pre-production units now being made, production to start immediately after final review if no issues are found PinePhone Hardware: wireless charging and fingerprint reader back cases being tested and reviewed in coming days; LoRa back case awaiting I2C driver PinePhone S ## Install Arch Linux with Full-Disk Encryption DevFeed: [Install Arch Linux with Full-Disk Encryption]() Original publisher: [Read original article]() Author: Fernando Cejas (me@fernandocejas.com) Published: 2020-12-28T00:00:00Z Content type: tutorial Language: en Sources: [Fernando Cejas Blog]() Topics: [Arch Linux](), [Encryption](), [Linux](), [Package manager](), [Hardware](), [intel](), [dell]() Tags: [android](), [command-line](), [culture](), [debian](), [development](), [distribution](), [encryption](), [engineering](), [infrastructure](), [installation](), [ios](), [java](), [kotlin](), [linux](), [open-source](), [pacman](), [programming](), [python](), [rust](), [scala](), [software](), [software-development](), [web-development]() ### AI overview A guide to installing Arch Linux with full-disk encryption while explaining the concepts involved. It assumes basic command-line knowledge and covers installation on Intel-based hardware, including a Dell XPS 13. ### Source excerpt This post will act pretty much as **a guide** (a **long** one), in order to help you **INSTALL and UNDERSTAND Arch Linux** with **full disk encryption**. Let's also walk together through some of the **concepts involved in the amazing world of Linux**. ## My i3 window manager setup DevFeed: [My i3 window manager setup]() Original publisher: [Read original article]() Author: Sam Saffron Published: 2019-04-10T02:12:04Z Content type: article Language: en Sources: [Sam Saffron]() Topics: [Arch Linux](), [Linux](), [pacman](), [Windows](), [Wiki](), [Ubuntu](), [Documentation](), [Firefox]() Tags: [blog](), [blog-post](), [c-sharp](), [developer](), [documentation](), [firefox](), [linux](), [net](), [pacman](), [rails](), [reddit](), [ruby](), [saffron](), [sam](), [sql](), [ubuntu](), [weblog](), [windows](), [youtube]() ### AI overview A developer describes moving from a Windows setup with Ubuntu and i3 to using Arch Linux and i3 as a primary desktop environment. The article discusses the author's early experience, motivations for choosing Arch Linux, and initial customization of the desktop. ### Source excerpt I have been a long time i3 window manager user. But not really. My old Windows 10 based setup involved doing all my console work in an Ubuntu VM running i3. However, the lion's share of the non console work was still done in Windows, including browsing and more. For multiple years now I only partially experienced i3, it showed. My i3 setup was almost vanilla. My move to Arch Linux changed everything. This move completely shifted the way I think about my relationship with my desktop environment. Previously, my relationship with Windows was very simplistic. Windows works the way it works, I simply adapted to that. Sometimes I learned a new shortcut, but the majority of my Windows day-to-day involved dragging windows around, reaching Firefox window and tab saturation, closing windows with the mouse and so on. I am not a great example of a Windows ninja some users go down a far more custom path. I do feel I am pretty typical though of a developer using Windows or Mac. I was given a menu, I learned a tiny bit of it, then I simply threw away the menu and reached for the mouse. In this blog post I would like to talk about what my 3.5 week adventure has looked like and where I am today! Opening moves When I moved to Linux I did not know much of the current state of Linux on the desktop but I did know 2 things: I would be using Arch Linux I would be using the i3 tiling window manager I opted for Arch cause I love not having to worry about upgrading my system every 6-12 months to another major release, I think pacman and the package library on Arch is amazing, if I ever am missing tiny bits from the official library it is trivial for me to just grab a package from the very comprehensive AUR. I also think the documentation in the Arch wiki is fantastic and it helped me enormously. I opted for i3 cause I wanted to fully experience the window manager, not treat it as a glorified tmux like I was for years. A day or so into my move I was uncomfortable with the way my stock install ## Linux Desktop Setup DevFeed: [Linux Desktop Setup]() Original publisher: [Read original article]() Published: 2019-01-14T23:00:00Z Content type: opinion Language: en Sources: [Dennis Felsing]() Topics: [Linux](), [Arch Linux](), [Kernel](), [Shell]() Tags: [desktop](), [distribution](), [kernel](), [linux](), [linux-desktop-setup](), [news](), [shell](), [terminal]() ### AI overview A personal overview of a Linux desktop software setup and the author's priorities for local, terminal-based, efficient, and composable software. The article discusses using Arch Linux across computers and private servers, including kernel-module and restart issues after upgrades. ### Source excerpt Russian Translation by Akhmad Karimov My software setup has been surprisingly constant over the last decade, after a few years of experimentation since I initially switched to Linux in 2006. It might be interesting to look back in another 10 years and see what changed. A quick overview of what's running as I'm writing this post: Motivation My software priorities are, in no specific order: Programs should run on my local system so that I'm in control of them, this excludes cloud solutions. Programs should run in the terminal, so that they can be used consistently from anywhere, including weak computers or a phone. Keyboard focused is nearly automatic by using terminal software. I prefer to use the mouse where it makes sense only, reaching for the mouse all the time during typing feels like a waste of time. Occasionally it took me an hour to notice that the mouse wasn't even plugged in. Ideally use fast and efficient software, I don't like hearing the fan and feeling the room heat up. I can also keep running older hardware for much longer, my 10 year old Thinkpad x200s is still fine for all the software I use. Be composable. I don't want to do every step manually, instead automate more when it makes sense. This naturally favors the shell. Operating Systems I had a hard start with Linux 12 years ago by removing Windows, armed with just the Gentoo Linux installation CD and a printed manual to get a functioning Linux system. It took me a few days of compiling and tinkering, but in the end I felt like I had learnt a lot. I haven't looked back to Windows since then, but I switched to Arch Linux on my laptop after having the fan fail from the constant compilation stress. Later I also switched all my other computers and private servers to Arch Linux. As a rolling release distribution you get package upgrades all the time, but the most important breakages are nicely reported in the Arch Linux News. One annoyance though is that Arch Linux removes the old kernel modules once yo ## How to install Wordpress on Arch Linux DevFeed: [How to install Wordpress on Arch Linux]() Original publisher: [Read original article]() Author: Marco Gomiero Published: 2018-01-19T00:00:00Z Content type: tutorial Language: en Sources: [Posts on Marco Gomiero]() Topics: [Arch Linux](), [WordPress](), [Linux](), [configuration](), [PHP](), [pacman](), [servers]() Tags: [commands](), [configuration](), [guide](), [how-to](), [install](), [installation](), [linux](), [packages](), [pacman](), [server](), [wordpress]() ### AI overview A tutorial for installing WordPress on Arch Linux, covering Apache setup, PHP configuration, and MariaDB installation. ### Source excerpt Every time I've tried to install Wordpress on Arch Linux it was a tragedy. Sometimes a configuration was missing, sometimes stuff not well known was broken and I never found an updated and complete guide. So here you are! In all the following commands I've omitted "sudo". Please use it when it is necessary. Before starting make you sure that all the packages are updated. pacman -Syu Install Apache First of all, you need to install and configure Apache, the web server. ## IPSEC/L2TP VPN on a Raspberry Pi running Arch Linux DevFeed: [IPSEC/L2TP VPN on a Raspberry Pi running Arch Linux]() Original publisher: [Read original article]() Author: Keith Smiley Published: 2014-01-28T04:49:00Z Content type: tutorial Language: en Sources: [Keith Smiley]() Topics: [Virtual Private Network](), [Arch Linux](), [Raspberry Pi](), [Linux](), [Arm](), [Firewall](), [pacman](), [Script](), [systemd](), [configuration]() Tags: [arm](), [article](), [configuration](), [firewall](), [ipv4](), [linux](), [pacman](), [raspberry-pi](), [script](), [systemd](), [vpn]() ### AI overview This tutorial explains how to configure an IPsec/L2TP VPN on a Raspberry Pi running the ARM version of Arch Linux. It covers installing the required packages, configuring firewall rules and redirects, and creating a systemd-launched script so the configuration persists after restart. ### Source excerpt After you buy a Raspberry Pi, or two, you need to figure out what to use them for. While you'll get a ton of interesting ideas from Googling "uses for a Raspberry Pi," I didn't particularly find them any more than a thought exercise. Making a VPN stood out as an actually useful configuration. Originally when I got my (accidentally chosen) Model A, I spent a little while going through this guide using Raspbian. That seemed to work fine until I recently purchased a Model B to replace it and couldn't reproduce the configuration. I decided to write the steps that I was finally able to use to get a functional VPN running on Arch Linux. I started out by following this guide hoping that it would get me a functioning VPN without too much work. Most of this setup will be based on that article with some tweaks for what I had to do to make the settings stick. Unfortunately while it worked after the setup the configuration did not persist after restart. For this configuration, like I said earlier, I wanted to use the ARM version of Arch Linux rather than Raspbian for the install. You can download the Raspberry Pi compatible Arch image from their downloads page. I'm not sure I would recommend Arch for people who haven't installed it before or at least gotten through their Beginners' Guide. The ARM Image, like the normal image, doesn't come with a GUI, perfect for this use of the Pi. I'm not going to bother with making sure this works before restarting, since that doesn't seem like much of an issue with actual usage (although you can just run the scripts we create and it should work fine). I wouldn't recommend doing much configuration before doing this intial setup. I did this the first time and after an hour of configuration my VPN did not work correctly, I ended up nuking the work I had done and starting over. Start by installing the necessary components: pacman -Sy openswan xl2tpd ppp lsof python2 You need to do some configuration of the firewall and redirects: echo "net.ipv4.