Warm greetings fellow Linux-and-FOSS lovers! 😁🙏💚✨🤙
It's been a few months since my last installment of Let's Learn Linux!, so I felt that it was time for another round of Linux love! In this installment, I wanted to touch on one particular version of the Linux release model: the rolling release.
When the topic of operating systems comes up in conversation, whether it is about Windows, MacOS, iOS, Android, the various BSD variants, or even most distributions of Linux, invariably the focus moves to which version, or release, of the OS is being discussed. This is because most operating systems have distinct and discreet versions, often quite different one from the other. Because of this, there are sometimes issues when upgrading from one version to another.
Focusing even just within Linux distributions, the vast majority follow the punctuated or point-release model, where a new version is released at a certain cadence. Ubuntu releases a new version every six months, in April and October. Some distros do so with a bit more time between releases, often once per year, or even every few years. Before a version is released, the software that will be shipped with that version is 'frozen' at a particular point in the development cycle, so any newer versions of such software are ignored until the next release cycle.
I was very familiar with this release model, as I used Ubuntu for six years before being tempted by Arch Linux's always-up-to-date rolling-release model. In honesty, it's one of the things that attracted me to Arch in the first place. Arch Linux has no distinct versions or releases. The installation media, which is released at the beginning of each month, is simply designated by date. You install Arch once, and you have a perpetually up-to-date system.
To give you an example of what I mean by 'perpetually up-to-date system', I want to mention my three Arch Linux installations. All of them were installed quite a bit more than five years ago.
Installation Times
Arch1
Antergos=>Arch - Tuesday, September 19, 2017 PDT (Pacific Daylight Time)
[2017-09-19 00:53 (12:53 AM)]
Arch2
Official Install - Sunday, November 5, 2017 PST (Pacific Standard Time - started at 2AM)
[2017-11-05 05:47 (5:47 AM)]
Arch3
Official Install - Wednesday, January 17, 2018 PST (Pacific Standard Time)
[2018-01-17 10:04 (10:04 AM)]
My first installation was done using Antergos, an Arch-based disto that no longer exists, that I later converted into pure Arch. This first one was installed on Tuesday, September 19, 2017, which means that as of today, it was installed 5 years, 10 months, and 3 days ago.
The second installation was my first one that I installed the official command-line way, and that one was done on Sunday, November 5, 2017, which was 5 years, 8 months, 2 weeks, and 3 days ago.
My third installation was originally done on a desktop computer with UEFI firmware, then when that computer died (jungle living) I converted it to work in my Dell BIOS-boot laptop, then when that computer finally died, I converted the hard drive back to UEFI to be able to work in my new ASUS laptop. This installation was done on Wednesday, January 17, 2018, which was 5 years, 6 months, and 4 days ago.
All of these Arch Linux installations have outlived multiple hard drives and computers. This is possible because I keep a clone of each hard drive, ready to use if the original dies.
Arch is known for having the most up-to-date versions of most software. While Arch is bleeding/cutting-edge, the focus is always to use the most recent stable versions of software, and to make sure that everything 'plays well together' at any particular time. While there are issues or problems that do arise, they are usually fixed quickly, and when there is a change that is known ahead of time will cause problems, it is posted on the Arch Linux homepage. In the almost six years that I've been using Arch, usually everything just works, and when I have run into issues, I've always been able to resolve them.
After having used a rolling-release distribution for more than half a decade, I can tell you that I would never go back to a point-release distro, for many reasons. Arch's way of doing things fits me just fine, thank you very much!
That brings me to the end of this installment of Let's Learn Linux! I hope that it was interesting, educational, motivating, and maybe even inspiring! Until next time! 😁 🙏 💚 ✨ 🤙
Thank you all so much who have helped me get to where I am today, and allowing me to share more of the beauty and magic from my life and my world with you, and for your continuous appreciation and support! I am truly deeply grateful! 😁🙏💚✨🤙
If you'd like to find me on other alternative platforms where I have accounts (I spend most of my time here on Hive), click on this signature image below to go to my LinkTree page.
If you'd like to send me a BTC Lighting Tip (made possible by the fantastic work of brianoflondon on @v4vapp), just scan the QR image below. 👇
Sources
Signature image created by @doze, and the dividers made by @thepeakstudio, with all tweaked to their present form by me.
Banner image created by me using Polish, with the Arch Linux logo converted into ASCII art, and Tux the Linux Peguin created by Larry Ewing.