Initialising Pyromaniac with lots of modules in ROM

by gerph
macOS ◆ xterm-256color ◆ fish 1088 views

The resident modules (ROM and podule modules, although only the former are currently supported) are now implemented independantly from the RMA modules. These are separate modules which are present in memory and initialised prior to the system boot. This allows the resident modules to fail their initialisation but not prevent the system booting.

Here, the ROM initialisation is configured to be ‘noisy’, printing out messages about the modules as they start up. Additionally, the system is configured using the new configuration files which can contain parameters that would previously have been supplied on the command line - this is useful for this case, as there are about 200 modules present.

Not all of the modules work - indeed many don’t work at all. A few months ago I built everything that had a working build and collected them so that I could use them as tests. A surprising number now initialise, and many do actually work. There’s a lot of modules that are not even present in the list because they generate aborts for a variety of reasons.