On Thu, 2009-03-19 at 21:57 +0100, Frans Pop wrote: > Because the old modprobe does not understand the new relative (or rather > rootless) paths, aggravated by the fact that initramfs-tools does not > error out or display errors from modprobe (probably for good historic > reasons), I suddenly had an initramfs that contained no modules and thus > a system that failed to reboot with the new kernel. Well, that lack of understanding the difference between relative/explict paths was fixed but of course we can't go back in time and fix what's already out there and in use. Yes, it was a bad idea of mine (perhaps) to change the existing file format and I've learned something, but it should only have affected for example that 3.4 release you're using. Jon. -- To unsubscribe from this list: send the line "unsubscribe linux-modules" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
