Depends mainly on the GLIBC.
That is the Gnu Main C library, almost all Linux programs need that library (the exemption might be pure assembler programs, but these are rare)
The main file is a symlink -
/lib64/libc.so.6
I currently setting up the 5.0 finale version of Port, but run a few tests prior to shutdown and will boot up the machine after a break. And I am too lazy to look into the new modules.
Currently I have:
Code: Select all
root@porteus:~# file /lib64/libc.so.6
/lib64/libc.so.6: symbolic link to libc-2.33.so
As you can see, I have GLIBC v2.33
Meaning, a program that
needs v2.33 will run, one that needs 2.32 or lower will also run.
But any program that
needs at least v2.34 will never run. You cannot change the GLIBC in a system, that will break everything. (Trust me, I tried. It literally breaks everything, not even init or shutdown will work, the system looks like it is still running, but programs can do only things that have already loaded all the needed libaries functions in the past, anything new, be it minor as dirt will fail since no needed library cannot be loaded anymore. The system is doomed and only a hard reboot can solve that.)
If you need that program with a newer GLIBC you must upgrade your whole system, when that is possible.
Worst case scenario: let's presume the newest available GLIBC for Porteus is GLIBC v2.33. And the program you want to make into a module needs v2.34 - no chance. Then you need to use an older version of that program, one that needs v2.33 or less.
_________________________________________________
But even when the GLIBC seems to work, there still can be some things going wrong because some Linux distros handle some paths differently. The most common issue is the path where the man pages are sitting, Slackware differs from most other distributions in that.
_________________________________________________
You can also try tinycorelinux modules, they are very efficiently made (tcl has rigid standards in creating modules) - and they used to be compatible with Porteus modules, at least approx 1 1/2 years ago that was the case. Just download a tcl module with a correct GLIBC, rename it to whatever
.xzm and activate it, then you see if it works.