reassign 302324 initrd-tools retitle 302324 Misleading error message for files in /lib/modules/$KVERS/kernel that have non-.o/.ko suffix severity 302324 minor thanks
This bug included a number of different issues. Summarizing the relevant point for initrd-tools: If an admin or package creates a file in /lib/modules/$KVERS/kernel that doesn't end in .o or .ko - like some kernel module packages do by diverting a module to e.g. foo.ko.orig when they provide a newer versions of some module that is also included in the kernel package itself - mkinitrd outputs a grave error message: Setting up kernel-image-2.6.10-nb (01) ... /usr/sbin/mkinitrd: add_modules_dep_2_5: modprobe failed FATAL: Module loop.ko_orig not found. WARNING: This failure MAY indicate that your kernel will not boot! but it can also be triggered by needed modules being compiled into the kernel. The resulting initrd works without problems and the stray file IMHO doesn't justify an error message of that severity. Instead of warning about the file, mkinitrd could ignore anything not named .o or .ko when looking for kernel modules. [I realize initrd-tools is kept alive in low-maintenance mode mostly (only?) for sarge -> etch upgrade support, but I wanted to process this old bug report.] cheers, Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
