Porteus

why number the modules?
000-kernel ... 003-xfce ... 07-printing ... 08-nvidia ...
The modules must be loaded in exactly this order ?

It helps and sometimes for system modules they have to be.

The system actually picks the modules in the order they are numbered. "Kernel" has to be loaded before "core", which has to be loaded before the D.E. and everything else, as Ed_P pointed out.

Today I discovered an OS which is a lot like Porteus from Malta, called Zephix. The modules it uses also have to have a "priority" in how they are named, and the easiest way is to use series numbers at the beginning of each name.

The thing is there's a discrepancy with how Porteus modules are named: the "vital" components have three-digit series numbers while eg. "05-devel.xzm" has only two digits at front. Everything should have had two digits or three digits because of the way the OS sorts. It doesn't have anything to do with "locales", it's ASCII.

One more important thing is like if you have same filesnames with different content in 001-module and 003-module, while on boot when these modules are extracted and loaded, the file in first module 001 will be replaced with same file in 003-module.

gnintilgyes wrote: ↑

06 Dec 2022, 02:39

The thing is there's a discrepancy with how Porteus modules are named: the "vital" components have three-digit series numbers while eg. "05-devel.xzm" has only two digits at front.

You are correct and that bugged me ever since Porteus was created.

In my book all modules should have the nnn-name syntax ("n" here as: "numeral"), e.g. having "005-devel.xzm" and "006-man.xzm"…

Added in 3 minutes 27 seconds:

Testuser wrote: ↑

06 Dec 2022, 19:00

One more important thing is like if you have same filesnames with different content in 001-module and 003-module, while on boot when these modules are extracted and loaded, the file in first module 001 will be replaced with same file in 003-module.

Indeed, therefore my personal settings and script modules are all named 9[89]?-* to be loaded after all other modules
e.g. 985-palemoon* for my browser stuff and 991-usr_local_bin* for personal global scripts and programs meant to be used for all DEs and finally 992-rootcopy_5.0* for settings individual for each DE.

Hi gnintilgyes,
Zephix modules also work in Porteus 5.0
Rename .zx to .xzm and activate
I've tried krita and natron

roro wrote: ↑

10 Dec 2022, 11:39

Zephix modules also work in Porteus 5.0
Rename .zx to .xzm and activate
I've tried krita and natron

I think there should be a pinned thread listing all Porteus compatible modules of other distros.
Like Tiny Core Linux - or Zephix.
With a short explanation like you did "Rename .zx to .xzm and activate" (or when the file system supports it: create a symlink from file.xz to file.xzm thus having files for Port but also keeping the files for Zephix)

Rava wrote: ↑

10 Dec 2022, 06:35

e.g. 985-palemoon* for my browser stuff and 991-usr_local_bin* for personal global scripts and programs meant to be used for all DEs and finally 992-rootcopy_5.0* for settings individual for each DE.

I am using 200-rootcopy and all personal global scripts first and then executing custom all other applications