From: Brian Waite <waite@skycomputers.com>
To: Dan Malek <dan@embeddededge.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: NFS root woes: No init found
Date: Wed, 4 Dec 2002 17:11:04 -0500 [thread overview]
Message-ID: <200212041711.04032.waite@skycomputers.com> (raw)
In-Reply-To: <3DEE781C.5070208@embeddededge.com>
I did this. I tried to start a staticly linked ash shell to no avail. No libs
are better than any libs :)
Thanks
Brian
On Wednesday 04 December 2002 4:48 pm, Dan Malek wrote:
> Brian Waite wrote:
> > ...Then I get the message No init found.
>
> First, try using something simple like /bin/bash as your init program.
> Trying to start up the init program relies on lots of things being
> present in the file system. If the program starts, and then exits,
> you still get this message.
>
> Just use a trivial, simple file system to get started. A shell,
> couple of commands and minimal libraries are easier to debug.
>
> Good luck :-)
>
> -- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-12-04 22:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 21:35 NFS root woes: No init found Brian Waite
2002-12-04 21:48 ` Dan Malek
2002-12-04 22:11 ` Brian Waite [this message]
2002-12-04 22:20 ` Wolfgang Grandegger
2002-12-04 22:30 ` Brian Waite
2002-12-04 22:47 ` Jerry Van Baren
2002-12-04 23:03 ` Brian Waite
2002-12-04 22:49 ` Roland Dreier
2002-12-04 22:52 ` Brian Waite
2002-12-04 22:27 ` Roland Dreier
2002-12-04 22:36 ` Brian Waite
2002-12-05 8:50 ` Dan Vatca
2002-12-05 15:20 ` Brian Waite
2002-12-05 15:58 ` Allen Curtis
-- strict thread matches above, loose matches on Subject: below --
2002-12-07 1:36 Pagnotta, Chris
2002-12-07 11:02 ` Wolfgang Denk
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=200212041711.04032.waite@skycomputers.com \
--to=waite@skycomputers.com \
--cc=dan@embeddededge.com \
--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 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.