mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eyal Lebedinsky <eyal@eyal.emu.id.au>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.19pre8aa2
Date: Sun, 05 May 2002 23:38:59 +1000	[thread overview]
Message-ID: <3CD535F3.1193069@eyal.emu.id.au> (raw)
In-Reply-To: <4003.1020585881@ocs3.intra.ocs.com.au>

Keith Owens 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.
> 
> Who created the ksyms and soundconf files?

I do. Since I have many kernels built, my build script copies the
important bits into there. I have done this for many years now
(as can be seen by the ancient 'soundconf' still being copied)
without any problems. /lib/modules is the only per-kernel area
on my machine and it is the most natural place to keep these files.

The failure started showing up only later in 2.4, I do not remember
exactly when but it is many months ago now. The 'not an ELF' message
was non fatal until then. I was pretty much keeping up with the
modutils releases.

--
Eyal Lebedinsky (eyal@eyal.emu.id.au) <http://samba.org/eyal/>

  parent reply	other threads:[~2002-05-05 13:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-04 14:54 2.4.19pre8aa2 Andrea Arcangeli
2002-05-04 15:02 ` 2.4.19pre8aa2 Christoph Hellwig
2002-05-04 23:34   ` 2.4.19pre8aa2 Eyal Lebedinsky
2002-05-05  3:04     ` 2.4.19pre8aa2 Keith Owens
2002-05-05  7:40       ` 2.4.19pre8aa2 Eyal Lebedinsky
2002-05-05  8:04         ` 2.4.19pre8aa2 Keith Owens
2002-05-05  8:16           ` 2.4.19pre8aa2 Keith Owens
2002-05-05 13:38           ` Eyal Lebedinsky [this message]
2002-05-05  0:25   ` 2.4.19pre8aa2 Andrea Arcangeli
2002-05-04 18:56 ` 2.4.19pre8aa2 Francois Romieu
2002-05-05  0:14   ` 2.4.19pre8aa2 Andrea Arcangeli
2002-05-08  2:27 ` 2.4.19pre8aa2 Pozsar Balazs
2002-05-08  9:34   ` 2.4.19pre8aa2 Andrea Arcangeli
2002-05-08  9:46     ` Problems with mm on Alpha Oliver Pitzeier
2002-05-08 10:54       ` Ivan Kokshaysky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3CD535F3.1193069@eyal.emu.id.au \
    --to=eyal@eyal.emu.id.au \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®