Based on the SUSE Linux Enterprise (SLE) 12 Service Pack (SP) 3 enterprise-ready operating system. The openSUSE team has unveiled a new version of openSUSE’s Leap edition. The new version, openSUSE Leap 42.3, is a conservative update to the Leap series, introducing mostly minor fixed and package updates. “The release of Leap 42.3 provides adopters a reliable server operating system for deploying IT services in physical, virtual or cloud environments. Leap’s third edition of the 42 series has more than 10,000 packages and offers stability-minded users a refresh and hardware enablement release. The release is powered by the same Linux 4.4 Long-Term-Support (LTS) kernel found in the previous Leap edition. Leap 42.3 continues to use KDE’s Long-Term-Support release 5.8 as the default desktop selection while also offering GNOME 3.20, the same as used by SUSE Linux Enterprise. A variety of additional desktops is available in the installer through the newly designed desktop selection.“
Happy GNU/Linux 😀
After the team’s decision does not want to support the x86 32 bit architecture for OpenSUSE Leap, many users today are at the mercy of the waves. The least painful solution concerns the unstable branch of the distribution. Ladies and gentlemen, you have the possibility to use OpenSUSE tumbleweed even on computers that have the x86 32-bit processors.
As a starting base, Tumbleweed is not suitable for professional use, being a rolling release. With some passage we could choose the most coherent way to have a stability similar to leap, transforming the system into a rolling half-release. So to realize the transformation, I am happy to introduce you two really interesting steps to be able to configure the system in a more stable way.
Launching from the terminal under root the command:
# zypper al ´kernel-version´
You will have the possibility to block the specific package you want, in our example a specific version of the kernel, then instead of version we will write the correct version of the kernel. From this moment on, any future updates will not change the current version of your kernel. Obviously never forgetting that using tumbleweed we would always have a system that requires so many upgrades. If we choose to block the kernel, we can proceed with the recommended package updates for packages already installed in the system by launching from the terminal under root the command:
# zypper inr
In this way we will always be able to update the system with an effective method, keeping the system lean, clean and very stable like a rock solid.
If not, we will not have to launch the two commands previously illustrated but it will be enough to launch the command under root:
# zypper dup
And we will perform the classic upgrade of the distribution, will update all the packages of the system, including the kernel, and in this way we the full potentials of the rolling release.
Happy GNU/Linux 😀