In order to aid loading openSUSE installation and Live images on USB sticks we have a little GUI program called imagewriter. It's a bit dated so Fabian started a newer one with better UI suitable for touch screen that offers the available images on demand, store images offline for conferences and fairs etc: https://github.com/openSUSE/imagewriter2
It's written in C++ with Qt and still needs some work to be production ready:
almost 2 years
6 hacker ♥️.
Has no hacker:
In the past year we've found ourselves in the middle of a pandemic, we merged two awesome companies together, and we have completely changed the trajectory of SUSE and Rancher. This project is intended to transfer knowledge of SUSE to Rancher and Rancher to SUSE for those who may be challenged with time and resources to try new things. This gives us a chance to explore other uses for Kubernetes all while taking advantage of older equipment (for use as workers) we may have to spare.
io_uring is a new asynchronous I/O framework, which was merged into upstream from 5.1. During this hackweek, I want to learn about the difference between it and native aio, how it is designed and do some performace tests based on it.
Some of my old workstations (Sun3, Apollo DN3x00/4x00) use ECL signals for their monochrome monitor. Since these monitors are already dead or dying I was looking for a conversion to something more modern. As I couldn't find anything I found the ULX3S boards, which already have everything for driving a HDMI monitor. So goal of this project is to use the FPGA board for converting the video signal.
I have a Xiaomi Scooter Pro 1 which I bought two years ago, it has 25 - 27 km/h of max speed by factory setting, but it's more or less slow to me since I'm a speed lover :smiley: So I decide to unlock the speed limit (maximum with safety might be 40 km/h) during this hackweek.
With the teres-1  laptop we have a first arm64 device we could use as end-users. Much work to run mainline kernel + u-boot was done already. But power consumption of the laptop is not optimal (~2 hours of battery life time).
The idea is to support cpufreq for the A64 SoC upstream, which would enable the teres-1, pine64 and pinebook to run more power efficient. up to now it seems nobody is working on the driver .
The kdump plumbing is implemented as a dracut module. The original intention was to reuse the logic that dracut uses to deal with storage and network, but it turns out that kdump needs are often very different, so a lot of time is spent on avoiding dracut features that are undesirable.
This idea has been partially implemented for JeOS images, where we are collecting some data from the images whenever a new build ends up in openQA. For instance, https://openqa.opensuse.org/tests/2419705#step/image_info/9 is collecting the size of the image, as well as total number of RPMs, the list of RPMs with their size and some filesystem information.