Read in a crash or oops-style backtrace and access DWARF information to output the current content of the stack and registers in term of symbols, and the the crash commands to dump/pretty print them. In other words, when looking at a crash dump, answer the questions "Which variable is currently stored in $rax? What is the structure of the stack? Which variable is stored at $rsp+16?"
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.
The current approach to having new hardware support and features in SLE kernels it to integrate changes to individual drivers from the mainline kernel back into the SLE kernel. The Linux Kernel Backports project (https://backports.wiki.kernel.org/) in comparison has an approach which consists in adding a shim layer between unmodified mainline drivers and older kernel interfaces. This project has its roots in wireless drivers. It currently supports only a handful of old ethernet adapters.
The goal of this hackweek project is to integrate support for the Intel 1Gb pci-express ethernet driver e1000e into the Backports project. This particular driver was chosen because it is widely used and modern while not being exotic.
I have been building an archive of the x86_64/default KOTDs for some months now. It's time to make them available at least internally and write some web frontend to the archive. The frontend could do various things:
* Display all packages for a given branch
over 1 year
4 hacker ♥️.
Has no hacker:
In openSUSE Asia summit 2015, there was a talk about the software defined networking, from the virtual switch, the controller, to the simulator. Just want to take a look at open vswitch and Ryu to learn more about SDN.