Re: 2.4.19pre8aa2

[Keith Owens <kaos@ocs.com.au>]

On Sun, 05 May 2002 18:04:41 +1000, 
Keith Owens <kaos@ocs.com.au> wrote:
>On Sun, 05 May 2002 17:40:56 +1000, 
>Eyal Lebedinsky <eyal@eyal.emu.id.au> wrote:
>>You are right, it is not the unresolved that caused it but the non
>>ELF objects in there (it used not to care before):
>>
>># /sbin/depmod-2.4.15 -ae ; echo $?
>>depmod: /lib/modules/2.4.19-pre8-aa2/ksyms is not an ELF file
>>depmod: /lib/modules/2.4.19-pre8-aa2/soundconf is not an ELF file
>>1
>
>All versions of depmod for 2.4 have always returned errors for invalid
>objects in /lib/modules, that check has not changed since modutils
>2.4.0.  modutils has not changed, somebody is storing extra text files
>in /lib/modules without telling modutils.  Don't do that.

My apologies, this is an unexpected side effect of a change in modutils
2.4.13.  Christian Lademann asked that depmod do as much work as
possible instead of exiting early.  That meant checking the error count
at the end of depmod and giving a non-zero return if any errors were
detected.  depmod before 2.4.13 ignored the return code from the
loadobj() function, with the 2.4.13 change the ignored error flag was
being used.

I will revert to ignoring the loadobj() return code for error purposes
in modutils 2.4.17.  The behavior is wrong but it is what people
expect.