This has been noticed while reordering some modules' makefiles.
In bootloader/module.mk there are too many targets that are not strictly related to the bootloader code but to the virtual environment used to perform bootloader and in general kernel execution (vbox img disk creation, deletion and vbox running).

I propose the following:

• move these targets in a different makefile
• create a new folder (e.g. execution-env) and move that new makefile there.

Now comes the question: is it conceptually correct to create a new module (new makefile means new module) even if we are not going to insert code into it?

Consider creating some targets (using Make) to check whether the project submodules have been cloned to the local dir.

Since this should work OOB (kernel tarball download -> configure -> make) and we want to have ANREM as a git submodule we could have an initial makefile containing a 'init' target (that clone all the submodules) that could be overwritten by the real project makefile after the cloning procedure.

After the init procedure ANREM (i.e. the modules of the project) should anyway check for all the submodules needed in the compile procedure (since one or more of them could have been deleted).

Lots of dependencies are now involved in the project. It's time to setup a configure procedure.

You should write a function that prints out memory mapping.