View Single Post
Old 06-23-2012, 07:21 PM   #67
wlaf
Enthusiast
wlaf writes the songs that make the whole world sing.wlaf writes the songs that make the whole world sing.wlaf writes the songs that make the whole world sing.wlaf writes the songs that make the whole world sing.wlaf writes the songs that make the whole world sing.wlaf writes the songs that make the whole world sing.wlaf writes the songs that make the whole world sing.wlaf writes the songs that make the whole world sing.wlaf writes the songs that make the whole world sing.wlaf writes the songs that make the whole world sing.wlaf writes the songs that make the whole world sing.
 
wlaf's Avatar
 
Posts: 44
Karma: 40820
Join Date: Jun 2012
Device: Kindle 3 WIFI
Quote:
Originally Posted by knc1 View Post
Quote:
Originally Posted by wlaf View Post
Using "setenv rdinit /bin/sh" I got:

Code:
uboot> setenv rdinit /bin/sh
uboot> boot
You need to add that to the existing command line argument strings.
You __must__ use the equals sign.

U-boot contains a small shell, when you print all of the environment variables, you are reading shell scripting.
I checked again, and it seems that you're right. The correct format seems to be:
Code:
setenv bootargs $bootargs init=/bin/sh
boot
And for testing purpose:
Code:
exec init
from here:
http://docwiki.gumstix.org/index.php/U-Boot
There are more complex usages that I don't want to test initially!

Btw, the original init was this (see page 3 for the logs from the initial state):
Code:
/sbin/init.sysvinit
wlaf is offline   Reply With Quote