Issue when not using `/etc/initramfs-tools/conf.d/*.conf`

[st0nedB]

I use dropbear-initramfs to unlock a LUKS LVM on an Ubuntu-Server 22.04. As I also use interface-bonding, I stumbled upon your repo.
Thanks for the amazing work! Just wanted to let you know of a minor issue I came across:

I used it to configure interface bonding and ran into an issue when adding the configuration to /etc/initramfs-tools/initramfs.conf instead of using the conf.d, e.g. via /etc/initramfs-tools/conf.d/some-important-rule.conf.
If the /etc/initramfs-tools/conf.d/ is an empty directory, running sudo update-initramfs -u generates the following output:

update-initramfs: Generating /boot/initrd.img-5.15.0-47-generic
grep: /etc/initramfs-tools/conf.d/*.conf: No such file or directory
grep: /etc/initramfs-tools/conf.d/*.conf: No such file or directory

If one reboots at this point, the initramfs will fail and possibly even fail to boot. I had to unlock by attaching a keyboard and screen to to the machine, then it would continue to boot.

The issue can be easily resolved by adding an empty *.conf file into conf.d, or by adding the config into an extra file (as I should have done in the first place anyways).

[stcz]

Sorry, but because I'm not using the hook anymore and a lack of time, I'm not able to maintain this repo anymore.

Please fork and start developing :)

[malakudi]

My pull request #18 fixes this issue