public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Smith <chris.smith@swri.org>
To: linux-kernel@vger.kernel.org
Subject: ld.so kernel difference
Date: Mon, 05 Jan 2004 16:20:15 -0600	[thread overview]
Message-ID: <7bf757ae92.7ae927bf75@swri.org> (raw)

I have a system booting via pxe using a kernel built from redhat source (2.4.20-8). I am trying to get the system to boot using a kernel.org kernel. (one of many 2.4.22, 23, 20) 

This system is very stripped down, no disks. ~12MB for the full running os. essentially the init is the only thing running. it starts various daemons then loops on a bash propmt.

What I am seeing (and why i sent it to this list) is that there appears to be a difference in how the libraries are being found between the two types of kernels. the redhat derived kenrel is working but none of the kernel.org kernels are. 

the error i am seeing with the kenrel.org kernels is: 
/bin/sh: error while loading shared libraries libc.so.6: cannot open shared object file: no such file or directory.

then it tries to kill the init and the kernel panics.

is there a way the kernel can influence how/where ld.so looks for a library? the libraries are present on the ramdisk just not found by the kernel. the kernel is accessing the ramdisk since it is trying to run the init script (it is failing on loading /bin/sh since this is not statically linked). the "redhat" kernel using the same ramdisk works fine (same ld.so.cache, etc).

??

chris


                 reply	other threads:[~2004-01-05 22:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=7bf757ae92.7ae927bf75@swri.org \
    --to=chris.smith@swri.org \
    --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