el bandido
TNAP-Images
Current year 2024 TNAP images are based on OpenPLi. The image consists of two main parts which are the root files system and the Linux kernel. The Linux kernel may be ran without enigma2 running, but I don't know of any way to run enigma2 without accessing the Linux kernel.
The enigma2 Linux kernel is the same kernel that would be found on a Linux based machine such as Ubuntu, except the enigma2 Linux kernel is a stripped and Modified version. The enigma2 Linux kernel is also usually "dated" by several years when compared to what is currently available in a Linux distribution. For example, a FTA receiver using a Linux kernel version of 4.4 would be using a Linux kernel distributed in 2016.
Both enigma2 and the Linux kernel contain an amazing amount of files. The enigma2 operating system generates more files while it is running that cannot be seen by disassembling or looking at the file structure of static enigma2 images. An example here would be the /proc folder located in an enigma2 image. This folder will be empty in a static or not running enigma2, but the /proc folder will contain files when the enigma2 is running inside the fta receiver.
The Linux kernel file system has to run or enigma2 cannot run. As stated earlier, the Linux kernel can run without enigma2, but not the other way around. I don't know of a way to look at the Linux kernel file structure while the receiver is running in the same way the enigma2 file structure may be looked at. For example, you may telnet into an enigma2 FTA receiver and see the enigma2 file system using telnet. I don't know of any way to see the Linux kernel file system while the FTA receiver is running.
Attached below are two files that give the best listing I could make of the two file systems that make an OpenPLi based TNAP enigma2 image. The not running or static enigma2 root file system has a listing of almost 18,000 files or sym-links and the Linux kernel from Octagon SF8008 has a listing of over 56,000 files. Once a person adds plugins and the FTA receiver is running, this file system count goes up by a noticeable amount.
It should also be noted that the Linux kernel files may be changed or altered by using patch files, and most of the enigma2 root filesystem can be edited outright. Someone fooling around with building enigma2 images for a few receiver models could easily see a build folder containing several million files with a build folder size exceeding 100 Gigabytes. A Terabyte is not really a lot Disk space for someone building images for several different receivers.
The enigma2 Linux kernel is the same kernel that would be found on a Linux based machine such as Ubuntu, except the enigma2 Linux kernel is a stripped and Modified version. The enigma2 Linux kernel is also usually "dated" by several years when compared to what is currently available in a Linux distribution. For example, a FTA receiver using a Linux kernel version of 4.4 would be using a Linux kernel distributed in 2016.
Both enigma2 and the Linux kernel contain an amazing amount of files. The enigma2 operating system generates more files while it is running that cannot be seen by disassembling or looking at the file structure of static enigma2 images. An example here would be the /proc folder located in an enigma2 image. This folder will be empty in a static or not running enigma2, but the /proc folder will contain files when the enigma2 is running inside the fta receiver.
The Linux kernel file system has to run or enigma2 cannot run. As stated earlier, the Linux kernel can run without enigma2, but not the other way around. I don't know of a way to look at the Linux kernel file structure while the receiver is running in the same way the enigma2 file structure may be looked at. For example, you may telnet into an enigma2 FTA receiver and see the enigma2 file system using telnet. I don't know of any way to see the Linux kernel file system while the FTA receiver is running.
Attached below are two files that give the best listing I could make of the two file systems that make an OpenPLi based TNAP enigma2 image. The not running or static enigma2 root file system has a listing of almost 18,000 files or sym-links and the Linux kernel from Octagon SF8008 has a listing of over 56,000 files. Once a person adds plugins and the FTA receiver is running, this file system count goes up by a noticeable amount.
It should also be noted that the Linux kernel files may be changed or altered by using patch files, and most of the enigma2 root filesystem can be edited outright. Someone fooling around with building enigma2 images for a few receiver models could easily see a build folder containing several million files with a build folder size exceeding 100 Gigabytes. A Terabyte is not really a lot Disk space for someone building images for several different receivers.