Anatol Pomozov

Thank you for the patch! It is useful to have such functionality. It also needs - documentation, I think https://github.com/anatol/booster/blob/master/docs/manpage.md#boot-time-kernel-parameters would be the best place to add information about parameters...

I'll be happy to test/review your changes. As well as contribute to your PR if you are fine with it.

@ethomson how do you feel if I start populating missing `[out]` and then send a PR for it?

And speaking of the documentation - there is a good number of functions that miss documentation. It is worth filling this gap.

I tried to google more about this problem. It looks like `dangling-pointer` warnings [were added recently](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106393) and are prone to [false positives](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109514). But I don't really know GCC/C++ well enough...

Could you please run booster with debug parameters and then post its full output here? `booster -v build --force --kernel-version 6.12.5-1-cachyos /tmp/booster-linux-cachyos.img`

Thank you for debugging the problem. I wonder what is the root cause for the problem with strip. Strip functionality is used only here (AFAIR) https://github.com/anatol/booster/blob/6df7c60694103287bd53877399a3cbca4490c820/generator/image.go#L186 so the main difference...

Hi @initMayday the `activate module` message you have are coming from generator. This is the phase where the *.img image is built. The original issue was related to the generator...

Thank you, this is indeed might be a useful warning for the boot speed improvement enthusiasts. I am trying to figure out what would be the criteria for the initrd-less...

Any objections for this change? If not - I am going to merge it to the codebase.