Tumbleweed Live Loses Installer, YaST Trusted Boot

by Ostatic Staff - May. 19, 2016

Today in Linux news Douglas DeMaio wrote the next Tumbleweed snapshot is to bring some exciting changes - and some not so exciting. They're dropping the installer from the live images. The YaST team announced some new changes in the bootloader module and installer as well as other developments from Sprint 19.

Douglas DeMaio today wrote that snapshots are being held up again lately due to upgrade to QT 5.6. Dominique Leuenberger teased this upgrade, among others, several times over the last weeks, but DeMaio today said the next snapshot will reflect the change-over, those dated 20160517 or greater. This will allow KDE upgrades to Plasma 5.6, Frameworks 5.22, and Applications 16.04.1. Linux 4.6 is also on the menu as is Perl 5.24.0.

DeMaio also added a reminder that openSUSE is seeking a Release Engineer. Coding is a must, but working remotely is possible. He said, "The position requires a proficiency in several major scripting languages like python, bash and perl. The job location is listed in Nuremberg, but people who are interested in working remotely should also apply." Those interested should consult the listing.

On the flip-side, bad with the good and all, DeMaio said they're dropping the installer from live images. They're still making live images, but one will have to download one of the other images to make the system permanent. No reason was given.

Speaking of openSUSE, The YaST Team shared some more exciting developments emerging from their coding sprints. This time the team announced new Trusted Boot. Trusted Boot "measures the boot integrity and places the results in Platform Configuration Registers" for computers with Trusted Platform Module. Some of those files it checks include the boot kernel, initrd, ntldr, chainloader, multiboot, and modules.

Improvements to SSH key import during install are in store as well. Previously importing keys was done in the background and folks unaware would sometimes file bug reports. Now the importation will "be more visible," or an active configuration option. You can now choose to import from whichever system(s) are detected or not to import at all. Network bonding was improved to alert users when bonding devices are sharing the same physical port (negating the actual purpose of bonding).