LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "AlessandroPPC" <aleppcrossi@libero.it>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: busybox problem
Date: Tue, 9 Dec 2003 17:28:08 +0100	[thread overview]
Message-ID: <007b01c3be71$6ec82c20$0400a8c0@eurostudio.local> (raw)


Hi to all,

To solve a problem with ram root filesystem Wolfgang Denk has suggestes to
me  to use his
SELF ramdisk image.
I have successfully used his package.
But I have found a problem with BusyBox init, when T have tried to
customized the init board
configuration.
The problem is related to /etc/rc.sh init script, in fact editing rc.sh and
rebuilding the ramdisk
image the output init is the following:


  "Bummer, could not run '/etc/rc.sh': No such device or directory"

Notice that /etc/rc.sh is present, is an exutable file and has root
privileges.

Any suggestion is appreciated.
R.R.C.S.C.

Thanks to all
Regards,
Alessandro


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

             reply	other threads:[~2003-12-09 16:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-09 16:28 AlessandroPPC [this message]
2003-12-09 16:56 ` busybox problem Jaap-Jan Boor

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='007b01c3be71$6ec82c20$0400a8c0@eurostudio.local' \
    --to=aleppcrossi@libero.it \
    --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