Remove update-initramfs diversion entirely#5
Merged
Merged
Conversation
The boot-finished guard added in 7d8e1f7 didn't work: cloud-init deletes boot-finished at the start of every boot, so bootcmd always re-applied the diversion. runcmd only runs once-per-instance, so it only cleaned up on first boot. On subsequent boots the diversion was re-applied permanently, causing unattended kernel upgrades to produce no initramfs — same kernel panic as before. The MODULES=dep setting in initramfs-tools already cuts rebuild time from minutes to seconds, making the diversion unnecessary. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Member
Author
|
This was silly, I didn't realize Debian didn't tailor the initrd to only have what it needed. You have to opt into this, which makes update-initramfs super fast. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The boot-finished guard added in 7d8e1f7 didn't work: cloud-init deletes boot-finished at the start of every boot, so bootcmd always re-applied the diversion. runcmd only runs once-per-instance, so it only cleaned up on first boot. On subsequent boots the diversion was re-applied permanently, causing unattended kernel upgrades to produce no initramfs — same kernel panic as before.
The MODULES=dep setting in initramfs-tools already cuts rebuild time from minutes to seconds, making the diversion unnecessary.