View Single Post
Old 06-19-2012, 07:01 PM   #56
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by wlaf View Post
This is the first thing I should try. Working with bash is much easier than recompiling the kernel and changing boot scripts and transferring it to the device.
If you have never brought up a Linux system "by hand" - you will have questions, do not hesitate to ask.

If the rdinit=/bin/sh on the kernel command line (gotten there by adding it to one of the u-boot, command line variables) gets you a sh command shell...

The first thing you will need to do is:
mount -t proc proc /proc
mount -t sysfs sysfs /sys
Those two will need to be mounted because many commands/utilities need to be able to reference them.

You will also need /dev but that may be handled by your kernel internally, we can look around and see what is needed after doing the above.

Note: It is getting late in the day, early in the evening, in my time zone - this may have to wait until tomorrow (say 12 hours from now).
knc1 is offline   Reply With Quote