The theory behind the partitioning proposal of yast2-storage-ng is that all possible distributions of partitions in the disk are evaluated and the best one, according to this criteria, is chosen. But I have found several examples in which is hard believe that the result is actually the optimal distribution of partitions. So I want to invest some time checking if the error is on my side and the code is indeed proposing the best solution and, if that's not the case, improving the decision making of the code.

I will implement the ReaR upstream issue https://github.com/rear/rear/issues/1399

During regular L3 work I often don't find enough time to work on the command line disk partitioner parted which I maintain. Changes often directly affect yast-storage(-ng) and libstorage(-ng). @aschnell opens bugs faster than I can solve them. Upstream is often slow and often wants patches differently.

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.

While there are plenty of benchmarks that compare different IO multiplexing techniques such as epoll vs poll/select, there's really nothing out there that particularly measures epoll system call latencies under different scenarios. Design and implement a series of performance benchmarks for this call under the 'perf bench' framework.

PVH domains are a new guest type supported by Xen being as lightweight as possible (e.g. no emulation of legacy devices via qemu) while taking advantage of the hardware virtualization features of the x86 processor. As there is no BIOS for a PVH domain booting is a little bit different than for pure hardware virtualized guests. To be able to start such a guest a little shim is needed to gather some information about the environment (especially memory layout) before the standard kernel boot path can be entered. By using a boot loader like grub2 this shim can be avoided as the memory information is already known by grub2 and stored into the so called zeropage according to the multiboot protocol.