While normally data is passed to linuxrc (including an AutoYaST profile), modern auto-install tools like Ignition from CoreOS support a very interesting method: the QEMU Firmware Config device. This allows to read from inside the VM a blob by reading /sys/firmware/qemu_fw_cfg/by_name/opt/keyname. The driver is included in recent Linux kernels.

This would be a multiple step solution, a first idea that I would explore would be: 1. Query Florian's qam_reposervice API from RRID to base products and modules needed for update

I would like to work mainly on https://fate.suse.com/323638, think of default configuration and perhaps create a small configuration script for conky.

• learn how to write Dracut modules
• investigate running Salt in Dracut initrd

Yes this project is yet another project for creating a Suse Manager clone. The motivation for that comes mainly from my need for a simple suse manager that i can easily run at home without the massive overhead involved in suse manager setup. Also since i mainly need to manage opensuse machines most of which are tumbleweed, suse managers repository model does not really work well in that case.

The DriConf-Project inside of MESA has seen its latest update in 2006 and is implemented with GTK+ 2. https://dri.freedesktop.org/wiki/DriConf/

Look at this beauty: https://github.com/crowbar/crowbar-core/blob/master/crowbar_framework/app/models/service_object.rb#L941 Nice uh? Its a 500 lines methods that its distinctly separated into 4 different pieces internally that make 4 very distinct phases inside.

See title

The YaST2 Network module manages network configuration including device configuration, DNS, Routing etc.. The current code is not very object oriented and in many cases there is not a good separation between the business logic and the presentation. The API is also not very clear an many people get confused for example between NetworkInterfaces (class that handles with the ifcfg-files and reside in yast-yast2) and LanItems.