Following several delays during the development cycle, the Mageia project has announced the release of Mageia 6. The new version includes the KDE Plasma 5 desktop environment, the DNF package manager is now available alongside urpmi and Mageia 6 includes live test media for the Xfce desktop environment: “The extra time that has gone into this release has allowed for many exciting additions, here are a few of the major additions and key features of Mageia 6: KDE Plasma 5 replaces the previous KDE SC 4 desktop environment. The new package manager DNF is provided as an alternative to urpmi, enabling a great packaging ecosystem: Support for AppStream and thus GNOME Software and Plasma Discover; support for Fedora COPR and openSUSE Build Service to provide third-party packages for Mageia 6 and later; dnfdragora, a new GUI tool for package management inspired from rpmdrake. Brand new icon theme for all Mageia tools, notably the Mageia Control Center. Successful integration of the ARM port (ARMv5 and ARMv7) in the build system, allowing to setup ARM chroots. Installation images are not available yet but will come in the future. GRUB2 as the default bootloader. New Xfce Live images to test Mageia with a lighter weight environment.“
Dump Mageia ISO on a USB flash drive
dd if=mageia-livecd-1-KDE4-europe1-americas-cdrom-i586.iso of=/dev/sd(x) bs=1M
Mageia 6 ships with kernel 4.9, which is a “long-term maintenance” release, with a currently-projected end-of-life (EOL) in January, 2019.
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 😀