Thanks Hareesh for the explanation. That gave me better understanding. :) @duryodhan : I read the discussion going on that thread. But the solution you gave is fine for kernel developers who are going to test something. What if we have to add system call to kernel release and then some other user is going to use that. He doesnt have any idea about system call number we have assigned,...he shud not be bothered abt that. ????
Whats the solution for that ? Sachin [P.S: sorry duryodhan for repeatd message. I forgot to do reply-all first time] On 9/8/07, duryodhan <[EMAIL PROTECTED]> wrote: > > Hey, > I would recommend that you directly call syscall yourself. > #define __NR_syscall_number 324 //(e.g) > #include <linux/unistd.h> > #include <sys/syscall.h> > > in the C program do > syscall(324, arg1, arg2) > > _syscall2 etc. is a pain to work with, and afaik has been unsupported > for quite some time. > http://lkml.org/lkml/2007/7/5/314 > > Regards, > duryodhan >
