Hello,
I am trying to debug a problem in the init process;
I would like to know - generally speaking, what is the best way to
debug the init process? ... there are several calls to INFO - where do
these messages go?
The main problem now is, it appears that init never returns from the
function init_parse_config (with my crude debugging method of creating
directories).
INFO("reading config file\n");
mkdir("/bar2", 0755);
init_parse_config_file("/init.rc");
mkdir("/bar3", 0755);
I changed the on fs rules so I could mount filesystems over nfs (could
it be why it's breaking) ? From what I understand actions are just
shell commands.
---0-0-0-
on fs
# mount mtd partitions
touch /fs-start
# Mount /system rw first to give the filesystem a chance to save a
checkpoint
#mount yaffs2 mtd@system /system
#mount yaffs2 mtd@system /system ro remount
#mount yaffs2 mtd@userdata /data nosuid nodev
#mount yaffs2 mtd@cache /cache nosuid nodev
mount nfs 192.168.1.64:/storage/workspace/android/out/target/
product/generic/system /system
mount nfs 192.168.1.64:/storage/workspace/android/out/target/
product/generic/system /system ro remount
mount nfs 192.168.1.64:/storage/workspace/android/out/target/
product/generic/data /data nosuid nodev
#mount yaffs2 mtd@cache /cache nosuid nodev
---0-0-0-
-ravi
--
unsubscribe: android-kernel+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-kernel
