2nd init lets us reinitialize a custom init process with custom binary and rc script.
Translation lol: it starts the init instance a second time, the first one frozen, and the second doing the job. 2nd init changes how a new init is called and injects code to restart the 1st init-but into a different program. If really simply put, another hijack, which circumvents the locked bootloader issue. (You can customise the whole system partition)
It needs to be combined with something called sh hijack, a hijack to run a custom program for a script that calls /system/bin/sh; the script itself occurs in an early stage, which is init as well. This from what I understood from linux manual and a brief look at what 2nd init is.
Sent from somewhere in a strangereal world...
Yep...Thank Byak, I finally found CVPS' blog post about it.
It a method of making a shadow not of the Kernel just the boot folder Init uses to boot into system which is read only. So it's really just making a new startup routine to get a clean no PID system that CM needs to work.
Quite ingenious really! LOL
Would be so much easier if that damn Bootloader were just unlocked! LOL