linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Locke <mlocke@mvista.com>
To: kingseft@samsung.co.kr
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: [Question] init does not find library files.....
Date: Tue, 06 Mar 2001 16:27:56 -0800	[thread overview]
Message-ID: <3AA5808C.4F976328@mvista.com> (raw)
In-Reply-To: H00002af04a809ff@MHS


you are probably missing an important link.  It is in
.../target/opt/hardhat...

Include that link in your ramdisk and it should work fine.

kingseft@samsung.co.kr wrote:
>
>   Thank for your kindful replying for our question about ramdisk.
>
>   Now we installed HardHat Linux CDK and found file system in /targer directory.
>   we follwed all procedures and made ramdisk.gz
>
>   But, when we ran this ramdisk iamge, init didn't found libc.so.6
>   of course, we put this libc.so.6 file into our /lib directory in ramdisk.gz
>   following is our result...
>
>   We need your comments, any comments will help us.. thanks...
>
>   ----------- our experiment result ----------
>
> RAM disk driver initialized: 16 RAM disks of 10240K size
> loop: registered device at major 7
> eth0: CPM ENET Version 0.2, 00:05:27:00:00:01
> RAMDISK: Compressed image found at block 0
> EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
> VFS: Mounted root (ext2 filesystem).
> Freeing unused kernel memory: 28k in
> init: error in loading shared libraries: libc.so.6: cannot open shared object fi
> le: No such file or directory      <--- Here is our problem!!!
>

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      parent reply	other threads:[~2001-03-07  0:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-06 23:50 [Question] init does not find library files kingseft
2001-03-07  0:21 ` Graham Stoney
2001-03-07  0:26   ` Graham Stoney
2001-03-07  0:27 ` Matthew Locke [this message]

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=3AA5808C.4F976328@mvista.com \
    --to=mlocke@mvista.com \
    --cc=kingseft@samsung.co.kr \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).