I am not sure this is the right place to fix this. Strictly speaking, an
initrd is not required in all setups or contexts which this script might
be called from. Hence, the current logic.
You say the virtual box dkms FTBFS. What is still continuing after that
failure? Shouldn't *that* be the "hard failure" reported to the user?
Please provide some logs and/or output from your reproducer to
illustrate what's happening.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2141741
Title:
55-initrd.install silently exits 0 when initrd missing causing
undetectable kernel panic on NVMe systems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2141741/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
