I had presented the "Wicked Network Manager" talk at openSUSE Asia summit @Beijing. I would like to keep studying the topic continuously. Getting involve the source code and study the operating style and components. I also met some problem after discussing and testing issues while my research , I want to keep it as a record and writing the technical document on wiki too.

Tool to inspect the meta data from a mini DV firewire transfer and report any quality problems such as dropouts. Preferably a gstreamer 1.x based tool.

Report from the research mailing list: some colleagues and myself had a small SLES 12 troubleshooting workshop today. We were playing around with the rescue system. There is this magic tool called "systemd-nspawn" that is

Current kGraft implementation allows to apply new patch only when the previous one is applied to the whole system. Every task is handled separately and it needs to wait for a safe place to switch. It might take a while, especially when the task is sleeping. Therefore it would be great to allow to apply more patches in parallel. It is not trivial because different tasks might be in different world, so the slow stub has to be clever and choose the right one without taking any lock...

Firefox dropped its built-in ntlm auth as it only handled ntlmv1 (insecure). On windows it uses SSPI to handle the ntlm cases, and on other platforms it simply does not support NTLM at all (and then only v1) without a manual flag change. Let's get it recognizing /usr/bin/ntlm_auth as the system tool for doing this.

Reverse engineering partially done already. Help appreciated with - decoding video stream from camera (overlay?)

The Allwinner Tech Optimus Board by Merrii is the evaluation board for the Allwinner A80 SoC with big.LITTLE Cortex-A15/-A7 configuration (32-bit ARMv7). The sources leaked from Allwinner contain GPL violations in U-Boot and Linux kernel and therefore won't easily build with openSUSE's armhf gcc (binaries seem to be softfp).

The Nvidia Jetson TK1 is an SBC with Nvidia Tegra K1 SoC (quad-core Cortex-A15, 32-bit ARMv7). I have openSUSE running on the Jetson TK1, but KVM is currently not usable as the CPUs are not booted in HYP mode. Thierry Reding of Nvidia has some work-in-progress for U-Boot and upstream kernel that I would like to test.

The Inforce Computing IFC6540 is an SBC with Qualcomm Snapdragon 805 SoC (32-bit ARMv7). I had previously brought up openSUSE on the IFC6410. A week before Hackweek Interstellar I got the IFC6540 to boot on serial console using the upstream-based Linaro integration branch, up to searching for the rootfs. Since USB and SATA support were still missing, my goal will be to prepare a MicroSD based rootfs to complete the bringup.

The Firefly-RK3288 is the first SBC with the Rockchip RK3288 SoC, the first available chip with Cortex-A17 cores (32-bit ARMv7). I received such a board just in time for Hackweek Interstellar and will be looking into booting an upstream kernel with openSUSE 13.2/Factory rootfs.

The open-iscsi package is the de facto standard Linux iSCSI initiator, but it does not support iSCSI MCS. MCS stands for multiple connections per session, and it means that the iSCSI initiator and target communicate over multiple connections to increase throughput. It is sometimes written as "MC/S".

Create a single node installation of OpenStack with the OpenSUSE OpenStack Quickstart scripts for 64 bit ARM (aarch64).

Learn the grub2 network stack and have fun with ipv6 network booting. :D

With many Proof of Concepts (PoCs) going on for SUSE Cloud, the development team has observed that we have no clear path on how Sales Engineers (SEs) and sometimes dedicated support engineers (xSE) can receive technical support to successfully complete the projects, often leading to escalation calls and even firefighting on-site visits by developers. Goal of that project is to come up with a best practice guide and to eventually set expectations on what's possible from a development point of view. Results should be documented in a central internal location and announced to all relevant parties.

Retty is a tool for changing stdin,stdout,stderr of a running process (http://pasky.or.cz/dev/retty/) which may be handy if you want to attach to a process running e.g. from a died ssh session, changing running process to run from under screen(1) etc.. Currently it doesn't work for 64-bit systems and it doesn't handle changing of a controlling tty of a process (which may be possible using setsid() and opening a new tty). The aim of this project it to fix the above deficiencies and package the tool in OBS.

Play with Docker orchestration tools like the ones provided by CoreOS, OpenShift and kubernetes. Provide packages for openSUSE and SLE.