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.
software.opensuse.org has an app store view. While it looks nice it does not provide the typical promises an app store makes:
- apps resp packages offered there match the user's system
RISC-V is an open ISA (Instruction Set Architecture) based on RISC architecture. It's originated from UC Berkeley and it's attracting more attention in recent years because of its full open architecture so every developer has opportunities to get involved in application processor design or apply it into different applications, such as IoT, Robotics, ... etc.
Any topic about RISC-V is welcome, here are some topics you might be interested in:
Many people ask how to start with openQA, ask "can you run these two lines in bash in an openQA" test and some shun the effort to try out openQA because it is "too big".
Terraform's remote backend requires a Terraform Cloud account and has an initial limited offering. While the initial offering is suitable for small resource management and teams this quickly becomes an issue as usage demands increase. In addition Terraform's remote operations (plan,apply, etc) are executed on HashiCorp's cloud resources which present issues for sensitive data such as passwords and access keys. Users are also constrained to as what tooling is available on the remote execution environment for example having kubectl as part of a local-resource. This project aims to address these shortcomings in a native Kubernetes implementation.
I once had a bad dream.
I started good, a sunny day. I had just fixed an issue and push it to my fork, in order to create a Pull Request. I was happy. It felt awesome to have found a fix so elegant. Two lines of code.
There is a running gag built into openQA called interactive mode. It goes like this: "if you need the interactive mode, it's broken". The reason: the so called interactive mode is a collection of hacks - in theory making it possible to update needles in a running test.
But in fact it's a UI desaster that almost never works. So the goal of this hackweek project is to get rid of it - and instead build a real control from the webui into the backend allowing tests to be written on the fly including needle creation/updates. Easy as that.
I thought it would be time to learn a new programming language. I decided to go with python, as it's an all-rounder and I have some basic knowledge on that.
The idea is to go through the Flask how-to and from there on start to implement my own homepage. This will introduce me to Python and web development at the same time.
Build kdump initrd without dracut
New SUSE R&D Employee workstation/laptop auto-installer
[unassigned] openSUSE app store
Refresh my reverse engineering skills
minimal openQA
Bridle - Terraform remote backend in Kubernetes
openQA IDE
Learn python by building a homepage with Flask