New System call & Kernel compilation

New System call & Kernel compilation

[selva kumar]

selva:
  After adding a new system call, should we have to
recompile the whole kernel? can anyone help me
regarding this?

Thanks
selva



		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - Helps protect you from nasty viruses. 
http://promotions.yahoo.com/new_mail

Re: New System call & Kernel compilation

[Randy.Dunlap]

selva kumar wrote:
> selva:
>   After adding a new system call, should we have to
> recompile the whole kernel? can anyone help me
> regarding this?

Yes, it's expected that you rebuild the kernel
(at least all affected files), then reboot that
kernel to use the new syscall.

OTOH, there has been some recent email on lkml about
dynamic syscalls and a way to allow them (mostly for
experimental use AIUI, but if that's the case, just
rebuilding and rebooting would probably do for most
people).

-- 
~Randy

Re: New System call & Kernel compilation

[Sam Ravnborg]

On Fri, Dec 17, 2004 at 02:26:31AM -0800, selva kumar wrote:
> selva:
>   After adding a new system call, should we have to
> recompile the whole kernel? can anyone help me
> regarding this?

You do not need to do a 'make clean'. Simply executing make will suffer 
since kbuild has track of all dependencies.

Assuming 2.6 kernel!

	Sam

Re: New System call & Kernel compilation

[Jan Engelhardt]

>>   After adding a new system call, should we have to
>> recompile the whole kernel? can anyone help me
>> regarding this?
>
>You do not need to do a 'make clean'. Simply executing make will suffer 
>since kbuild has track of all dependencies.
>
>Assuming 2.6 kernel!

Even in 2.4 you do not need make clean. make dep should suffice if you changed 
some includes.

I dislike how many FAQs and tutorials always add "do a make clean"... that 
requires you to recompile everything (read: may take "some time", when in 
practice you only need a few things (i'm speaking generally, any app is 
considered).


Jan Engelhardt
-- 
ENOSPC