You could keep the modified initrd just fine, the way I recommended you modify the initrd should keep across upgrades and such.
I experienced this bug with 2.6.20-4-386 and 2.6.20-4-generic, which means by 2.6.20-5-386 and 2.6.20-5-generic it should be fixed. However, I'm not an ubuntu kernel guy, just a regular kernel guy so I don't know what sort of distro policies they have in place for releasing important critical parts of a linux system. 2.6.20 in general was a much better release of the linux kernel than most of the other releases (imho), so any continued work on that version of the kernel should only get better.
You could keep the modified initrd just fine, the way I recommended you modify the initrd should keep across upgrades and such.
I experienced this bug with 2.6.20-4-386 and 2.6.20-4-generic, which means by 2.6.20-5-386 and 2.6.20-5-generic it should be fixed. However, I'm not an ubuntu kernel guy, just a regular kernel guy so I don't know what sort of distro policies they have in place for releasing important critical parts of a linux system. 2.6.20 in general was a much better release of the linux kernel than most of the other releases (imho), so any continued work on that version of the kernel should only get better.