From: Jari Nguyen Trung Thanh <jari.nguyen@serialsystem.com.sg>
To: Mike Hill <mhill@bustech.com>
Cc: Nils Hagge <Nils.Hagge@stud.uni-hannover.de>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: Kernel panic: No init found.
Date: Thu, 14 Dec 2000 00:00:56 +0800 (SGT) [thread overview]
Message-ID: <976723256.3a379d38783d0@mail.serialsystem.com.sg> (raw)
In-Reply-To: <004801c0651d$3a7d96e0$e3e8b2c6@hawk>
Hi Mike Hill and Nils Hagge,
Quoting Mike Hill <mhill@bustech.com>:
>
> I believe I have seen the same problem. As I recall, we first started
> seeing this problem when we removed a symlink (/opt/hardhat/devkit to /)
> that was included in the MontaVista target directory. We were told that
> we
> had it add it back because some of the MontaVista libraries were built
> incorrectly.
Oh, I forgot it, it happened to me in the past, too.
However, this just supports for building another application which can use the
library in the root/lib directory, when it run in the embedded systems...
You may want to check to see if you have that symlink in
> your
> target directory.
>
Hope this help,
Jari
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-12-13 16:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-13 14:17 Kernel panic: No init found Nils Hagge
[not found] ` <976717249.3a3785c2030de@mail.serialsystem.com.sg>
2000-12-13 15:32 ` Nils Hagge
2000-12-14 0:03 ` Graham Stoney
2000-12-14 1:55 ` jari.nguyen
2000-12-13 15:55 ` Mike Hill
2000-12-13 16:00 ` Jari Nguyen Trung Thanh [this message]
2000-12-13 17:45 ` mlocke
-- strict thread matches above, loose matches on Subject: below --
2003-09-26 6:44 Mike G.
2003-09-26 17:44 ` Mark Hatle
2003-09-29 1:10 ` Michael G.
2008-08-18 9:11 Kernel panic : No Init Found Fabien Oriede
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=976723256.3a379d38783d0@mail.serialsystem.com.sg \
--to=jari.nguyen@serialsystem.com.sg \
--cc=Nils.Hagge@stud.uni-hannover.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mhill@bustech.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.