On Tue, Mar 23, 2010 at 8:38 PM, perumal316 wrote:
> Hi,
>
> I have come up with a kernel module doing monitoring of system calls
> and will printk messages. Now I want to show these messages to user
> through an application.
What's wrong with the strace application?
Or the kernel audit subsyste
Hi, please try *su*, I think *sudo *command is not present in android's
busybox.
Regards,
Karthik Poduval
On Wed, Mar 24, 2010 at 4:58 AM, Gidiyo wrote:
> Hi,
>
> I would like to know what other kernel command could I used for my
> ported Android.
> Currently, using minicom, I could list my roo
Hi,
I would like to know what other kernel command could I used for my
ported Android.
Currently, using minicom, I could list my root file system by typing
'ls' command.
But when I tried sudo, it prompt me with a 'sudo: not found'.
I would like to enable a device driver. What are the command do I
On Wed, Mar 24, 2010 at 3:45 AM, karthik poduval
wrote:
> Hi Please find replies inline:-
>
> Regards,
> Karthik Poduval
>
> On Tue, Mar 23, 2010 at 1:53 PM, Ambuj wrote:
>
>> Hi,
>>
>> I am a Junior Undergraduate in a University in India, I have been
>> working with Embedded Systems Programming
This is a great contribution, thanks for all your effort!!
I cant wait to see it running on my android!
--
unsubscribe: android-kernel+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-kernel
To unsubscribe from this group, send email to
android-kernel+unsubscribegoo
Hi,
If you want to monitor system calls for an aplication, you could make use of
strace command or refer tot its code for your use case.
Regards,
Karthik Poduval
On Tue, Mar 23, 2010 at 10:38 PM, perumal316 wrote:
> Hi,
>
> I have come up with a kernel module doing monitoring of system calls
>
You mean I should use "dmesg>file.log" in the java program I am
writing to read the printk messages?
Regards,
Perumal
On Mar 24, 5:00 pm, Tirtha Kanti Ghosh wrote:
> Though I am not sure about your needbut a simple solution which I can
> think of is
>
> dmesg > file.log (or >> for appending
Though I am not sure about your needbut a simple solution which I can
think of is
dmesg > file.log (or >> for appending)
read the file.log from your app.
Now, how frequent you need to do dmesg>file.log, that's totally depends on
your need.
I mean this way you can at least read printk() mess
