On 08/01/2012 05:32 AM, Pieter wrote: > echo writes to stdout, which is by default redirected to /dev/null. > > You could try to use "logwrapper", but I am not sure it will work in init.rc > (it > does work in "regular" sh scripts). > > Pieter > > > On Tuesday, July 24, 2012 8:30:27 PM UTC+2, 9exceptionThrower9 wrote: > > > I am modifying the respective "init.rc" found in ~/system/core/rootdir" > and > "init.tuna.rc" in "~/device/samsung/tuna" files so that there are a few > echo > commands to help me debug. > > Does anyone know if Google/Android's RC files do not allow Linux syntax > like > this? I am using a line of code inserted at various points within the RC > file such as: > > /# Checkpoint 0.1 > echo "Check 0.1: About to create basic filesystem structure and set > up > the wpa_supplicant configuration!" >>& `pwd`/Desktop/boot_log_general.txt/ > > I am trying to reroute the normal output to a file I can find elsewhere > and > view to at least how far the phone steps in the boot process at the > initialization stage. Should this work or is there developer > command/syntax > to get some kind of output from the RC? > > Any guidance to help me set up at least this kind of rudimentary kind of > debugging during the boot process would be greatly appreciated!
Try: 'echo "my message here" >/dev/kmsg' See http://elinux.org/Debugging_by_printing#Printk_from_userspace This will put your message in the kernel's log buffer, which can be extracted later with dmesg. If you happen to have kernel printk timestamps turned on (see the same page in the wiki), then as a bonus you'll get a timestamp on your message. -- Tim ============================= Tim Bird Architecture Group Chair, CE Workgroup of the Linux Foundation Senior Staff Engineer, Sony Network Entertainment ============================= -- unsubscribe: [email protected] website: http://groups.google.com/group/android-kernel
