hi
i am working on open suse..
can any one say what are the steps to add a system call for
linux kernel 2.6.34..
what are the exact files to be updated for the version 2.6.34.
Thank you in advance...

can any one atleast say exact procedure for adding a system call in 2.6.27 and what are the exact files to be updated....

Was that information missing from the link I gave you here http://www.linuxquestions.org/questi...4/#post4056569 ?

thanks for the information but when i am compiling the kernel it is showing some error UTSRELEASES.h. i downloaded the kernel from kernel.org twice but its showing the same error...

Then post the exact error message!

this is what the error message i got

make && make modules_install && make install
scripts/kconfig/conf -s arch/x86/Kconfig
CHK include/linux/version.h
UPD include/linux/version.h
/bin/sh: -c: line 0: unexpected EOF while looking for matching `"'
/bin/sh: -c: line 1: syntax error: unexpected end of file
make: *** [include/linux/utsrelease.h] Error 2

You have written the make file ? The errors may be in it !
Run only make and post the exact output here. And if there are some errors, post the Makefile here ! Then may be someone can help you.

Read Chapter 10. System Calls of the book "Understanding the Linux Kernel, 3rd Edition"

i am using kernel 2.6.27. Make gave me this error
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
GEN .version
CHK include/linux/compile.h
UPD include/linux/compile.h
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
KSYM .tmp_kallsyms1.S
AS .tmp_kallsyms1.o
LD .tmp_vmlinux2
KSYM .tmp_kallsyms2.S
AS .tmp_kallsyms2.o
CHK include/linux/version.h
HOSTCC scripts/unifdef
scripts/unifdef.c:209:25: error: conflicting types for ‘getline’
/usr/include/stdio.h:653:20: note: previous declaration of ‘getline’ was here
make[2]: *** [scripts/unifdef] Error 1
make[1]: *** [__headers] Error 2
make: *** [vmlinux] Error 2

I don't like this idea of yours.

You post same problems in different threads. You have posted this make error here as well as you have created a new thread for it ?

And this is not the first time you are doing it !

I do not want to reply to you now.

A different thread should be created for a different problem, that's Good,

but posting same problem in two threads is not a good idea.