Init Framework
Once extracted to your TiVo drive mounted at /tivo, the init_framework.tgz will have placed the following files. Keep in mind that the actual path right now will be /tivo/, but once the drive is running in the tivo, this will be the absolute path. For example, when you’ve extracted it you will find the path for 001_bash.init is /tivo/init/001_bash.init. This is all just clarification. Be sure the following files are in place:
/test.conf
/init/001_bash.init
/init/010_lba48.init
/init/011_uma6fix.init
/init/kmonte.o
/init/monte
/init/vmlinux.px (renamed lba48_2.4.18.px)
/init/uma6fix.o
/init/uma6fix_license.txt
Notes:
The ‘test.conf’ file in your system’s root directory is what kicks off the ‘init_framework’ process, so if it is not found, nothing else that is present in your ‘/init’ folder will be found, and therefore run.
The init_framework montes (chainloads) into the custom lba48 kernel with uma6 support (required for RID units, not required for Non-RID) units. In order to support the monte process, a 3.1.1c killhdinitrd kernel is used.
If you remove the monte process by virtue of deleting the ‘test.conf’ file, you can no longer boot directly into 4.x using a 3.1.1c killhdinitrd kernel.
If you like what’s here, please follow me on twitter here.
