A fresh release of the minimalist and very lightweight Alpine Linux is here, with support for Chinese LoongArch64 CPUs.
As usual for Alpine Linux, 3.21 follows closely upon the release of a new LTS kernel version. Kernel 6.12 was declared the new LTS on December 5, and this version of Alpine was announced the same day (see the bootnote for more information).
Alpine is not a completely GNU-free Linux distro - for instance, although it includes LLVM 19, parts of it are compiled with GCC 14.2.0 - but it comes quite close. While almost all other Linux distributions use the standard GNU standard C library, along with Void Linux, Alpine uses musl libc instead. (In case that makes you think DNS will be broken, the issues around musl and DNS were fixed in Alpine 3.18 a year and a half ago.) Even so, a lot of apps and tools assume that Linux == glibc.
It's hard to specify what gives a Unix-like OS its "feel," but it's definitely a real thing. For this vulture, the combination of a different , shell and core utilities, and the relatively restricted set of desktop apps means Alpine feels more like it's one of the BSDs than any other Linux. As such, if you're tired of the bloat of modern Linux, this is an excellent option to take a step away from it. In the best possible way, it feels like Linux used to decades ago: lean, mean, and devoid of flabby commercial apps. It's also a good first step toward moving to FreeBSD or one of the others. While you still have one foot in the world of Linux, a lot of familiar apps are missing or are very different, and you must learn to adapt.
It's pretty easy to get Alpine running in a VM. Just download the Extended image, boot it, and run setup-alpine. Once it's done, reboot into the new OS and run setup-desktop.
It gets a little trickier on real hardware, especially if you want to dual-boot Alpine. We suggest formatting a key with the essential Ventoy multi-boot creator, and, as well as the Alpine ISO, put the latest SystemRescue ISO file on there too. Use Gparted under SystemRescue to create your target partitions first. Then follow Alpine's instructions for setting up disks manually. (We've yet to see any machine that genuinely needs the separate partition that the setup asks for.)
Boot the Alpine ISO, run through the preliminary steps of - setting the keyboard, finding mirrors, creating users, and so on - but out when it asks where to install. Mount your target partition under , then run setup-disk:
The Alpine wiki points to this guide to dual-booting with Windows 11, which may help anyone unfortunate enough to be lumbered with Microsoft's latest so-called trusted computing effort.
It's worth learning, even if you don't use it as a desktop. As an example, the Frood initramfs-based NAS is a fascinating demonstration of the sort of setup Alpine facilitates - without the complexities of NixOS and learning the Nix language. ®
Synchronizing release schedules with an upstream project has been done for decades. For instance, at first Ubuntu only offered GNOME, and its release cycles were timed to arrive right after new versions of GNOME. When Ubuntu 4.10 was released in 2004, it used kernel 2.6.8. As far as we know, long-term supported kernels didn't exist yet back then. Syncing with kernel releases makes more sense to us than desktop releases, especially since most distros support lots of different desktops. One problem is that the kernel release cycle isn't set in stone: