build: add --without-kmodules configure flag

[dvoytik]

Which can be used to exclude kernel modules from rootfs in
the image building phase.

Signed-off-by: Dmitry Voytik dmitry.voytik@huawei.com

[Jimmy-Xu]

Can one of the admins verify this patch?

[gnawux]

I think it's would be better to support specifying the customized kernel path in the configure command line, such as

.```
./configure --with-custom_kernel=/path/to/the/kernel

[dvoytik]

@gnawux I agree, that way would be more generic and cover other problems. But also it would need to overhaul the whole build/make-initrd.sh at least. Unfortunately I don't have time to do this and test other case like virtualbox, aarch64, etc.
Actually personally I'd abandon totally the image build part and rely completely on https://buildroot.org/. With buildroot you would need only to put hyperstart binary in specific location, other stuff (like iptables, kernel modules, etc.) is covered by buildroot. Also it would simplify cross-building for other architectures.

[gao-feng]

Looks weird having --with-custom_kernel without --with-custom_modules, actually we need --with-custom_modules more IMO.

[dvoytik]

@gao-feng Okay, I can rename it to --with-custom_modules. Let me update the pull request. How do your prefer - a squash or additional commit on top of this?

[dvoytik]

@gao-feng I am a bit confused. Do you want me to keep the logic of the patch? In my patch I just want to be able to exclude provided by hyperstart kernel modules (we don't use them in our project). If yes then maybe it make sense to rename the option to "--without-kmodules" and by default it is turned off (i.e. resulting to inclusion of the provided kernel modules, so no breaking of previous build functionality)?

[gao-feng]

@dvoytik ok, let's simplify the logic, --without-kmodules looks good to me

[gao-feng]

LGTM

[Jimmy-Xu]

Can one of the admins verify this patch?