As of 5cdbd57de09b64f48d06351b065dc8949493d7e8 we have done it for the kernel, but to have a better feeling of what instruction counts mean, we should do a few more.

A simple well known algorithm would also be good.

It'd be good to state publicly the oldest kernel and glibc (or even other libc versions) we support.
This would allow us to remove some legacy code or force support for legacy code.

This shouldn't require test to be functional (e.g. for some cases like module drivers it could be hard),
but LTP to be compiled and when difficult/impossible to achieve this functionality, it could resulted in TCO

The Slax URL which explains the boot internals is here:

https://www.slax.org/internals.php

The corresponding URL in the tutorials should be updated. Also, the websites should be updated (put the new tutorial document) as well in order to reflect this change.

it's great you folks a few example configs for the exporter.. however since you demonstrate a lovely grafana graph graphing the metrics (say that 5 times fast), it would really swell if you also included the dashboard definition JSON that creates those exact grafana graphs..

p.s.. a [quick search](https://grafana.com/grafa

An attempt to port LinuxBoot to the Dell E7420 mentions that there are no guidelines for which DXE modules are necessary to retain, which can be discarded etc.

We should document that.

Configuration file format is not going to be stabilised until 1.0 or higher versions, but our wiki pages can fit only master release. We need to update the documentation and add the following:

• Add 'Available from: VERSION' to all directives to indicate which minimal version must be used for the directive. E.g. directive vhost was introduced in 0.6 release, but not accessible in 0.5 releas

While trying to learn how to use EVDI I discovered that evdi_get_event_ready is mentioned in the Quick Start, but not the detailed documentation. As I understand it, the detailed documentation is supposed to document all of libevdi.

Currently, the PCM formats that are supported are mostly the signed integer ones.

The rest of the PCM formats from sound/asound.h should be supported.

See the definitions here.

One problem with faulting programs under KRF is that KRF might decide to inject a fault during the dynamic link/load phase, aborting ld-linux.so instead of the actual target image. This usually isn't helpful, since it doesn't indicate any mistakes in the target itself.

It should be possible to check the loaded program's name via the current task, probably via comm. We should use that (or