I believe some people see this as a security feature.

In IPFire 2 we don’t use this I think, so a module will be just fine.

Acked-by: Michael Tremer <michael.tremer(a)ipfire.org>

> On 26 Dec 2022, at 20:27, Peter Müller <peter.mueller(a)ipfire.org> wrote:
> 
> Backported from IPFire 3.x as aea3e8471c0c11d4a5a1164efbe7c7c948667b6e.
> 
> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
> ---
> config/kernel/kernel.config.x86_64-ipfire | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/config/kernel/kernel.config.x86_64-ipfire b/config/kernel/kernel.config.x86_64-ipfire
> index e3a57b18a..519fc8770 100644
> --- a/config/kernel/kernel.config.x86_64-ipfire
> +++ b/config/kernel/kernel.config.x86_64-ipfire
> @@ -902,7 +902,7 @@ CONFIG_COMPAT_BINFMT_ELF=y
> CONFIG_ELFCORE=y
> CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y
> CONFIG_BINFMT_SCRIPT=y
> -CONFIG_BINFMT_MISC=y
> +CONFIG_BINFMT_MISC=m
> CONFIG_COREDUMP=y
> # end of Executable file formats
> 
> -- 
> 2.35.3