An easier way to get to know the system


30 years ago, I got in touch with programming at the first time.

After 10 years,I developed a SCM system by myself and sold it successfully.

5 years later, I hopped my job and engaged with the core business of Chinese first-line life insurance companies.

At 2005, the business upgrading of the insurance companies inspired me a lot and therefore I put my hand to the tool, which is goal- oriented: you can spare more time while people are digging the code. You will only spend 10 minutes to get familiar to the logic, while the other use 1 hour trying to translate the code.

One year earlier I quitted my job and began the commercialization of this original tool. I named it Program Logic Extract Device.

This tool achieved my goal. It can translate the enormous Programming codes as easy as a pie and even ravel out the logic inside of them.

In June I determined to extract Linux, which lots of programmers want to learn about but at the same time don't have courage to face it.

Extract principle:

1.cover the source code documents as much as possible. (reference makefile)

2.try not to change the SC(If needed, mainly change to conditional compiling,see annotations under ple_build.c)

Extract environment:windows 8. There is no relative environment of Linux.

Extract version: based on linux 4.0.4, current version: 4.4

Extract boundaries:core part of x86-32 bits platform,internalstorage and document parts are not included.

There are ways to get to know linux:

What we have already summarized are mainly the parts of core enablement (sorry to clarify that we are not professional at Linux),we are looking forward to someone to come forward with us.

By means of our function tree you are able to read all the functions that are extracted.


Due to the lack of environment(without Linux environment),we cannot achieve covering all the source codes. Moreover can we not cover all the theories.

We didn’t extract the assembly codes, because we are not professional at assemblymen, which could cause errors of function links. For example, the function die will be linked to  arch/x86/kernel/dumpstack.c.

Here exist some unreadable codes. These are mainly caused by the unsuccessful extractions of conditional compiling. That each change of compiling will arouse chain reactions, we had to make some technical improvements to control those codes in a tolerance interva. Other than that, we are not able to find the provenances of some codes, like oid_search_table in /lib/oid_registry.c,It should be array block according to the context, however, there are no meanings in h. and c. So we thought it could be produced by the macrocode, but where exactly? If you know it, please tell us!

Letter of thanks:

To all the resources I used from the Internet.

To my guide- Mr Li and Mr Qiao.

To all the one who offered me with help.

To my beloved family.

With your corporation we could be better:

We look forward to your sponsorship to advance the technology of our program.You can support us with ways down below:

1. Annotate the SC to let more people get to know Linux. We will update it regularly.

2.recommend or provide us with business chances. We can extract embedded SQLc(large data bases,Tuxedo 3 layer structures etc.,we have already such cases) standard C-program. We can do deep extracting,help developer to solve relative problems,output documents as required.

3.sponsor us:Industrial and Commercial Bank of China,account:622200 0200120300348,accountee:武松山 Songshan Wu ( Please leave your contact information attached,We have clear goal and know exactly what we are doing)

武松山 Songshan Wu

8.6 .2015


qq group:476570507

tel:+86 13436368359