Restore backup of initrd if zero-length file results
Bug #77279 reported by
Michael Olson
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| initramfs-tools (Ubuntu) |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
Binary package hint: initramfs-tools
I noticed that as of a routine feisty upgrade that I performed yesterday, the initrd image that I was using the 2.6.17-10-generic kernel is being replalced by a 0-length file. The worst part is that since update-initramfs was called multiple times, the backup is also a 0-length file. I am unable to re-create the image because I get a message to the effect that udev depends on 2.6.19 or later.
It would be optimal if the update-initramfs script would check to see whether the generated initrd file is 0-length. If it is, the backup should be restored immediately.
Revision history for this message
| Michael Olson (mwolson) wrote | #1 |
| Changed in initramfs-tools: | |
| importance: | Undecided → Wishlist |
| status: | New → Confirmed |
To post a comment you must log in.
Note: the 0-length file was caused by udev now requiring a 2.6.19 or later kernel. I'm not too concerned about that at the moment.