Although a significant part of the YaST Team is enjoying their well deserved summer vacations, the development wheel keeps turning. During the latest two weeks we have fixed quite some bugs in several parts of (Auto)YaST. But listing fixed bugs it’s quite boring, so let’s focus on more interesting stuff we have also achieved.
- Fetching the AutoYaST profile during installation can be a complex process, as a first step to simplify that, we have documented the current handling of the profile.
- Talking about simplicity, we removed an undocumented AutoYaST feature for creating images.
- We implemented a couple of improvements regarding I/O devices auto-configuration on s390: now Linuxrc persists the setting to the installed system and the installation proposal allows to tune it.
- AutoYaST cloning was also improved and the firewall section can now be exported in compact format. That is, including only the modified zones.
- We achieved a small reduction in the size of the system images used to run the installer.
- As a side result, the documentation of
mk_imagereceived a significant update. - We fixed several aspects of the Service Manager section of the AutoYaST UI. See the pull requests: [1], [2], [3].
- We also made sure YaST can deal with the dual location of
/usr/etc/nsswitch.confand/etc/nsswitch.conf. - Last but not least, we unified the layout for the installer and YaST Firstboot, making both more configurable in the process. See the related documentation and some screenshots.
YaST Firstboot with the layout steps and active banner (the SUSE logo).
YaST Firstboot with the layout title-on-top and also active banner.
YaST Firstboot with the layout title-on-left and without banner.
As you can imagine, more combinations are possible.
As summer continues in Europe, we hope to bring you more refreshing news in two weeks. Meanwhile, try the new features and have a lot of fun!