Modification modules loading\unloading its tricky operation.
By default - each firmware package contain some postinstall scriptf wich perform:
1) Correct adding modules requirements in modprobe.d
2) Perform adding initrams modules and hooks
3) Perform rebuilding initramfs.
All this steps totally depends on firmware maintainer and we cant support all possible situations.
Conclusion:
1) --include-kernel-module & --blacklist-kernel-module will be remove from fuel-bootstrap tool scope
2) User still can add any customization to modules(by they own risk) with --script ${script} parameter
For example:
##
$ cat script
#!/bin/bash
echo "Adding user modification into bootstrap!"
echo '# add custom blacklist module, by bootstrap maintainer' >> /etc/modprobe.d/user_custom.conf
echo "blacklist fuse" >> /etc/modprobe.d/user_custom.conf
##
Modification modules loading\unloading its tricky operation.
By default - each firmware package contain some postinstall scriptf wich perform:
1) Correct adding modules requirements in modprobe.d
2) Perform adding initrams modules and hooks
3) Perform rebuilding initramfs.
All this steps totally depends on firmware maintainer and we cant support all possible situations.
Conclusion: kernel- module & --blacklist- kernel- module will be remove from fuel-bootstrap tool scope
1) --include-
2) User still can add any customization to modules(by they own risk) with --script ${script} parameter
For example:
##
$ cat script
#!/bin/bash
echo "Adding user modification into bootstrap!" d/user_ custom. conf d/user_ custom. conf
echo '# add custom blacklist module, by bootstrap maintainer' >> /etc/modprobe.
echo "blacklist fuse" >> /etc/modprobe.
##